VMware: volume create ignores adapter_type
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Medium
|
Vipin Balachandran |
Bug Description
I believe this issue is part of the root cause for this nova bug: https:/
Basically, when creating a volume from a vmdk image, the adapter_type is ignored and it defaults to LSI logic.
https:/
https:/
So cinder creates a volume with LSI SCSI controller and IDE disk. And eventually, when I try to boot from a volume in Nova, I get "No operating system found". I don't think you can boot an IDE disk using SCSI adapter.
However, I am able to boot from an image with IDE adapter. So seems the volume step is causing an issue.
My recreate steps:
1) glance image-create --name cirros-sparse --is-public=True --container-
2) cinder create --name sparse-ide --image-id cd0a8dea-
3) Observe in vCenter that the newly created volume has adapter set as LSI logic.
My VMDK image metadata:
KDMV?9??
# Disk DescriptorFile
version=1
CID=5269c92d
parentCID=ffffffff
createType=
# Extent description
RW 80325 SPARSE "disk-vmdk.vmdk"
ericwb@
head: 20disk-vmdk.vmdk: invalid number of lines
ericwb@
KDMV?9??
# Disk DescriptorFile
version=1
CID=5269c92d
parentCID=ffffffff
createType=
# Extent description
RW 80325 SPARSE "disk-vmdk.vmdk"
# The Disk Data Base
#DDB
ddb.virtualHWVe
ddb.geometry.
ddb.geometry.heads = "16"
ddb.geometry.
ddb.adapterType = "ide"
Changed in cinder: | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → Vipin Balachandran (vbala) |
tags: | added: vmdk |
Changed in cinder: | |
importance: | High → Medium |
tags: |
added: drivers removed: vmdk |
Changed in cinder: | |
milestone: | none → juno-3 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | juno-3 → 2014.2 |
Its not just the adapter_type affecting the boot of the volume. It appears the sparse tag is also causing an issue. I know because I tweaked my cinder devstack to acknowledge IDE. So handling sparse would also have to be part of this fix.
From my testing, you should be able to create a volume in Openstack and manually start the VM for the volume in vCenter without error. This is not true of this sparse-ide image. https:/ /www.dropbox. com/s/793n37blb 4ra3t6/ disk-vmdk. vmdk