summaryrefslogtreecommitdiffstats
path: root/nova/utils.py
diff options
context:
space:
mode:
authorYufang Zhang <yufang521247@gmail.com>2013-01-14 21:02:40 +0800
committerYufang Zhang <yufang521247@gmail.com>2013-01-15 11:02:13 +0800
commit2adf6399b43102b5998f4779e6976b2b5296de6f (patch)
treefd237bf7585226cba06197ce3f593007669ad7e3 /nova/utils.py
parentaa18fca87fd4655c47e473639a30a6b61ed88fce (diff)
downloadnova-2adf6399b43102b5998f4779e6976b2b5296de6f.tar.gz
nova-2adf6399b43102b5998f4779e6976b2b5296de6f.tar.xz
nova-2adf6399b43102b5998f4779e6976b2b5296de6f.zip
libvirt: use tap for non-blockdevice images on Xen
This patch reverts 35c4962c0b97bae5b8751d316d5822fe22c1ab6a: 'use file instead of tap for non-blockdevice images on Xen', which breaks qcow2 disk working on Xen. If the method pick_disk_driver_name() returns 'file' for qcow2 format, we would get the following disk XML snippet: <disk type="file" device="disk"> <driver name="file" type="qcow2" cache="none"/> <source file="/data/instances/instance-00000081/disk"/> <target bus="xen" dev="hda"/> </disk> which produces configuration in the xen tools like: "file:/data/instances/instance-00000081/disk,hda,w" Guest would not boot successfully, as Xen doesn't think of disk format as qcow2. Instead, 'tap' works with both raw and qcow2 disk. For LP#1084618, I think it is related with libvirt verion. In my deployment(libvirt-1.0.1), 'tap' dirver could produce correct configuration for both raw and qcow2 disk format. Change-Id: I636b2fed366474e2ae8c3b52403e3085724b24f0
Diffstat (limited to 'nova/utils.py')
0 files changed, 0 insertions, 0 deletions