On Tue, Aug 09, 2011 at 11:09:06AM -0400, Cole Robinson wrote:
> On 08/08/2011 04:37 PM, Marc Haber wrote:
> > 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?
>
> cc-ing virt-tool-list
Bcc, or forgotten?
> Latest virt-manager-0.9.0 allows adding a libvirt mpath pool which might
> be what you're looking for. If you don't have that version you can try
> configuring it on the command line with virsh.
I have that version, but an mpath pool set to /dev/mapper stays empty.
Googling and reading the available docs suggests that this feature
only looks for /dev/mapper/mpath*
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
