On 02/02/2016 07:05 AM, Christoffer Dall wrote:
I'm not familiar enough with libvirt, nor the use of QMP, to really argue one way or another, but I find it a bit strange that we'd prefer libvirt to query two entities over one. And, why should the libvirt installed on a particular host prefer gicv3 as the default, just because KVM supports it, even when QEMU does not?
I think the assumption here is that if you install a recent libvirt you also install a recent QEMU. You always have the risk of things not working if you have too old a QEMU, right?
Libvirt exists for providing back-compat glue. The following combinations are supported: old libvirt, old qemu new libvirt, old qemu new libvirt, new qemu and it is only this combination that might require a libvirt upgrade to work correctly: old libvirt, new qemu -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org