With Havana+ you should be able to use the new block_device_mapping code to
specify a particular bus during launch, but for Grizzly you can specify the bus
by setting metadata on the image in glance.
glance image-update uuid --property hw_disk_bus=ide
There are a few properites like this, see
https://wiki.openstack.org/wiki/LibvirtCustomHardware
Vish
On Sep 20, 2013, at 6:30 PM, Pattabi Ayyasami patt...@brocade.com wrote:
Hi,
We have a KVM qcow2 image to be launched on a KVM host. From Dashboard, I
don’t find a way to specify the disk type for a new instance as IDE. The
instance was launched with a virtio disk type.
virsh dumpxml kvm_vm_name
shows the following.
….
disk type='file' device='disk'
driver name='qemu' type='qcow2' cache='none'/
source
file='/opt/stack/data/nova/instances/2f317b2e-f3b8-40cd-ba79-402231ccee51/disk'/
target dev='vda' bus='virtio'/
address type='pci' domain='0x' bus='0x00' slot='0x08'
function='0x0'/
/disk
….
I want it to be
target dev=’vda’ bus=’ide’/
address type='drive' controller='0' bus='0' unit='0'/
The libvirt.xml under data/nova/instances/image_id
….
disk type=file device=disk
driver name=qemu type=qcow2 cache=none/
source
file=/opt/stack/data/nova/instances/2f317b2e-f3b8-40cd-ba79-402231ccee51/disk/
target bus=virtio dev=vda/
/disk
….
I want it to be
target bus=”ide” dev=vda”/
I could manually change libvirt.xml and virsh edit kvm_vm_name as
mentioned above. But I want to be able to do it either from Dashboard GUI or
commands such as glance or nova.
Does anyone have any pointers on workarounds / solution on this?
Thanks
Pattabi
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev