Re: [libvirt] [PATCH v2] qemu: don't use deprecated -no-kvm-pit-reinjection

>> if (qemuCaps->arch == VIR_ARCH_X86_64 || >> qemuCaps->arch == VIR_ARCH_I686) { >> virQEMUCapsSet(qemuCaps, QEMU_CAPS_PCI_MULTIBUS); >> virQEMUCapsSet(qemuCaps, QEMU_CAPS_NO_ACPI); >> - virQEMUCapsSet(qemuCaps, QEMU_CAPS_NO_KVM_PIT); > > This part seems dubious, like it might break upgrades. If an older > libvirt says that qemu has a feature, and a VM is running, then when you > upgrade libvirtd and the feature is no longer provided by qemu, then > libvirtd may silently drop the domain definition because it can't find a > qemu binary that supports the same features as were required by the > older libvirtd. It shouldn't hurt to leave this cap bit set, even if > the rest of this patch is about avoiding the need to rely on this cap bit. That shouldn't happen I think. For any runing guest, we have recorded the original capabilities in the domain status XML file. So any caps we detect against QEMU binaries upon restart will only impact newly started guests.