virt-manager seems to handle LVM in the old-fashioned way, accessing the LV devices via /dev/vgname/lvname instead of /dev/mapper/vgname-lvname. This hides other devices which might have been created by device mapper, for example, unlocked crypto devices. I would like to be able to cryptsetup luksOpen /dev/mapper/vgname-c_lvname lvname, which creates a device node /dev/mapper/lvname, and to import the clear text device into an KVM guest.
This does not work since the LVM Volume Group looks into /dev/vgname, not seeing the unlocked device. mpath does obviously only look for /dev/mapper/mpath*, and adding /dev/mapper as a regular directory doesn't work since virt-manager wants do to things with /dev/mapper/control that it cannot do.
The "nice" way would be to add a new storage pool type "Device Mapper", which handles /dev/mapper correctly. A somewhat dirtier way would be to tell the "directory" storage pool type that /dev/mapper/control needs to be handled differently.
Anyway, I need to find a workaround. Any hints?
*** This bug has been marked as a duplicate of bug 710866 ***