One of my hosts refuse to start any VM if the storage is a block device (with <source dev='/dev...'>). I tested rge following cases: 1) whole disk mapped to VM; 2) zvol mapped to VM; 3) CDROM mapped to VM via /dev/sr0 All these cases result in a message: error: Unable to get devmapper targets for /dev/zvol/home64/lab/zfs-lab-root-ext4: No such file or directory All storage that is contained in a file (qcow2, raw and iso images) works OK. I can't understand what went wrong. Can you suggest further debugging steps?
qemu is run as qemu user, member of cdrom and disk groups to allow direct disk access. home64 ~ # groups qemu disk cdrom kvm disk cdrom kvm qemu
(In reply to Anton Gubarkov from comment #0) > One of my hosts refuse to start any VM if the storage is a block device > (with <source dev='/dev...'>). > I tested rge following cases: 1) whole disk mapped to VM; 2) zvol mapped to > VM; 3) CDROM mapped to VM via /dev/sr0 > > All these cases result in a message: > error: Unable to get devmapper targets for > /dev/zvol/home64/lab/zfs-lab-root-ext4: No such file or directory > > All storage that is contained in a file (qcow2, raw and iso images) works OK. > > I can't understand what went wrong. Can you suggest further debugging steps? Do you have your kernel compiled with Device Mapper support (CONFIG_BLK_DEV_DM)? Since version 4.3 it is needed for sucessfully attaching block devices to vm.
No CONFIG_BLK_DEV_DM was the culprit. Big thanks!
