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: Iae2962bb86100f03fd3ad9aac3767da876291e74
Closes-Bug: #1718295
(cherry picked from commit 807579755c4a116309eca5b2bcdbab9d1f393bab)
Reviewed: https:/ /review. openstack. org/509774 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=5e9508b77f8 6f1fadb173a071e 2519aad24534f9
Committed: https:/
Submitter: Jenkins
Branch: stable/pike
commit 5e9508b77f86f1f adb173a071e2519 aad24534f9
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 309eca5b2bcdbab 9d1f393bab)
Closes-Bug: #1718295
(cherry picked from commit 807579755c4a116