virt-manager - how to add /dev/mapper as a storage pool

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I would like to be able to configure VMs running off dm-crypt devices
that were unlocked in the host. Unlocked dm-crypt devices show up in
/dev/mapper/devicename, with devicename being the second parameter
given to cryptsetup luksOpen.

The LVM storage pool type insists on searching in /dev/vgname and
cannot be tricked into reading /dev/mapper by giving it a fake VG
named mapper; the LVM storage pool type "dir" mishandles
/dev/mapper/control ("illegal seek").

Is there a workaround to be able to use such devices in virt-manager
without having to define a single storage pool for every device used?

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things."    Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature |  How to make an American Quilt | Fax: *49 3221 2323190


[Index of Archives]     [Virt Tools]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux