mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2025-01-09 06:25:19 +00:00
bd3d00babc
When -device is configured via JSON a bug [1] is triggered in qemu were the DEVICE_DELETED event for the removal of the device frontend is no longer delivered to libvirt. Without the DEVICE_DELETED event we don't remove the corresponding entries in the VM XML. Until qemu will be fixed we must stop using the JSON syntax for -device. This patch removes the detection of the capability. The capability is used only during startup of a fresh VM so we don't need to consider any compaitibility steps for existing VMs. For users who wish to use 'libvirt-7.9' and 'libvirt-7.10' with 'qemu-6.2' there are two possible workarounds: - filter out the 'device.json' qemu capability '/etc/libvirt/qemu.conf': capability_filters = [ "device.json" ] - filter out the 'device.json' qemu capability via qemu namespace XML: <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> [...] <qemu:capabilities> <qemu:del capability='device.json'/> </qemu:capabilities> </domain> We must never again use the same capability name as we are now instructing users to filter it as a workaround so once qemu is fixed we'll need to pick a new capability value for it. [1] https://bugzilla.redhat.com/show_bug.cgi?id=2036669 Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=2035237 Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Ani Sinha <ani@anisinha.ca> Reviewed-by: Ján Tomko <jtomko@redhat.com> |
||
---|---|---|
.. | ||
caps_2.11.0.s390x.replies | ||
caps_2.11.0.s390x.xml | ||
caps_2.11.0.x86_64.replies | ||
caps_2.11.0.x86_64.xml | ||
caps_2.12.0.aarch64.replies | ||
caps_2.12.0.aarch64.xml | ||
caps_2.12.0.ppc64.replies | ||
caps_2.12.0.ppc64.xml | ||
caps_2.12.0.s390x.replies | ||
caps_2.12.0.s390x.xml | ||
caps_2.12.0.x86_64.replies | ||
caps_2.12.0.x86_64.xml | ||
caps_3.0.0.ppc64.replies | ||
caps_3.0.0.ppc64.xml | ||
caps_3.0.0.riscv32.replies | ||
caps_3.0.0.riscv32.xml | ||
caps_3.0.0.riscv64.replies | ||
caps_3.0.0.riscv64.xml | ||
caps_3.0.0.s390x.replies | ||
caps_3.0.0.s390x.xml | ||
caps_3.0.0.x86_64.replies | ||
caps_3.0.0.x86_64.xml | ||
caps_3.1.0.ppc64.replies | ||
caps_3.1.0.ppc64.xml | ||
caps_3.1.0.x86_64.replies | ||
caps_3.1.0.x86_64.xml | ||
caps_4.0.0.aarch64.replies | ||
caps_4.0.0.aarch64.xml | ||
caps_4.0.0.ppc64.replies | ||
caps_4.0.0.ppc64.xml | ||
caps_4.0.0.riscv32.replies | ||
caps_4.0.0.riscv32.xml | ||
caps_4.0.0.riscv64.replies | ||
caps_4.0.0.riscv64.xml | ||
caps_4.0.0.s390x.replies | ||
caps_4.0.0.s390x.xml | ||
caps_4.0.0.x86_64.replies | ||
caps_4.0.0.x86_64.xml | ||
caps_4.1.0.x86_64.replies | ||
caps_4.1.0.x86_64.xml | ||
caps_4.2.0.aarch64.replies | ||
caps_4.2.0.aarch64.xml | ||
caps_4.2.0.ppc64.replies | ||
caps_4.2.0.ppc64.xml | ||
caps_4.2.0.s390x.replies | ||
caps_4.2.0.s390x.xml | ||
caps_4.2.0.x86_64.replies | ||
caps_4.2.0.x86_64.xml | ||
caps_5.0.0.aarch64.replies | ||
caps_5.0.0.aarch64.xml | ||
caps_5.0.0.ppc64.replies | ||
caps_5.0.0.ppc64.xml | ||
caps_5.0.0.riscv64.replies | ||
caps_5.0.0.riscv64.xml | ||
caps_5.0.0.x86_64.replies | ||
caps_5.0.0.x86_64.xml | ||
caps_5.1.0.sparc.replies | ||
caps_5.1.0.sparc.xml | ||
caps_5.1.0.x86_64.replies | ||
caps_5.1.0.x86_64.xml | ||
caps_5.2.0.aarch64.replies | ||
caps_5.2.0.aarch64.xml | ||
caps_5.2.0.ppc64.replies | ||
caps_5.2.0.ppc64.xml | ||
caps_5.2.0.riscv64.replies | ||
caps_5.2.0.riscv64.xml | ||
caps_5.2.0.s390x.replies | ||
caps_5.2.0.s390x.xml | ||
caps_5.2.0.x86_64.replies | ||
caps_5.2.0.x86_64.xml | ||
caps_6.0.0.aarch64.replies | ||
caps_6.0.0.aarch64.xml | ||
caps_6.0.0.s390x.replies | ||
caps_6.0.0.s390x.xml | ||
caps_6.0.0.x86_64.replies | ||
caps_6.0.0.x86_64.xml | ||
caps_6.1.0.x86_64.replies | ||
caps_6.1.0.x86_64.xml | ||
caps_6.2.0.aarch64.replies | ||
caps_6.2.0.aarch64.xml | ||
caps_6.2.0.ppc64.replies | ||
caps_6.2.0.ppc64.xml | ||
caps_6.2.0.x86_64.replies | ||
caps_6.2.0.x86_64.xml |