Open Stack

Honestly, I dont know. I dont use either. Just heard it was broken in kvm, but it was there because of xen.

Thanks,
Kevin

________________________________
From: Géza Gémes
Sent: Sunday, May 24, 2015 1:07:01 AM
To: openstack-dev at lists.openstack.org
Subject: Re: [openstack-dev] [nova] usefulness of device parameter at volumeAttachment

libvirt/xen or xenapi? PVM or HVM?

Thank you!

Geza

On 05/23/2015 02:21 PM, Fox, Kevin M wrote:
I believe xen supports it.

Thanks,
Kevin

________________________________
From: Géza Gémes
Sent: Saturday, May 23, 2015 2:00:32 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [nova] usefulness of device parameter at volumeAttachment

Hi,

When someone calls nova volume-attach or the block-device-mapping
parameter at boot, it is possible to specify a device name for the
guest. However I couldn't find any guest OS which would honor this. E.g.
with libvirt/kvm, if the guest has two virtio disks already (vda and
vdb), specifying vdf would be ignored and the disk will be attached as
vdc in the guest.
I propose to deprecate this option and at boot where it is not optional
to accept only auto as an option.

Best regards,

Geza

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<mailto:OpenStack-dev-request at lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<mailto:OpenStack-dev-request at lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150524/b8dd185d/attachment.html>