Qemu 2.10 added the requirement of a --force-share flag to qemu-img
info when reading information about a disk that is in use by a
guest. We do this a lot in Nova for operations like gathering
information before live migration.
Up until this point all qemu/libvirt version matching has been solely
inside the libvirt driver, however all the image manip code was moved
out to nova.virt.images. We need the version of QEMU available there.
This does it by initializing that version on driver init host. The net
effect is also that broken libvirt connections are figured out
earlier, as there is an active probe for this value.
Reviewed: https:/ /review. openstack. org/505673 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=807579755c4 a116309eca5b2bc dbab9d1f393bab
Committed: https:/
Submitter: Zuul
Branch: master
commit 807579755c4a116 309eca5b2bcdbab 9d1f393bab
Author: Matt Riedemann <email address hidden>
Date: Wed Sep 20 10:44:11 2017 -0400
Support qemu >= 2.10
Qemu 2.10 added the requirement of a --force-share flag to qemu-img
info when reading information about a disk that is in use by a
guest. We do this a lot in Nova for operations like gathering
information before live migration.
Up until this point all qemu/libvirt version matching has been solely
inside the libvirt driver, however all the image manip code was moved
out to nova.virt.images. We need the version of QEMU available there.
This does it by initializing that version on driver init host. The net
effect is also that broken libvirt connections are figured out
earlier, as there is an active probe for this value.
Co-Authored-By: Sean Dague <email address hidden>
Change-Id: Iae2962bb86100f 03fd3ad9aac3767 da876291e74
Closes-Bug: #1718295