Seems like different libvirt versions generate a storage volume name in
different format. We would like to learn how libvirt names a storage
volume under a block based storage pool. So that we may properly extract
the LUN identifier out of the volume name for now and in the future.
On host A l
On Tue, Aug 09, 2011 at 12:45:06PM -0400, Cole Robinson wrote:
> Not really sure then, maybe this is something that libvirt should be
> extended to handle. CCing libvirt devel list
Please note that I am only subscribed to libvirt-users, please Cc me
on replies.
There is also https://bugzilla.redh
On 08/09/2011 12:31 PM, Marc Haber wrote:
> 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
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 b
On 08/08/2011 04:37 PM, Marc Haber wrote:
> 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.
>
>
