← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1489194] [NEW] hw_scsi_model from glance image is not used when booting instance from new volume

 

Public bug reported:

When creating an instance backed by a cinder volume, the disk device /dev/vda is used regardless of image settings. I am using the following image metadata to set virtio-scsi driver on my instances:
hw_disk_bus=scsi
hw_scsi_model=virtio-scsi

When I boot instances using a normal root device ("boot from image"),
they are using /dev/sda and virtio-scsi as expected. When booting from
volume (either with a new volume or an existing image-based volume),
they use "<target dev='vda' bus='virtio'/>", ignoring the image
metadata.

According to this spec: http://specs.openstack.org/openstack/nova-
specs/specs/juno/approved/add-virtio-scsi-bus-for-bdm.html

A "work item" was: "Nova retrieve “hw_scsi_model” property from volume’s
glance_image_metadata when booting from cinder volume"

I would expect this work is what would implement setting virtio-scsi on
volume backed instances, however none of the reviews I have looked
through for that spec appear to implement anything regarding volume
backed instances.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1489194

Title:
  hw_scsi_model from glance image is not used when booting instance from
  new volume

Status in OpenStack Compute (nova):
  New

Bug description:
  When creating an instance backed by a cinder volume, the disk device /dev/vda is used regardless of image settings. I am using the following image metadata to set virtio-scsi driver on my instances:
  hw_disk_bus=scsi
  hw_scsi_model=virtio-scsi

  When I boot instances using a normal root device ("boot from image"),
  they are using /dev/sda and virtio-scsi as expected. When booting from
  volume (either with a new volume or an existing image-based volume),
  they use "<target dev='vda' bus='virtio'/>", ignoring the image
  metadata.

  According to this spec: http://specs.openstack.org/openstack/nova-
  specs/specs/juno/approved/add-virtio-scsi-bus-for-bdm.html

  A "work item" was: "Nova retrieve “hw_scsi_model” property from
  volume’s glance_image_metadata when booting from cinder volume"

  I would expect this work is what would implement setting virtio-scsi
  on volume backed instances, however none of the reviews I have looked
  through for that spec appear to implement anything regarding volume
  backed instances.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1489194/+subscriptions


Follow ups