July 2026 - Devel - libvirt List Archives

[PATCH 0/7] qemu: Update qemu capabilities and use new monitor syntax
by Peter Krempa 16 Jul '26

16 Jul '26

Peter Krempa (7): qemucapabilitiestest: Update 'caps_11.1.0_x86_64' to 'v11.1.0-rc0' qemucapabilitiestest: Update 'caps_11.1.0_aarch64' to 'v11.1.0-rc0' qemuMonitorJSONIOProcessLine: Log monitor object pointer in debug message qemu: monitor: Standardize log format in QEMU_CHECK_MONITOR_FULL macro qemu: capabilities: Introduce QEMU_CAPS_OBJECT_MONITOR_QMP qemu: command: Use monitor via '-object monitor-qmp,...' qemuxmlconftest: Add a note that the pinned CPU model tests test also old-style QMP monitor instantation src/qemu/qemu_capabilities.c | 2 + src/qemu/qemu_capabilities.h | 1 + src/qemu/qemu_command.c | 17 +- src/qemu/qemu_monitor.c | 2 +- src/qemu/qemu_monitor_json.c | 2 +- .../qemu_11.1.0-q35.x86_64-expanded.xml | 1 + .../qemu_11.1.0-q35.x86_64-supported.xml | 1 + .../domaincapsdata/qemu_11.1.0-q35.x86_64.xml | 1 + tests/domaincapsdata/qemu_11.1.0.x86_64.xml | 1 + .../caps_11.1.0_aarch64.replies | 2026 +++++++++-------- .../caps_11.1.0_aarch64.xml | 5 +- .../caps_11.1.0_x86_64.replies | 1996 ++++++++-------- .../caps_11.1.0_x86_64.xml | 7 +- ...arch64-cpu-passthrough.aarch64-latest.args | 2 +- ...ault-cpu-kvm-virt-10.0.aarch64-latest.args | 2 +- ...ault-cpu-tcg-virt-10.0.aarch64-latest.args | 2 +- ...aarch64-features-pauth.aarch64-latest.args | 2 +- .../aarch64-features-ras.aarch64-latest.args | 2 +- .../aarch64-features-sve.aarch64-latest.args | 2 +- ...rch64-gic-default-both.aarch64-latest.args | 2 +- ...aarch64-gic-default-v2.aarch64-latest.args | 2 +- ...aarch64-gic-default-v3.aarch64-latest.args | 2 +- .../aarch64-gic-default.aarch64-latest.args | 2 +- .../aarch64-gic-host.aarch64-latest.args | 2 +- .../aarch64-gic-none-both.aarch64-latest.args | 2 +- .../aarch64-gic-none-tcg.aarch64-latest.args | 2 +- .../aarch64-gic-none-v2.aarch64-latest.args | 2 +- .../aarch64-gic-none-v3.aarch64-latest.args | 2 +- .../aarch64-gic-none.aarch64-latest.args | 2 +- .../aarch64-gic-v2.aarch64-latest.args | 2 +- .../aarch64-gic-v3.aarch64-latest.args | 2 +- .../aarch64-kvm-32-on-64.aarch64-latest.args | 2 +- ...usb-minimal.aarch64-latest.abi-update.args | 2 +- .../aarch64-nousb-minimal.aarch64-latest.args | 2 +- .../aarch64-pci-serial.aarch64-latest.args | 2 +- ...iew-minimal.aarch64-latest.abi-update.args | 2 +- ...rch64-realview-minimal.aarch64-latest.args | 2 +- ...arch64-traditional-pci.aarch64-latest.args | 2 +- ...aarch64-usb-controller.aarch64-latest.args | 2 +- .../aarch64-video-default.aarch64-latest.args | 2 +- ...4-video-virtio-gpu-pci.aarch64-latest.args | 2 +- ...ault-models.aarch64-latest.abi-update.args | 2 +- ...64-virt-default-models.aarch64-latest.args | 2 +- ...rch64-virt-default-nic.aarch64-latest.args | 2 +- .../aarch64-virt-graphics.aarch64-latest.args | 2 +- ...h64-virt-headless-mmio.aarch64-latest.args | 2 +- .../aarch64-virt-headless.aarch64-latest.args | 2 +- ...irt-minimal.aarch64-latest.abi-update.args | 2 +- .../aarch64-virt-minimal.aarch64-latest.args | 2 +- .../aarch64-virt-virtio.aarch64-latest.args | 2 +- ...64-virt-virtualization.aarch64-latest.args | 2 +- ...o-pci-manual-addresses.aarch64-latest.args | 2 +- .../acpi-generic-initiator.x86_64-latest.args | 2 +- .../acpi-table-many.x86_64-latest.args | 2 +- .../acpi-table.x86_64-latest.args | 2 +- .../amd-iommu.x86_64-latest.args | 2 +- .../arm-vexpressa9-basic.aarch64-latest.args | 2 +- .../arm-vexpressa9-nodevs.aarch64-latest.args | 2 +- .../arm-vexpressa9-virtio.aarch64-latest.args | 2 +- .../async-teardown.x86_64-latest.args | 2 +- .../audio-alsa-best.x86_64-latest.args | 2 +- .../audio-alsa-full.x86_64-latest.args | 2 +- .../audio-alsa-minimal.x86_64-latest.args | 2 +- .../audio-coreaudio-best.x86_64-latest.args | 2 +- .../audio-coreaudio-full.x86_64-latest.args | 2 +- ...audio-coreaudio-minimal.x86_64-latest.args | 2 +- ...udio-default-nographics.x86_64-latest.args | 2 +- .../audio-default-sdl.x86_64-latest.args | 2 +- .../audio-default-spice.x86_64-latest.args | 2 +- .../audio-default-vnc.x86_64-latest.args | 2 +- .../audio-file-best.x86_64-latest.args | 2 +- .../audio-file-full.x86_64-latest.args | 2 +- .../audio-file-minimal.x86_64-latest.args | 2 +- .../audio-jack-full.x86_64-latest.args | 2 +- .../audio-jack-minimal.x86_64-latest.args | 2 +- .../audio-many-backends.x86_64-latest.args | 2 +- .../audio-none-best.x86_64-latest.args | 2 +- .../audio-none-full.x86_64-latest.args | 2 +- .../audio-none-minimal.x86_64-latest.args | 2 +- .../audio-oss-best.x86_64-latest.args | 2 +- .../audio-oss-full.x86_64-latest.args | 2 +- .../audio-oss-minimal.x86_64-latest.args | 2 +- .../audio-pipewire-best.x86_64-latest.args | 2 +- .../audio-pipewire-full.x86_64-latest.args | 2 +- .../audio-pipewire-minimal.x86_64-latest.args | 2 +- .../audio-pulseaudio-best.x86_64-latest.args | 2 +- .../audio-pulseaudio-full.x86_64-latest.args | 2 +- ...udio-pulseaudio-minimal.x86_64-latest.args | 2 +- .../audio-sdl-best.x86_64-latest.args | 2 +- .../audio-sdl-full.x86_64-latest.args | 2 +- .../audio-sdl-minimal.x86_64-latest.args | 2 +- .../audio-spice-best.x86_64-latest.args | 2 +- .../audio-spice-full.x86_64-latest.args | 2 +- .../audio-spice-minimal.x86_64-latest.args | 2 +- .../autoindex.x86_64-latest.args | 2 +- .../balloon-device-auto.x86_64-latest.args | 2 +- ...loon-device-deflate-off.x86_64-latest.args | 2 +- .../balloon-device-deflate.x86_64-latest.args | 2 +- .../balloon-device-period.x86_64-latest.args | 2 +- .../balloon-device.x86_64-latest.args | 2 +- .../balloon-mmio-deflate.aarch64-latest.args | 2 +- .../blkdeviotune-group-num.x86_64-latest.args | 2 +- ...blkdeviotune-max-length.x86_64-latest.args | 2 +- .../blkdeviotune-max.x86_64-latest.args | 2 +- .../blkdeviotune.x86_64-latest.args | 2 +- .../blkiotune-device.x86_64-latest.args | 2 +- .../blkiotune.x86_64-latest.args | 2 +- .../boot-cdrom.x86_64-latest.args | 2 +- .../boot-complex.x86_64-latest.args | 2 +- .../boot-floppy-q35.x86_64-latest.args | 2 +- .../boot-floppy.x86_64-latest.args | 2 +- ...boot-menu-disable-drive.x86_64-latest.args | 2 +- ...nu-disable-with-timeout.x86_64-latest.args | 2 +- .../boot-menu-disable.x86_64-latest.args | 2 +- ...enu-enable-with-timeout.x86_64-latest.args | 2 +- .../boot-menu-enable.x86_64-latest.args | 2 +- .../boot-multi.x86_64-latest.args | 2 +- .../boot-network.x86_64-latest.args | 2 +- .../boot-order.x86_64-latest.args | 2 +- .../channel-guestfwd.x86_64-latest.args | 2 +- ...l-qemu-vdagent-features.x86_64-latest.args | 2 +- .../channel-qemu-vdagent.x86_64-latest.args | 2 +- .../channel-spicevmc.x86_64-latest.args | 2 +- .../channel-unix-guestfwd.x86_64-latest.args | 2 +- ...hannel-unix-source-path.x86_64-latest.args | 2 +- .../channel-virtio-auto.x86_64-latest.args | 2 +- .../channel-virtio-autoadd.x86_64-latest.args | 2 +- ...annel-virtio-autoassign.x86_64-latest.args | 2 +- .../channel-virtio-default.x86_64-latest.args | 2 +- .../channel-virtio-state.x86_64-latest.args | 2 +- .../channel-virtio-unix.x86_64-latest.args | 2 +- .../channel-virtio.x86_64-latest.args | 2 +- .../chardev-backends-json.x86_64-latest.args | 2 +- .../chardev-backends.x86_64-latest.args | 2 +- .../chardev-label.x86_64-latest.args | 2 +- .../chardev-reconnect.x86_64-latest.args | 2 +- .../clock-absolute.x86_64-latest.args | 2 +- .../clock-catchup.x86_64-latest.args | 2 +- .../clock-france.x86_64-latest.args | 2 +- .../clock-hpet-off.x86_64-latest.args | 2 +- ...caltime-basis-localtime.x86_64-latest.args | 2 +- .../clock-localtime.x86_64-latest.args | 2 +- .../clock-realtime.x86_64-latest.args | 2 +- .../clock-timer-armvtimer.aarch64-latest.args | 2 +- .../clock-timer-hyperv-rtc.x86_64-latest.args | 2 +- .../clock-utc.x86_64-latest.args | 2 +- .../clock-variable.x86_64-latest.args | 2 +- .../console-compat-auto.x86_64-latest.args | 2 +- .../console-compat-chardev.x86_64-latest.args | 2 +- .../console-compat-crash.x86_64-latest.args | 2 +- .../console-compat.x86_64-latest.args | 2 +- .../console-compat2.x86_64-latest.args | 2 +- .../console-virtio-many.x86_64-latest.args | 2 +- ...rial-autoassign-address.x86_64-latest.args | 2 +- .../console-virtio-unix.x86_64-latest.args | 2 +- .../console-virtio.x86_64-latest.args | 2 +- .../controller-order.x86_64-latest.args | 2 +- .../controller-scsi-auto.x86_64-latest.args | 2 +- ...ller-scsi-inherit-model.x86_64-latest.args | 2 +- .../controller-usb-order.x86_64-latest.args | 2 +- .../controller-virtio-scsi.x86_64-latest.args | 2 +- .../cpu-Haswell-noTSX.x86_64-latest.args | 2 +- .../cpu-Haswell.x86_64-latest.args | 2 +- .../cpu-Haswell2.x86_64-latest.args | 2 +- .../cpu-Haswell3.x86_64-latest.args | 2 +- ...-Icelake-Server-pconfig.x86_64-latest.args | 2 +- .../cpu-cache-disable.x86_64-latest.args | 2 +- .../cpu-cache-disable3.x86_64-latest.args | 2 +- .../cpu-cache-emulate-l3.x86_64-latest.args | 2 +- .../cpu-cache-passthrough.x86_64-latest.args | 2 +- .../cpu-check-default-none.x86_64-latest.args | 2 +- ...cpu-check-default-none2.x86_64-latest.args | 2 +- ...u-check-default-partial.x86_64-latest.args | 2 +- ...-check-default-partial2.x86_64-latest.args | 2 +- .../cpu-check-none.x86_64-latest.args | 2 +- .../cpu-empty.x86_64-latest.args | 2 +- .../cpu-eoi-disabled.x86_64-latest.args | 2 +- .../cpu-eoi-enabled.x86_64-latest.args | 2 +- .../cpu-exact1.x86_64-latest.args | 2 +- .../cpu-exact2-nofallback.x86_64-latest.args | 2 +- .../cpu-exact2.x86_64-latest.args | 2 +- .../cpu-host-kvmclock.x86_64-latest.args | 2 +- .../cpu-host-model-cmt.x86_64-latest.args | 2 +- ...host-model-fallback-kvm.x86_64-latest.args | 4 +- ...host-model-fallback-tcg.x86_64-latest.args | 2 +- ...cpu-host-model-features.x86_64-latest.args | 4 +- .../cpu-host-model-kvm.x86_64-latest.args | 4 +- ...st-model-nofallback-kvm.x86_64-latest.args | 4 +- ...st-model-nofallback-tcg.x86_64-latest.args | 2 +- .../cpu-host-model-tcg.x86_64-latest.args | 2 +- .../cpu-host-model-vendor.x86_64-latest.args | 2 +- ...st-passthrough-features.x86_64-latest.args | 2 +- .../cpu-host-passthrough.x86_64-latest.args | 2 +- .../cpu-hotplug-startup.x86_64-latest.args | 2 +- .../cpu-kvmclock.x86_64-latest.args | 2 +- .../cpu-minimum1.x86_64-latest.args | 2 +- .../cpu-minimum2.x86_64-latest.args | 2 +- ...cpu-no-removed-features.x86_64-latest.args | 2 +- .../cpu-numa-disjoint.x86_64-latest.args | 2 +- .../cpu-numa-disordered.x86_64-latest.args | 2 +- .../cpu-numa-memshared.x86_64-latest.args | 2 +- ...-numa-no-memory-element.x86_64-latest.args | 2 +- .../cpu-numa1.x86_64-latest.args | 2 +- .../cpu-numa2.x86_64-latest.args | 2 +- ...-phys-bits-emulate-bare.x86_64-latest.args | 2 +- .../cpu-phys-bits-emulate.x86_64-latest.args | 2 +- .../cpu-phys-bits-emulate2.x86_64-latest.args | 2 +- .../cpu-phys-bits-limit.x86_64-latest.args | 2 +- ...u-phys-bits-passthrough.x86_64-latest.args | 2 +- .../cpu-strict1.x86_64-latest.args | 2 +- .../cpu-topology1.x86_64-latest.args | 2 +- .../cpu-topology2.x86_64-latest.args | 2 +- .../cpu-topology3.x86_64-latest.args | 2 +- .../cpu-topology4.x86_64-latest.args | 2 +- .../cpu-topology5.aarch64-latest.args | 2 +- .../cpu-translation.x86_64-latest.args | 2 +- .../cpu-tsc-frequency.x86_64-latest.args | 2 +- .../cputune-cpuset-big-id.x86_64-latest.args | 2 +- .../cputune-numatune.x86_64-latest.args | 2 +- .../cputune-zero-shares.x86_64-latest.args | 2 +- .../cputune.x86_64-latest.args | 2 +- .../crypto-builtin.x86_64-latest.args | 2 +- .../default-kvm-host-arch.x86_64-latest.args | 2 +- .../default-qemu-host-arch.x86_64-latest.args | 2 +- ...ult-video-type-aarch64.aarch64-latest.args | 2 +- ...fault-video-type-x86_64.x86_64-latest.args | 2 +- .../devices-acpi-index.x86_64-latest.args | 2 +- .../disk-active-commit.x86_64-latest.args | 2 +- .../disk-aio-io_uring.x86_64-latest.args | 2 +- .../disk-aio.x86_64-latest.args | 2 +- .../disk-arm-virtio-sd.aarch64-latest.args | 2 +- ...-backing-chains-noindex.x86_64-latest.args | 2 +- ...disk-blockio-no-discard.x86_64-latest.args | 2 +- .../disk-blockio.x86_64-latest.args | 2 +- .../disk-boot-cdrom.x86_64-latest.args | 2 +- .../disk-boot-disk.x86_64-latest.args | 2 +- .../disk-cache.x86_64-latest.args | 2 +- ...m-empty-network-invalid.x86_64-latest.args | 2 +- ...sk-cdrom-network-nbdkit.x86_64-latest.args | 2 +- .../disk-cdrom-network.x86_64-latest.args | 2 +- .../disk-cdrom-tray.x86_64-latest.args | 2 +- ...om-usb-empty.x86_64-latest.abi-update.args | 2 +- .../disk-cdrom.x86_64-latest.args | 2 +- .../disk-copy_on_read.x86_64-latest.args | 2 +- .../disk-detect-zeroes.x86_64-latest.args | 2 +- .../disk-discard.x86_64-latest.args | 2 +- .../disk-discard_no_unref.x86_64-latest.args | 2 +- .../disk-error-policy.x86_64-latest.args | 2 +- .../disk-floppy-q35.x86_64-latest.args | 2 +- .../disk-floppy-tray.x86_64-latest.args | 2 +- .../disk-floppy.x86_64-latest.args | 2 +- .../disk-fmt-qcow.x86_64-latest.args | 2 +- .../disk-geometry.x86_64-latest.args | 2 +- .../disk-ide-split.x86_64-latest.args | 2 +- .../disk-ide-wwn.x86_64-latest.args | 2 +- .../disk-ioeventfd.x86_64-latest.args | 2 +- .../disk-metadata-cache.x86_64-latest.args | 2 +- .../disk-mirror-old.x86_64-latest.args | 2 +- .../disk-mirror.x86_64-latest.args | 2 +- ...isk-network-http-nbdkit.x86_64-latest.args | 2 +- .../disk-network-http.x86_64-latest.args | 2 +- .../disk-network-iscsi.x86_64-latest.args | 2 +- .../disk-network-nbd.x86_64-latest.args | 2 +- .../disk-network-nfs.x86_64-latest.args | 2 +- ...rbd-encryption-layering.x86_64-latest.args | 2 +- ...rbd-encryption-luks-any.x86_64-latest.args | 2 +- ...-network-rbd-encryption.x86_64-latest.args | 2 +- ...sk-network-rbd-no-colon.x86_64-latest.args | 2 +- .../disk-network-rbd.x86_64-latest.args | 2 +- ...isk-network-source-auth.x86_64-latest.args | 2 +- ...rce-curl-nbdkit-backing.x86_64-latest.args | 2 +- ...work-source-curl-nbdkit.x86_64-latest.args | 2 +- ...isk-network-source-curl.x86_64-latest.args | 2 +- .../disk-network-ssh-key.x86_64-latest.args | 2 +- ...disk-network-ssh-nbdkit.x86_64-latest.args | 2 +- ...sk-network-ssh-password.x86_64-latest.args | 2 +- .../disk-network-ssh.x86_64-latest.args | 2 +- ...rk-tlsx509-nbd-hostname.x86_64-latest.args | 2 +- ...isk-network-tlsx509-nbd.x86_64-latest.args | 2 +- .../disk-no-boot.x86_64-latest.args | 2 +- .../disk-nvme.x86_64-latest.args | 2 +- .../disk-order.x86_64-latest.args | 2 +- ...sk-qcow2-datafile-store.x86_64-latest.args | 2 +- .../disk-readonly-disk.x86_64-latest.args | 2 +- .../disk-rotation.x86_64-latest.args | 2 +- .../disk-sata-device.x86_64-latest.args | 2 +- .../disk-sata-product.x86_64-latest.args | 2 +- .../disk-scsi-device-auto.x86_64-latest.args | 2 +- .../disk-scsi-disk-split.x86_64-latest.args | 2 +- .../disk-scsi-disk-vpd.x86_64-latest.args | 2 +- .../disk-scsi-disk-wwn.x86_64-latest.args | 2 +- ...sk-scsi-lun-passthrough.x86_64-latest.args | 2 +- .../disk-scsi.x86_64-latest.args | 2 +- .../disk-serial.x86_64-latest.args | 2 +- .../disk-shared.x86_64-latest.args | 2 +- .../disk-slices.x86_64-latest.args | 2 +- .../disk-snapshot.x86_64-latest.args | 2 +- .../disk-source-fd.x86_64-latest.args | 2 +- .../disk-source-pool-mode.x86_64-latest.args | 2 +- .../disk-source-pool.x86_64-latest.args | 2 +- ...tuppolicy-optional-drop.x86_64-latest.args | 2 +- ...sk-statistics-intervals.x86_64-latest.args | 2 +- .../disk-target-nvme.x86_64-latest.args | 2 +- .../disk-transient.x86_64-latest.args | 2 +- .../disk-usb-device-model.x86_64-latest.args | 2 +- ...est.QEMU_CAPS_DEVICE_USB_BOT-disabled.args | 2 +- ...ate.QEMU_CAPS_DEVICE_USB_BOT-disabled.args | 2 +- ...k-usb-device.x86_64-latest.abi-update.args | 2 +- .../disk-usb-device.x86_64-latest.args | 2 +- .../disk-vhostuser-numa.x86_64-latest.args | 2 +- .../disk-vhostuser.x86_64-latest.args | 2 +- .../disk-vhostvdpa.x86_64-latest.args | 2 +- .../disk-virtio-queues.x86_64-latest.args | 2 +- ...irtio-scsi-reservations.x86_64-latest.args | 2 +- .../disk-virtio.x86_64-latest.args | 2 +- .../downscript.x86_64-latest.args | 2 +- .../encrypted-disk-usage.x86_64-latest.args | 2 +- .../encrypted-disk.x86_64-latest.args | 2 +- .../eoi-disabled.x86_64-latest.args | 2 +- .../eoi-enabled.x86_64-latest.args | 2 +- .../event_idx.x86_64-latest.args | 2 +- ...memory-no-numa-topology.x86_64-latest.args | 2 +- ...fd-memory-numa-topology.x86_64-latest.args | 2 +- ...d-memory-numa-topology2.x86_64-latest.args | 2 +- ...d-memory-numa-topology3.x86_64-latest.args | 2 +- ...d-memory-numa-topology4.x86_64-latest.args | 2 +- .../fips-enabled.x86_64-latest.args | 2 +- ...are-auto-bios-stateless.x86_64-latest.args | 2 +- .../firmware-auto-bios.x86_64-latest.args | 2 +- ...efi-aarch64.aarch64-latest.abi-update.args | 2 +- ...mware-auto-efi-aarch64.aarch64-latest.args | 2 +- ...-enrolled-keys-aarch64.aarch64-latest.args | 2 +- ...-auto-efi-enrolled-keys.x86_64-latest.args | 2 +- ...loader-qcow2-nvram-path.x86_64-latest.args | 2 +- ...efi-format-loader-qcow2.x86_64-latest.args | 2 +- ...-loader-raw.aarch64-latest.abi-update.args | 2 +- ...-efi-format-loader-raw.aarch64-latest.args | 2 +- ...uto-efi-format-mismatch.x86_64-latest.args | 2 +- ...nvram-qcow2-network-nbd.x86_64-latest.args | 2 +- ...format-nvram-qcow2-path.x86_64-latest.args | 2 +- ...-efi-format-nvram-qcow2.x86_64-latest.args | 2 +- ...t-nvram-raw-loader-path.x86_64-latest.args | 2 +- ...-raw-nvramtemplate-path.x86_64-latest.args | 2 +- ...at-nvram-raw.x86_64-latest.abi-update.args | 2 +- ...to-efi-format-nvram-raw.x86_64-latest.args | 2 +- ...mat-nvramtemplate-qcow2.x86_64-latest.args | 2 +- ...uto-efi-loader-insecure.x86_64-latest.args | 2 +- ...re-auto-efi-loader-path.x86_64-latest.args | 2 +- ...oader-secure.x86_64-latest.abi-update.args | 2 +- ...-auto-efi-loader-secure.x86_64-latest.args | 2 +- ...to-efi-no-enrolled-keys.x86_64-latest.args | 2 +- ...are-auto-efi-no-secboot.x86_64-latest.args | 2 +- ...are-auto-efi-nvram-file.x86_64-latest.args | 2 +- ...efi-nvram-network-iscsi.x86_64-latest.args | 2 +- ...o-efi-nvram-network-nbd.x86_64-latest.args | 2 +- ...are-auto-efi-nvram-path.x86_64-latest.args | 2 +- ...auto-efi-nvram-template.x86_64-latest.args | 2 +- ...ware-auto-efi-rw-pflash.x86_64-latest.args | 2 +- .../firmware-auto-efi-rw.x86_64-latest.args | 2 +- ...rmware-auto-efi-secboot.x86_64-latest.args | 2 +- ...rmware-auto-efi-smm-off.x86_64-latest.args | 2 +- ...ware-auto-efi-stateless.x86_64-latest.args | 2 +- ...o-efi-varstore-aarch64.aarch64-latest.args | 2 +- ...e-auto-efi-varstore-q35.x86_64-latest.args | 2 +- ...are-auto-efi.x86_64-latest.abi-update.args | 2 +- .../firmware-auto-efi.x86_64-latest.args | 2 +- ...nual-bios-not-stateless.x86_64-latest.args | 2 +- ...e-manual-bios-stateless.x86_64-latest.args | 2 +- .../firmware-manual-bios.x86_64-latest.args | 2 +- ...i-aarch64-legacy-paths.aarch64-latest.args | 2 +- ...anual-efi-acpi-aarch64.aarch64-latest.args | 2 +- ...are-manual-efi-acpi-q35.x86_64-latest.args | 2 +- ...are-manual-efi-features.x86_64-latest.args | 2 +- ...loader-path-nonstandard.x86_64-latest.args | 2 +- ...anual-efi-loader-secure.x86_64-latest.args | 2 +- ...olled-keys-legacy-paths.x86_64-latest.args | 2 +- ...al-efi-no-enrolled-keys.x86_64-latest.args | 2 +- ...no-secboot-legacy-paths.x86_64-latest.args | 2 +- ...e-manual-efi-no-secboot.x86_64-latest.args | 2 +- ...ual-efi-noacpi-aarch64.aarch64-latest.args | 2 +- ...e-manual-efi-nvram-file.x86_64-latest.args | 2 +- ...efi-nvram-network-iscsi.x86_64-latest.args | 2 +- ...l-efi-nvram-network-nbd.x86_64-latest.args | 2 +- ...late-nonstandard-format.x86_64-latest.args | 2 +- ...onstandard-legacy-paths.x86_64-latest.args | 2 +- ...am-template-nonstandard.x86_64-latest.args | 2 +- ...nual-efi-nvram-template.x86_64-latest.args | 2 +- ...-manual-efi-rw-implicit.x86_64-latest.args | 2 +- ...ual-efi-rw-legacy-paths.x86_64-latest.args | 2 +- ...ual-efi-rw-modern-paths.x86_64-latest.args | 2 +- .../firmware-manual-efi-rw.x86_64-latest.args | 2 +- ...fi-secboot-legacy-paths.x86_64-latest.args | 2 +- ...ware-manual-efi-secboot.x86_64-latest.args | 2 +- ...re-manual-efi-stateless.x86_64-latest.args | 2 +- ...l-efi-varstore-aarch64.aarch64-latest.args | 2 +- ...manual-efi-varstore-q35.x86_64-latest.args | 2 +- .../firmware-manual-efi.x86_64-latest.args | 2 +- ...e-manual-noefi-acpi-q35.x86_64-latest.args | 2 +- ...l-noefi-noacpi-aarch64.aarch64-latest.args | 2 +- ...manual-noefi-noacpi-q35.x86_64-latest.args | 2 +- .../floppy-drive-fat.x86_64-latest.args | 2 +- tests/qemuxmlconfdata/fs9p.x86_64-latest.args | 2 +- .../genid-auto.x86_64-latest.args | 2 +- .../qemuxmlconfdata/genid.x86_64-latest.args | 2 +- .../graphics-dbus-address.x86_64-latest.args | 2 +- .../graphics-dbus-audio.x86_64-latest.args | 2 +- .../graphics-dbus-chardev.x86_64-latest.args | 2 +- .../graphics-dbus-p2p.x86_64-latest.args | 2 +- .../graphics-dbus-usbredir.x86_64-latest.args | 2 +- .../graphics-dbus.x86_64-latest.args | 2 +- ...egl-headless-rendernode.x86_64-latest.args | 2 +- .../graphics-egl-headless.x86_64-latest.args | 2 +- ...graphics-listen-network.x86_64-latest.args | 2 +- .../graphics-rdp.x86_64-latest.args | 2 +- ...graphics-sdl-fullscreen.x86_64-latest.args | 2 +- .../graphics-sdl.x86_64-latest.args | 2 +- ...s-spice-agent-file-xfer.x86_64-latest.args | 2 +- ...aphics-spice-agentmouse.x86_64-latest.args | 2 +- ...s-spice-auto-socket-cfg.x86_64-latest.args | 2 +- ...phics-spice-auto-socket.x86_64-latest.args | 2 +- ...phics-spice-compression.x86_64-latest.args | 2 +- ...hics-spice-egl-headless.x86_64-latest.args | 2 +- ...pice-gl-auto-rendernode.x86_64-latest.args | 2 +- .../graphics-spice-no-args.x86_64-latest.args | 2 +- .../graphics-spice-qxl-vga.x86_64-latest.args | 2 +- .../graphics-spice-sasl.x86_64-latest.args | 2 +- .../graphics-spice-socket.x86_64-latest.args | 2 +- .../graphics-spice-timeout.x86_64-latest.args | 2 +- ...raphics-spice-usb-redir.x86_64-latest.args | 2 +- .../graphics-spice.x86_64-latest.args | 2 +- ...ics-vnc-auto-socket-cfg.x86_64-latest.args | 2 +- ...raphics-vnc-auto-socket.x86_64-latest.args | 2 +- ...aphics-vnc-egl-headless.x86_64-latest.args | 2 +- ...hics-vnc-no-listen-attr.x86_64-latest.args | 2 +- .../graphics-vnc-none.x86_64-latest.args | 2 +- .../graphics-vnc-policy.x86_64-latest.args | 2 +- .../graphics-vnc-power.x86_64-latest.args | 2 +- ...remove-generated-socket.x86_64-latest.args | 2 +- .../graphics-vnc-sasl.x86_64-latest.args | 2 +- ...-vnc-socket-new-cmdline.x86_64-latest.args | 2 +- .../graphics-vnc-socket.x86_64-latest.args | 2 +- ...hics-vnc-standalone-p2p.x86_64-latest.args | 2 +- ...s-vnc-standalone-socket.x86_64-latest.args | 2 +- ...graphics-vnc-standalone.x86_64-latest.args | 2 +- ...graphics-vnc-tls-secret.x86_64-latest.args | 2 +- .../graphics-vnc-tls.x86_64-latest.args | 2 +- .../graphics-vnc-websocket.x86_64-latest.args | 2 +- .../graphics-vnc.x86_64-latest.args | 2 +- ...tdev-mdev-display-ramfb.x86_64-latest.args | 2 +- ...play-spice-egl-headless.x86_64-latest.args | 2 +- ...ev-display-spice-opengl.x86_64-latest.args | 2 +- ...isplay-vnc-egl-headless.x86_64-latest.args | 2 +- ...ostdev-mdev-display-vnc.x86_64-latest.args | 2 +- .../hostdev-mdev-display.x86_64-latest.args | 2 +- ...hostdev-mdev-precreated.x86_64-latest.args | 2 +- ...tdev-pci-address-device.x86_64-latest.args | 2 +- ...-pci-address-unassigned.x86_64-latest.args | 2 +- .../hostdev-pci-address.x86_64-latest.args | 2 +- ...stdev-pci-display-ramfb.x86_64-latest.args | 2 +- ...stdev-pci-multifunction.x86_64-latest.args | 2 +- ...ev-scsi-autogen-address.x86_64-latest.args | 2 +- ...hostdev-scsi-large-unit.x86_64-latest.args | 2 +- .../hostdev-scsi-lsi.x86_64-latest.args | 2 +- .../hostdev-scsi-shareable.x86_64-latest.args | 2 +- ...dev-scsi-vhost-scsi-pci.x86_64-latest.args | 2 +- ...ev-scsi-vhost-scsi-pcie.x86_64-latest.args | 2 +- ...ostdev-scsi-virtio-scsi.x86_64-latest.args | 2 +- ...usb-address-device-boot.x86_64-latest.args | 2 +- ...tdev-usb-address-device.x86_64-latest.args | 2 +- ...ostdev-usb-address-port.x86_64-latest.args | 2 +- .../hostdev-usb-address.x86_64-latest.args | 2 +- ...tdev-usb-vendor-product.x86_64-latest.args | 2 +- ...ostdev-vfio-multidomain.x86_64-latest.args | 2 +- .../hostdev-vfio.x86_64-latest.args | 2 +- .../hotplug-base.x86_64-latest.args | 2 +- .../hugepages-default-2M.x86_64-latest.args | 2 +- ...ges-default-system-size.x86_64-latest.args | 2 +- .../hugepages-default.x86_64-latest.args | 2 +- .../hugepages-memaccess.x86_64-latest.args | 2 +- .../hugepages-memaccess2.x86_64-latest.args | 2 +- .../hugepages-memaccess3.x86_64-latest.args | 2 +- .../hugepages-nodeset.x86_64-latest.args | 2 +- ...gepages-numa-default-2M.x86_64-latest.args | 2 +- ...pages-numa-default-dimm.x86_64-latest.args | 2 +- .../hugepages-numa-default.x86_64-latest.args | 2 +- ...pages-numa-nodeset-part.x86_64-latest.args | 2 +- .../hugepages-numa-nodeset.x86_64-latest.args | 2 +- .../hugepages-nvdimm.x86_64-latest.args | 2 +- .../hugepages-shared.x86_64-latest.args | 2 +- .../qemuxmlconfdata/hwuuid.x86_64-latest.args | 2 +- .../hyperv-host-model.x86_64-latest.args | 2 +- .../hyperv-off.x86_64-latest.args | 2 +- .../hyperv-panic.x86_64-latest.args | 2 +- .../hyperv-passthrough.x86_64-latest.args | 2 +- ...-spinlocks-never-notify.x86_64-latest.args | 2 +- .../hyperv-stimer-direct.x86_64-latest.args | 2 +- .../qemuxmlconfdata/hyperv.x86_64-latest.args | 2 +- .../input-linux.x86_64-latest.args | 2 +- .../input-usbmouse-addr.x86_64-latest.args | 2 +- .../input-usbmouse.x86_64-latest.args | 2 +- .../input-usbtablet.x86_64-latest.args | 2 +- .../intel-iommu-aw-bits.x86_64-latest.args | 2 +- ...ntel-iommu-caching-mode.x86_64-latest.args | 2 +- ...ntel-iommu-device-iotlb.x86_64-latest.args | 2 +- ...l-iommu-dma-translation.x86_64-latest.args | 2 +- ...-eim-autoadd.x86_64-latest.abi-update.args | 2 +- .../intel-iommu-eim.x86_64-latest.args | 2 +- .../intel-iommu.x86_64-latest.args | 2 +- ...-smmuv3-pci-bus-single.aarch64-latest.args | 2 +- .../iommu-smmuv3-pci-bus.aarch64-latest.args | 2 +- .../iommu-smmuv3.aarch64-latest.args | 2 +- .../iommufd-q35-fd.x86_64-latest.args | 2 +- .../iommufd-q35.x86_64-latest.args | 2 +- ...fd-virt-pci-bus-single.aarch64-latest.args | 2 +- .../iommufd-virt.aarch64-latest.args | 2 +- .../iommufd.x86_64-latest.args | 2 +- .../iothreads-disk.x86_64-latest.args | 2 +- .../iothreads-ids-partial.x86_64-latest.args | 2 +- ...othreads-ids-pool-sizes.x86_64-latest.args | 2 +- .../iothreads-ids.x86_64-latest.args | 2 +- ...ads-virtio-scsi-mapping.x86_64-latest.args | 2 +- ...threads-virtio-scsi-pci.x86_64-latest.args | 2 +- .../kvm-features-off.x86_64-latest.args | 2 +- .../kvm-features.x86_64-latest.args | 2 +- .../kvm-pit-delay.x86_64-latest.args | 2 +- .../kvm-pit-discard.x86_64-latest.args | 2 +- .../kvmclock+eoi-disabled.x86_64-latest.args | 2 +- .../kvmclock.x86_64-latest.args | 2 +- ...nch-security-sev-direct.x86_64-latest.args | 2 +- ...launch-security-sev-snp.x86_64-latest.args | 2 +- .../qemuxmlconfdata/lease.x86_64-latest.args | 2 +- ...luks-disks-source-qcow2.x86_64-latest.args | 2 +- .../luks-disks-source.x86_64-latest.args | 2 +- .../luks-disks.x86_64-latest.args | 2 +- ...ch-virt-console-native.aarch64-latest.args | 2 +- ...ch-virt-console-virtio.aarch64-latest.args | 2 +- ...-serial+console-native.aarch64-latest.args | 2 +- ...ach-virt-serial-compat.aarch64-latest.args | 2 +- ...ach-virt-serial-native.aarch64-latest.args | 2 +- .../mach-virt-serial-pci.aarch64-latest.args | 2 +- .../mach-virt-serial-usb.aarch64-latest.args | 2 +- .../machine-aliases1.x86_64-latest.args | 2 +- .../machine-aliases2.x86_64-latest.args | 2 +- .../machine-core-off.x86_64-latest.args | 2 +- .../machine-core-on.x86_64-latest.args | 2 +- .../machine-i8042-off.x86_64-latest.args | 2 +- .../machine-i8042-on.x86_64-latest.args | 2 +- .../machine-smm-off.x86_64-latest.args | 2 +- .../machine-smm-on.x86_64-latest.args | 2 +- .../machine-vmport-opt.x86_64-latest.args | 2 +- ...memory-default-hugepage.x86_64-latest.args | 2 +- .../memfd-memory-numa.x86_64-latest.args | 2 +- ...emory-hotplug-dimm-addr.x86_64-latest.args | 2 +- .../memory-hotplug-dimm.x86_64-latest.args | 2 +- ...memory-hotplug-multiple.x86_64-latest.args | 2 +- ...-hotplug-numa-preferred.x86_64-latest.args | 2 +- ...y-hotplug-nvdimm-access.x86_64-latest.args | 2 +- ...ry-hotplug-nvdimm-align.x86_64-latest.args | 2 +- ...ry-hotplug-nvdimm-label.x86_64-latest.args | 2 +- ...-hotplug-nvdimm-overlap.x86_64-latest.args | 2 +- ...ory-hotplug-nvdimm-pmem.x86_64-latest.args | 2 +- ...hotplug-nvdimm-readonly.x86_64-latest.args | 2 +- .../memory-hotplug-nvdimm.x86_64-latest.args | 2 +- ...mory-hotplug-virtio-mem.x86_64-latest.args | 2 +- ...ory-hotplug-virtio-pmem.x86_64-latest.args | 2 +- .../memory-hotplug.x86_64-latest.args | 2 +- .../memorybacking-set.x86_64-latest.args | 2 +- .../memorybacking-unset.x86_64-latest.args | 2 +- .../memtune-unlimited.x86_64-latest.args | 2 +- .../memtune.x86_64-latest.args | 2 +- .../metadata-duplicate.x86_64-latest.args | 2 +- .../metadata.x86_64-latest.args | 2 +- .../migrate-numa-unaligned.x86_64-latest.args | 2 +- .../migrate.x86_64-latest.args | 2 +- .../misc-disable-s3.x86_64-latest.args | 2 +- .../misc-disable-suspends.x86_64-latest.args | 2 +- .../misc-enable-s4.x86_64-latest.args | 2 +- .../misc-no-reboot.x86_64-latest.args | 2 +- .../misc-uuid.x86_64-latest.args | 2 +- .../mlock-off.x86_64-latest.args | 2 +- .../mlock-on.x86_64-latest.args | 2 +- .../mtp-usb-device.x86_64-latest.args | 2 +- ...ultifunction-pci-device.x86_64-latest.args | 2 +- .../name-escape.x86_64-latest.args | 2 +- .../net-bandwidth.x86_64-latest.args | 2 +- .../net-bandwidth2.x86_64-latest.args | 2 +- .../net-client.x86_64-latest.args | 2 +- .../net-coalesce.x86_64-latest.args | 2 +- .../net-eth-hostip.x86_64-latest.args | 2 +- .../net-eth-ifname.x86_64-latest.args | 2 +- .../net-eth-names.x86_64-latest.args | 2 +- .../net-eth-unmanaged-tap.x86_64-latest.args | 2 +- .../net-eth.x86_64-latest.args | 2 +- .../net-hostdev-bootorder.x86_64-latest.args | 2 +- ...net-hostdev-multidomain.x86_64-latest.args | 2 +- ...ostdev-vfio-multidomain.x86_64-latest.args | 2 +- .../net-hostdev-vfio.x86_64-latest.args | 2 +- .../net-hostdev.x86_64-latest.args | 2 +- .../net-isolated-port.x86_64-latest.args | 2 +- .../net-linkstate.x86_64-latest.args | 2 +- .../net-many-models.x86_64-latest.args | 2 +- .../net-mcast.x86_64-latest.args | 2 +- .../net-midonet.x86_64-latest.args | 2 +- .../net-mtu.x86_64-latest.args | 2 +- .../net-openvswitch.x86_64-latest.args | 2 +- .../net-server.x86_64-latest.args | 2 +- .../net-udp.x86_64-latest.args | 2 +- .../net-usb.x86_64-latest.args | 2 +- .../net-user-addr.x86_64-latest.args | 2 +- .../net-user-passt.x86_64-latest.args | 2 +- .../net-user.x86_64-latest.args | 2 +- .../net-vdpa-multiqueue.x86_64-latest.args | 2 +- .../net-vdpa.x86_64-latest.args | 2 +- .../net-vhostuser-multiq.x86_64-latest.args | 2 +- .../net-vhostuser-passt.x86_64-latest.args | 2 +- .../net-vhostuser.x86_64-latest.args | 2 +- .../net-virtio-device.x86_64-latest.args | 2 +- ...virtio-disable-offloads.x86_64-latest.args | 2 +- .../net-virtio-netdev.x86_64-latest.args | 2 +- ...irtio-network-portgroup.x86_64-latest.args | 2 +- .../net-virtio-rss.x86_64-latest.args | 2 +- ...et-virtio-rxtxqueuesize.x86_64-latest.args | 2 +- ...-virtio-teaming-hostdev.x86_64-latest.args | 2 +- ...-virtio-teaming-network.x86_64-latest.args | 2 +- .../net-virtio-teaming.x86_64-latest.args | 2 +- .../net-virtio-vhost.x86_64-latest.args | 2 +- .../net-virtio.x86_64-latest.args | 2 +- .../nosharepages.x86_64-latest.args | 2 +- ...auto-memory-vcpu-cpuset.x86_64-latest.args | 2 +- ...no-cpuset-and-placement.x86_64-latest.args | 2 +- ...d-auto-vcpu-no-numatune.x86_64-latest.args | 2 +- ...to-vcpu-static-numatune.x86_64-latest.args | 2 +- ...static-memory-auto-vcpu.x86_64-latest.args | 2 +- ...static-vcpu-no-numatune.x86_64-latest.args | 2 +- .../qemuxmlconfdata/numad.x86_64-latest.args | 2 +- ...ne-auto-nodeset-invalid.x86_64-latest.args | 2 +- .../numatune-auto-prefer.x86_64-latest.args | 2 +- .../numatune-distances.x86_64-latest.args | 2 +- .../numatune-hmat-none.x86_64-latest.args | 2 +- .../numatune-hmat.x86_64-latest.args | 2 +- ...atune-memnode-no-memory.x86_64-latest.args | 2 +- ...emnode-restrictive-mode.x86_64-latest.args | 2 +- .../numatune-memnode.x86_64-latest.args | 2 +- .../numatune-no-vcpu.x86_64-latest.args | 2 +- .../numatune-system-memory.x86_64-latest.args | 2 +- ...vcpus-topology-mismatch.x86_64-latest.args | 2 +- .../pages-dimm-discard.x86_64-latest.args | 2 +- ...pages-discard-hugepages.x86_64-latest.args | 2 +- .../pages-discard.x86_64-latest.args | 2 +- .../panic-double.x86_64-latest.args | 2 +- .../panic-no-address.x86_64-latest.args | 2 +- .../qemuxmlconfdata/panic.x86_64-latest.args | 2 +- ...arallel-parport-chardev.x86_64-latest.args | 2 +- .../parallel-tcp-chardev.x86_64-latest.args | 2 +- .../parallel-unix-chardev.x86_64-latest.args | 2 +- ...pi-root-hotplug-disable.x86_64-latest.args | 2 +- ...cpi-root-hotplug-enable.x86_64-latest.args | 2 +- .../pci-autoadd-addr.x86_64-latest.args | 2 +- .../pci-autoadd-idx.x86_64-latest.args | 2 +- .../pci-autofill-addr.x86_64-latest.args | 2 +- .../pci-bridge-many-disks.x86_64-latest.args | 2 +- .../pci-bridge.x86_64-latest.args | 2 +- .../pci-expander-bus.x86_64-latest.args | 2 +- .../pci-many.x86_64-latest.args | 2 +- .../pci-rom-disabled.x86_64-latest.args | 2 +- .../pci-rom.x86_64-latest.args | 2 +- .../pci-serial-dev-chardev.x86_64-latest.args | 2 +- ...e-expander-bus-aarch64.aarch64-latest.args | 2 +- .../pcie-expander-bus.x86_64-latest.args | 2 +- ...root-port-model-generic.x86_64-latest.args | 2 +- ...root-port-model-ioh3420.x86_64-latest.args | 2 +- ...cie-root-port-nohotplug.x86_64-latest.args | 2 +- .../pcie-root-port.x86_64-latest.args | 2 +- .../pcie-root.x86_64-latest.args | 2 +- ...-switch-downstream-port.x86_64-latest.args | 2 +- ...ie-switch-upstream-port.x86_64-latest.args | 2 +- .../pcihole64-gib.x86_64-latest.args | 2 +- .../pcihole64-q35.x86_64-latest.args | 2 +- .../pcihole64-virt.aarch64-latest.args | 2 +- .../pcihole64.x86_64-latest.args | 2 +- .../pmu-feature-off.x86_64-latest.args | 2 +- .../pmu-feature.x86_64-latest.args | 2 +- .../pstore-acpi-erst.x86_64-latest.args | 2 +- .../pv-spinlock-disabled.x86_64-latest.args | 2 +- .../pv-spinlock-enabled.x86_64-latest.args | 2 +- .../pvpanic-pci-aarch64.aarch64-latest.args | 2 +- ...pci-no-address-aarch64.aarch64-latest.args | 2 +- .../pvpanic-pci-x86_64.x86_64-latest.args | 2 +- ...35-default-devices-only.x86_64-latest.args | 2 +- .../q35-multifunction.x86_64-latest.args | 2 +- .../q35-pci-force-address.x86_64-latest.args | 2 +- .../q35-pcie-autoadd.x86_64-latest.args | 2 +- .../q35-pcie.x86_64-latest.args | 2 +- .../q35-usb2-multi.x86_64-latest.args | 2 +- .../q35-usb2-reorder.x86_64-latest.args | 2 +- .../q35-usb2.x86_64-latest.args | 2 +- .../q35-virt-manager-basic.x86_64-latest.args | 2 +- tests/qemuxmlconfdata/q35.x86_64-latest.args | 2 +- .../qemu-ns-alt.x86_64-latest.args | 2 +- ...qemu-ns-commandline-ns0.x86_64-latest.args | 2 +- ...qemu-ns-commandline-ns1.x86_64-latest.args | 2 +- .../qemu-ns-commandline.x86_64-latest.args | 2 +- ...-domain-commandline-ns0.x86_64-latest.args | 2 +- ...u-ns-domain-commandline.x86_64-latest.args | 2 +- .../qemu-ns-domain-ns0.x86_64-latest.args | 2 +- .../qemu-ns-no-env.x86_64-latest.args | 2 +- .../qemu-ns.x86_64-latest.args | 2 +- ...reboot-timeout-disabled.x86_64-latest.args | 2 +- .../reboot-timeout-enabled.x86_64-latest.args | 2 +- .../restore-v2-fd.x86_64-latest.args | 2 +- .../restore-v2.x86_64-latest.args | 2 +- ...rder-domain-subelements.x86_64-latest.args | 2 +- .../seclabel-dac-none.x86_64-latest.args | 2 +- ...eclabel-device-multiple.x86_64-latest.args | 2 +- ...label-dynamic-baselabel.x86_64-latest.args | 2 +- ...label-dynamic-labelskip.x86_64-latest.args | 2 +- ...el-dynamic-none-relabel.x86_64-latest.args | 2 +- .../seclabel-dynamic-none.x86_64-latest.args | 2 +- ...clabel-dynamic-override.x86_64-latest.args | 2 +- ...eclabel-dynamic-relabel.x86_64-latest.args | 2 +- .../seclabel-dynamic.x86_64-latest.args | 2 +- .../seclabel-none.x86_64-latest.args | 2 +- ...l-selinux-none-override.x86_64-latest.args | 2 +- ...clabel-static-labelskip.x86_64-latest.args | 2 +- ...seclabel-static-relabel.x86_64-latest.args | 2 +- .../seclabel-static.x86_64-latest.args | 2 +- .../serial-debugcon.x86_64-latest.args | 2 +- ...rial-dev-chardev-iobase.x86_64-latest.args | 2 +- .../serial-dev-chardev.x86_64-latest.args | 2 +- .../serial-file-chardev.x86_64-latest.args | 2 +- .../serial-file-log.x86_64-latest.args | 2 +- .../serial-many-chardev.x86_64-latest.args | 2 +- .../serial-pty-chardev.x86_64-latest.args | 2 +- .../serial-spiceport.x86_64-latest.args | 2 +- ...serial-target-port-auto.x86_64-latest.args | 2 +- .../serial-tcp-chardev.x86_64-latest.args | 2 +- ...rial-tcp-telnet-chardev.x86_64-latest.args | 2 +- ...p-tlsx509-chardev-notls.x86_64-latest.args | 2 +- ...-tlsx509-chardev-verify.x86_64-latest.args | 2 +- ...ial-tcp-tlsx509-chardev.x86_64-latest.args | 2 +- ...-tlsx509-secret-chardev.x86_64-latest.args | 2 +- .../serial-udp-chardev.x86_64-latest.args | 2 +- .../serial-unix-chardev.x86_64-latest.args | 2 +- .../serial-vc-chardev.x86_64-latest.args | 2 +- .../shmem-plain-doorbell.x86_64-latest.args | 2 +- .../smartcard-controller.x86_64-latest.args | 2 +- ...t-certificates-database.x86_64-latest.args | 2 +- ...tcard-host-certificates.x86_64-latest.args | 2 +- .../smartcard-host.x86_64-latest.args | 2 +- ...rd-passthrough-spicevmc.x86_64-latest.args | 2 +- ...artcard-passthrough-tcp.x86_64-latest.args | 2 +- ...rtcard-passthrough-unix.x86_64-latest.args | 2 +- .../smbios-type-fwcfg.x86_64-latest.args | 2 +- .../qemuxmlconfdata/smbios.x86_64-latest.args | 2 +- .../sound-device-virtio.x86_64-latest.args | 2 +- .../sound-device.x86_64-latest.args | 2 +- .../tap-vhost-incorrect.x86_64-latest.args | 2 +- .../tap-vhost.x86_64-latest.args | 2 +- .../throttlefilter.x86_64-latest.args | 2 +- ...pm-emulator-crb-profile.x86_64-latest.args | 2 +- .../tpm-emulator-tpm2-enc.x86_64-latest.args | 2 +- ...pm-emulator-tpm2-pstate.x86_64-latest.args | 2 +- .../tpm-emulator-tpm2.x86_64-latest.args | 2 +- .../tpm-emulator.x86_64-latest.args | 2 +- .../tpm-external.x86_64-latest.args | 2 +- .../tpm-passthrough-crb.x86_64-latest.args | 2 +- .../tpm-passthrough.x86_64-latest.args | 2 +- .../tseg-explicit-size.x86_64-latest.args | 2 +- ...roller-automatic-i440fx.x86_64-latest.args | 2 +- ...troller-automatic-isapc.x86_64-latest.args | 2 +- ...oller-automatic-microvm.x86_64-latest.args | 2 +- ...ontroller-automatic-q35.x86_64-latest.args | 2 +- ...ler-automatic-realview.aarch64-latest.args | 2 +- ...tomatic-unavailable-q35.x86_64-latest.args | 2 +- ...automatic-virt-aarch64.aarch64-latest.args | 2 +- ...ault-fallback-realview.aarch64-latest.args | 2 +- ...-fallback-virt-aarch64.aarch64-latest.args | 2 +- ...ntroller-default-i440fx.x86_64-latest.args | 2 +- ...-controller-default-q35.x86_64-latest.args | 2 +- ...oller-default-realview.aarch64-latest.args | 2 +- ...r-default-virt-aarch64.aarch64-latest.args | 2 +- ...troller-ich9-autoassign.x86_64-latest.args | 2 +- ...ntroller-ich9-companion.x86_64-latest.args | 2 +- ...ntroller-ich9-ehci-addr.x86_64-latest.args | 2 +- ...ler-nec-xhci-autoassign.x86_64-latest.args | 2 +- ...usb-controller-nec-xhci.x86_64-latest.args | 2 +- .../usb-controller-piix3.x86_64-latest.args | 2 +- ...sb-controller-qemu-xhci.x86_64-latest.args | 2 +- .../usb-hub-autoadd-deluxe.x86_64-latest.args | 2 +- .../usb-hub-autoadd.x86_64-latest.args | 2 +- .../usb-hub.x86_64-latest.args | 2 +- .../usb-long-port-path.x86_64-latest.args | 2 +- .../usb-none.x86_64-latest.args | 2 +- .../usb-port-autoassign.x86_64-latest.args | 2 +- .../usb-port-missing.x86_64-latest.args | 2 +- .../usb-ports.x86_64-latest.args | 2 +- .../usb-redir-boot.x86_64-latest.args | 2 +- ...sb-redir-filter-version.x86_64-latest.args | 2 +- .../usb-redir-filter.x86_64-latest.args | 2 +- .../usb-redir-unix.x86_64-latest.args | 2 +- .../usb-redir.x86_64-latest.args | 2 +- .../usb1-usb2.x86_64-latest.args | 2 +- .../user-aliases-usb.x86_64-latest.args | 2 +- .../user-aliases.x86_64-latest.args | 2 +- .../user-aliases2.x86_64-latest.args | 2 +- .../vcpu-placement-static.x86_64-latest.args | 2 +- ...vhost-user-fs-fd-memory.x86_64-latest.args | 2 +- ...st-user-fs-fd-openfiles.x86_64-latest.args | 2 +- ...vhost-user-fs-hugepages.x86_64-latest.args | 2 +- .../vhost-user-fs-readonly.x86_64-latest.args | 2 +- .../vhost-user-fs-sock.x86_64-latest.args | 2 +- ...host-user-gpu-secondary.x86_64-latest.args | 2 +- .../vhost-user-vga.x86_64-latest.args | 2 +- .../vhost-vsock-auto.x86_64-latest.args | 2 +- .../vhost-vsock.x86_64-latest.args | 2 +- ...eo-bochs-display-device.x86_64-latest.args | 2 +- .../video-bochs-edid-none.x86_64-latest.args | 2 +- .../video-bochs-edid-off.x86_64-latest.args | 2 +- .../video-bochs-edid-on.x86_64-latest.args | 2 +- ...-device-pciaddr-default.x86_64-latest.args | 2 +- .../video-none-device.x86_64-latest.args | 2 +- ...video-qxl-device-vgamem.x86_64-latest.args | 2 +- ...video-qxl-device-vram64.x86_64-latest.args | 2 +- .../video-qxl-device.x86_64-latest.args | 2 +- .../video-qxl-heads.x86_64-latest.args | 2 +- .../video-qxl-noheads.x86_64-latest.args | 2 +- .../video-qxl-resolution.x86_64-latest.args | 2 +- ...o-qxl-sec-device-vgamem.x86_64-latest.args | 2 +- ...o-qxl-sec-device-vram64.x86_64-latest.args | 2 +- .../video-qxl-sec-device.x86_64-latest.args | 2 +- ...eo-ramfb-display-device.x86_64-latest.args | 2 +- ...video-vga-device-vgamem.x86_64-latest.args | 2 +- .../video-vga-device.x86_64-latest.args | 2 +- .../video-vga-edid-none.x86_64-latest.args | 2 +- .../video-vga-edid-off.x86_64-latest.args | 2 +- .../video-vga-edid-on.x86_64-latest.args | 2 +- .../video-vga-qxl-heads.x86_64-latest.args | 2 +- .../video-virtio-blob-off.x86_64-latest.args | 2 +- .../video-virtio-blob-on.x86_64-latest.args | 2 +- .../video-virtio-edid-none.x86_64-latest.args | 2 +- .../video-virtio-edid-off.x86_64-latest.args | 2 +- .../video-virtio-edid-on.x86_64-latest.args | 2 +- ...video-virtio-gpu-device.x86_64-latest.args | 2 +- ...video-virtio-gpu-sdl-gl.x86_64-latest.args | 2 +- ...eo-virtio-gpu-secondary.x86_64-latest.args | 2 +- ...deo-virtio-gpu-spice-gl.x86_64-latest.args | 2 +- .../video-virtio-gpu-virgl.x86_64-latest.args | 2 +- ...io-vga-device-downgrade.x86_64-latest.args | 2 +- ....QEMU_CAPS_VIRTIO_GPU_GL_PCI-disabled.args | 2 +- ...APS_VIRTIO_VGA_GL-disabled-ABI_UPDATE.args | 2 +- ...test.QEMU_CAPS_VIRTIO_VGA_GL-disabled.args | 2 +- ...video-virtio-vga-gpu-gl.x86_64-latest.args | 2 +- ....QEMU_CAPS_DEVICE_VIRTIO_VGA-disabled.args | 2 +- .../video-virtio-vga.x86_64-latest.args | 2 +- .../virtio-9p-createmode.x86_64-latest.args | 2 +- .../virtio-9p-multidevs.x86_64-latest.args | 2 +- ...irtio-input-passthrough.x86_64-latest.args | 2 +- .../virtio-input.x86_64-latest.args | 2 +- .../virtio-iommu-aarch64.aarch64-latest.args | 2 +- .../virtio-iommu-x86_64.x86_64-latest.args | 2 +- ...virtio-non-transitional.x86_64-latest.args | 2 +- ...-options-controller-ats.x86_64-latest.args | 2 +- ...ptions-controller-iommu.x86_64-latest.args | 2 +- ...tions-controller-packed.x86_64-latest.args | 2 +- ...virtio-options-disk-ats.x86_64-latest.args | 2 +- ...rtio-options-disk-iommu.x86_64-latest.args | 2 +- ...tio-options-disk-packed.x86_64-latest.args | 2 +- .../virtio-options-fs-ats.x86_64-latest.args | 2 +- ...virtio-options-fs-iommu.x86_64-latest.args | 2 +- ...irtio-options-fs-packed.x86_64-latest.args | 2 +- ...irtio-options-input-ats.x86_64-latest.args | 2 +- ...tio-options-input-iommu.x86_64-latest.args | 2 +- ...io-options-input-packed.x86_64-latest.args | 2 +- ...-options-memballoon-ats.x86_64-latest.args | 2 +- ...loon-freepage-reporting.x86_64-latest.args | 2 +- ...ptions-memballoon-iommu.x86_64-latest.args | 2 +- ...tions-memballoon-packed.x86_64-latest.args | 2 +- .../virtio-options-net-ats.x86_64-latest.args | 2 +- ...irtio-options-net-iommu.x86_64-latest.args | 2 +- ...rtio-options-net-packed.x86_64-latest.args | 2 +- .../virtio-options-rng-ats.x86_64-latest.args | 2 +- ...irtio-options-rng-iommu.x86_64-latest.args | 2 +- ...rtio-options-rng-packed.x86_64-latest.args | 2 +- ...irtio-options-video-ats.x86_64-latest.args | 2 +- ...tio-options-video-iommu.x86_64-latest.args | 2 +- ...io-options-video-packed.x86_64-latest.args | 2 +- .../virtio-options.x86_64-latest.args | 2 +- .../virtio-rng-builtin.x86_64-latest.args | 2 +- .../virtio-rng-default.x86_64-latest.args | 2 +- .../virtio-rng-egd-unix.x86_64-latest.args | 2 +- .../virtio-rng-egd.x86_64-latest.args | 2 +- .../virtio-rng-multiple.x86_64-latest.args | 2 +- .../virtio-rng-random.x86_64-latest.args | 2 +- .../virtio-transitional.x86_64-latest.args | 2 +- .../vmcoreinfo.x86_64-latest.args | 2 +- .../watchdog-device.x86_64-latest.args | 2 +- .../watchdog-dump.x86_64-latest.args | 2 +- .../watchdog-injectnmi.x86_64-latest.args | 2 +- .../watchdog-q35-multiple.x86_64-latest.args | 2 +- .../watchdog.x86_64-latest.args | 2 +- .../x86-kvm-32-on-64.x86_64-latest.args | 2 +- ...6_64-default-cpu-kvm-pc.x86_64-latest.args | 2 +- ..._64-default-cpu-kvm-q35.x86_64-latest.args | 2 +- ...efault-cpu-tcg-features.x86_64-latest.args | 2 +- ...6_64-default-cpu-tcg-pc.x86_64-latest.args | 2 +- ..._64-default-cpu-tcg-q35.x86_64-latest.args | 2 +- ...fault-models.x86_64-latest.abi-update.args | 2 +- ...86_64-pc-default-models.x86_64-latest.args | 2 +- .../x86_64-pc-graphics.x86_64-latest.args | 2 +- .../x86_64-pc-headless.x86_64-latest.args | 2 +- ...4-pc-minimal.x86_64-latest.abi-update.args | 2 +- .../x86_64-pc-minimal.x86_64-latest.args | 2 +- ...fault-models.x86_64-latest.abi-update.args | 2 +- ...6_64-q35-default-models.x86_64-latest.args | 2 +- .../x86_64-q35-graphics.x86_64-latest.args | 2 +- .../x86_64-q35-headless.x86_64-latest.args | 2 +- ...-q35-minimal.x86_64-latest.abi-update.args | 2 +- .../x86_64-q35-minimal.x86_64-latest.args | 2 +- tests/qemuxmlconftest.c | 4 + 919 files changed, 3101 insertions(+), 2783 deletions(-) -- 2.55.0

2 8

[PATCH] docs: Fix example syntax error and update testing.rst
by rsmigiel＠redhat.com 16 Jul '26

16 Jul '26

From: Radoslaw Smigielski <rsmigiel(a)redhat.com> From: Radoslaw Smigielski <rsmigiel(a)redhat.com> Fix syntax error in one of the testing examples on alpine-edge image with prefix. Update CI helper examples to use more recent OS versions: - Fedora 38 -> Fedora 44 - Debian 11 -> Debian 13 - Debian 10 -> Debian 13 Signed-off-by: Radoslaw Smigielski <rsmigiel(a)redhat.com> --- docs/testing.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/testing.rst b/docs/testing.rst index 84111ffd4c9e..436e8e8c3910 100644 --- a/docs/testing.rst +++ b/docs/testing.rst @@ -137,18 +137,18 @@ the default libvirt registry: ... Now, let's say one would want to run the ``website`` job from GitLab on Debian -11. This is how a GitLab job specification can be referenced on ``ci/helper``'s +13. This is how a GitLab job specification can be referenced on ``ci/helper``'s command line: :: - $ ci/helper run --job website debian-10 + $ ci/helper run --job website debian-13 What if you want to run an rpmbuild of libvirt on an RPM distro? :: - $ ci/helper run --job rpmbuild fedora-38 + $ ci/helper run --job rpmbuild fedora-44 Want to use your own, say alpine-edge, container image from your GitLab container registry? @@ -156,7 +156,7 @@ Proceed with the following: :: - $ ci/helper run --job build --image-prefix registry.gitlab.com/<user>/libvirt/ci- alpine-edge + $ ci/helper run --job build --image-prefix registry.gitlab.com/<user>/libvirt/ci-alpine-edge Finally, it would be nice if one could get an interactive shell inside the test environment to debug potential build issues. This can be achieved with the -- 2.54.0

2 1

[PATCH] remote: block use of URI transport in scheme & query parameters
by Daniel P. Berrangé 16 Jul '26

16 Jul '26

From: Daniel P. Berrangé <berrange(a)redhat.com> The remote driver client supports specifying a transport in the URI scheme component such as +ext, +unix, +tls, etc. This determines how it should connect to the daemons. It strips this transport from the scheme to create a plain driver name that it forwards on to the remote server. It also, however, supports a "name" URI parameter which can be used to override the stripped URI that gets sent to the remote server. Unfortunately there is no validation of the URI by the remote server, so the URI override could include the transport in the scheme component. When the remote server sees a transport in the URI scheme, the connection gets diverted into the remote driver which then opens another client connection. When the "ext" transport is combined with the "command" URI parameter, this allows the client to trick the server into running an arbitrary command with the same privileges as the server. This can be abused with a read-only connection to a privileged server in order to elevate local privileges. There is no a valid reason to accept a transport component in the URI scheme received by the server, so validate this condition and reject any connection that violates it. This patch is derived from a proposal made by the reporter along with their disclosure, but generalized to block all schemes, not merely +ext and apply unconditionally to all connections not merely read-only ones. Reported-by: Deutsche Telekom Red Team <redteam(a)telekom.de> Fixes: CVE-2026-15268 Signed-off-by: Daniel P. Berrangé <berrange(a)redhat.com> --- src/remote/remote_daemon_dispatch.c | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/src/remote/remote_daemon_dispatch.c b/src/remote/remote_daemon_dispatch.c index 329853b6da..95ab173b7c 100644 --- a/src/remote/remote_daemon_dispatch.c +++ b/src/remote/remote_daemon_dispatch.c @@ -2135,6 +2135,31 @@ remoteDispatchProbeURI(bool readonly, } #endif /* VIRTPROXYD */ +static int +remoteCheckPermittedConnURI(const char *uristr) +{ + g_autoptr(virURI) uri = NULL; + + if (!(uri = virURIParse(uristr))) + return -1; + + /* + * Use of a transport (eg "+ext") in the scheme can be used to + * trick the daemon into using the remote driver to connect to + * an arbitrary socket under the caller's control. The valid + * URIs from the remote driver client will never include a + * transport component, so always reject that attempt. + */ + if (uri->scheme && + strchr(uri->scheme, '+')) { + virReportError(VIR_ERR_OPERATION_DENIED, + _("Remote URI '%1$s' is not permitted to include a transport"), + uristr); + return -1; + } + + return 0; +} static int remoteDispatchConnectOpen(virNetServer *server G_GNUC_UNUSED, @@ -2164,6 +2189,10 @@ remoteDispatchConnectOpen(virNetServer *server G_GNUC_UNUSED, name = args->name ? *args->name : NULL; + if (name && STRNEQ(name, "") && + remoteCheckPermittedConnURI(name) < 0) + goto cleanup; + /* If this connection arrived on a readonly socket, force * the connection to be readonly. */ -- 2.55.0

2 1

[libvirt PATCH 0/4] network: reject line breaks in DNS records emitted to dnsmasq
by Michael Bommarito 16 Jul '26

16 Jul '26

The network XML schema supports typed DNS records using <dns><txt> and <dns><srv> tags, and the TXT and SRV domain/target values do not strip XML numeric char refs like 
 (LF). As a result, these XML values can be used to insert additional configuration or commands into the dnsmasq config created by the network driver, e.g., a malicious dhcp-script=... line. libvirt socket access is already documented as root-equivalent, and raw <dnsmasq:options> namespace already exists, so this fix should be treated as hardening-only for default deployments that do not provide unpriv users with access to configure/extend these values. The series validates on both the parser and the emitter side: 1-2. reject LF/CR in the TXT value and SRV domain/target at XML parse time; 3. add a defensive check in the dnsmasq config emitter so a future parser gap cannot reintroduce directive injection; the raw <dnsmasq:options> namespace is intentionally left untouched; 4. add parse-path and update-API negative tests using 
/. Coordinated and assigned CVE-2026-61477 by RH team. Testing: built against current master with the network driver and tests enabled. The new negative tests fail on unpatched master (the expected parse error does not occur) and pass with the series applied, across both the network XML parse path and the update API. Michael Bommarito (4): conf: reject line breaks in DNS TXT record values conf: reject line breaks in DNS SRV domain and target network: reject line breaks before writing dnsmasq DNS config tests: cover line-break rejection in DNS TXT and SRV records src/conf/network_conf.c | 24 ++++++++++++++++ src/network/bridge_driver.c | 28 +++++++++++++++++++ .../dns-txt-record-newline.xml | 1 + .../srv-record-target-newline.xml | 1 + tests/networkxml2xmlupdatetest.c | 12 ++++++++ ...-network-dns-srv-record-domain-newline.xml | 14 ++++++++++ ...-network-dns-srv-record-target-newline.xml | 14 ++++++++++ .../nat-network-dns-txt-record-newline.xml | 14 ++++++++++ tests/networkxmlconftest.c | 3 ++ 9 files changed, 111 insertions(+) create mode 100644 tests/networkxml2xmlupdatein/dns-txt-record-newline.xml create mode 100644 tests/networkxml2xmlupdatein/srv-record-target-newline.xml create mode 100644 tests/networkxmlconfdata/nat-network-dns-srv-record-domain-newline.xml create mode 100644 tests/networkxmlconfdata/nat-network-dns-srv-record-target-newline.xml create mode 100644 tests/networkxmlconfdata/nat-network-dns-txt-record-newline.xml -- 2.53.0

2 7

[PATCH v9 0/2] qemu: Support HW-accelerated vSMMUs
by Nathan Chen 15 Jul '26

15 Jul '26

Hi, This is a follow up to the eighth patchset [0] for supporting multiple hardware-accelerated vSMMU instances. For instance, specifying hostdevs associated with multiple accelerated SMMUs, configured to be routed to pcie-expander-bus controllers in a way where VFIO device to SMMUv3 associations are matched with the host: <devices> ... <controller type='pci' index='1' model='pcie-expander-bus'> <model name='pxb-pcie'/> <target busNr='252'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </controller> <controller type='pci' index='2' model='pcie-expander-bus'> <model name='pxb-pcie'/> <target busNr='248'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </controller> ... <controller type='pci' index='21' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='21' port='0x0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </controller> <controller type='pci' index='22' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='22' port='0xa8'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> ... <hostdev mode='subsystem' type='pci' managed='no'> <source> <address domain='0x0009' bus='0x01' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x15' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='no'> <source> <address domain='0x0019' bus='0x01' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x16' slot='0x00' function='0x0'/> </hostdev> <iommu model='smmuv3'> <driver pciBus='1' accel='on' ats='on' ril='off' ssidSize='20' oas='44'/> </iommu> <iommu model='smmuv3'> <driver pciBus='2' accel='on' ats='on' ril='off' ssidSize='20' oas='44'/> </iommu> </devices> This would get translated to a qemu command line with the arguments below: -device '{"driver":"pxb-pcie","bus_nr":252,"id":"pci.1","bus":"pcie.0","addr":"0x1"}' \ -device '{"driver":"pxb-pcie","bus_nr":248,"id":"pci.2","bus":"pcie.0","addr":"0x2"}' \ -device '{"driver":"pcie-root-port","port":0,"chassis":21,"id":"pci.21","bus":"pci.1","addr":"0x0"}' \ -device '{"driver":"pcie-root-port","port":168,"chassis":22,"id":"pci.22","bus":"pci.2","addr":"0x0"}' \ -device '{"driver":"arm-smmuv3","primary-bus":"pci.1","id":"iommu0","accel":true,"ats":"on","ril":"off","ssidsize":"20","oas":"44"}' \ -device '{"driver":"arm-smmuv3","primary-bus":"pci.2","id":"iommu1","accel":true,"ats":"on","ril":"off","ssidsize":"20","oas":"44"}' \ -device '{"driver":"vfio-pci","host":"0009:01:00.0","id":"hostdev0","bus":"pci.21","addr":"0x0"}' \ -device '{"driver":"vfio-pci","host":"0019:01:00.0","id":"hostdev1","bus":"pci.22","addr":"0x0"}' \ Two QEMU series implementing auto support for accel SMMUv3 properties are now present in the upstream master branch [1][2]. This Libvirt series leverages the auto support: users can omit SMMUv3 properties ATS, RIL, OAS, and SSIDSIZE on the domain XML, and they will also be omitted on the QEMU command line as a result. With these new QEMU series applied, the feature property values will default to 'auto' to be resolved based on what the host SMMU supports. This series is on Github: https://github.com/NathanChenNVIDIA/libvirt/tree/smmuv3-accel-v9/ Thanks, Nathan [0] https://lists.libvirt.org/archives/list/devel@lists.libvirt.org/thread/XETQ… [1] https://lore.kernel.org/all/20260323182454.1416110-1-nathanc@nvidia.com/ [2] https://lore.kernel.org/all/20260608174900.2227340-1-nathanc@nvidia.com/ Changes from v8: - Changed smmuv3 attribute QEMU CLI values to strings to match QEMU 11.0 Changes from v7: - Remove support for x-vpasid-cap-offset based on feedback pointing out the QEMU feature prefixed with x- is experimental and not to be supported in Libvirt - Implement support for auto SMMUv3 properties. Omitting these properties in the XML omits them on the QEMU command line as well, which results in default auto values being chosen for ATS, RIL, SSIDSIZE, and OAS - Add validation check that only allows enabling accel SMMUv3 features when accel is enabled - Add tests for accel=on but omitting accel SMMUv3 feature properties Changes from v6: - Remove smmuv3 'pasid' attribute - Add smmuv3 'ssidsize' attribute - Add support for 'vpasidCapOffset' element - Modify logic for building accel smmuv3 qemu command line to omit ATS, RIL, accel flags when not needed (enabled/disabled by default in QEMU SMMUv3) Nathan Chen (2): qemu: Add support for HW-accelerated nested SMMUv3 tests: qemuxmlconfdata: provide HW-accel smmuv3 sample XML and CLI args docs/formatdomain.rst | 29 +++++++ src/conf/domain_conf.c | 80 +++++++++++++++++++ src/conf/domain_conf.h | 5 ++ src/conf/domain_validate.c | 27 ++++++- src/conf/schemas/domaincommon.rng | 25 ++++++ src/qemu/qemu_command.c | 15 ++++ ...uv3-pci-bus-accel-auto.aarch64-latest.args | 38 +++++++++ ...muv3-pci-bus-accel-auto.aarch64-latest.xml | 63 +++++++++++++++ .../iommu-smmuv3-pci-bus-accel-auto.xml | 53 ++++++++++++ ...u-smmuv3-pci-bus-accel.aarch64-latest.args | 38 +++++++++ ...mu-smmuv3-pci-bus-accel.aarch64-latest.xml | 63 +++++++++++++++ .../iommu-smmuv3-pci-bus-accel.xml | 53 ++++++++++++ tests/qemuxmlconftest.c | 2 + 13 files changed, 490 insertions(+), 1 deletion(-) create mode 100644 tests/qemuxmlconfdata/iommu-smmuv3-pci-bus-accel-auto.aarch64-latest.args create mode 100644 tests/qemuxmlconfdata/iommu-smmuv3-pci-bus-accel-auto.aarch64-latest.xml create mode 100644 tests/qemuxmlconfdata/iommu-smmuv3-pci-bus-accel-auto.xml create mode 100644 tests/qemuxmlconfdata/iommu-smmuv3-pci-bus-accel.aarch64-latest.args create mode 100644 tests/qemuxmlconfdata/iommu-smmuv3-pci-bus-accel.aarch64-latest.xml create mode 100644 tests/qemuxmlconfdata/iommu-smmuv3-pci-bus-accel.xml -- 2.43.0

2 4

[PATCH] src: fix crash searching for XML context string on errors
by Daniel P. Berrangé 15 Jul '26

15 Jul '26

From: Daniel P. Berrangé <berrange(a)redhat.com> When we have an XML parse error, libxml2 invokes a callback that receives pointers to the start of the document being parsed and the location where the error was triggered. In the case of a document that contains 100's of empty lines (ie a sequence of newlines), at some point libxml2 will advance the base pointer discarding the useful context. Thus when catchXMLError then searches backwards to discard empty lines and look for the context element, it will eventually get to the start of the string. When this happens the virBuffer that holds the context string ends up empty and then catchXMLError will dereference a NULL pointer. In almost all cases, the APIs which accept XML documents from the user are behind the primary read-write socket, however, the CPU baseline API is exposed to the read-only socket. Thus an unprivileged user can trigger a denial of service by crashing the libvirt daemons with a malicious XML document. Check for this empty string condition and skip inclusion of the XML document context in the error message. Fixes: CVE-2026-61478 Reported-by: Rx <rx1513(a)altlinux.org> Signed-off-by: Daniel P. Berrangé <berrange(a)redhat.com> --- src/util/virxml.c | 46 +++++++++++++++++++++++++++++++--------------- 1 file changed, 31 insertions(+), 15 deletions(-) diff --git a/src/util/virxml.c b/src/util/virxml.c index beb5301378..8349115633 100644 --- a/src/util/virxml.c +++ b/src/util/virxml.c @@ -1173,7 +1173,8 @@ catchXMLError(void *ctx, const char *msg G_GNUC_UNUSED, ...) contextstr = virBufferContentAndReset(&buf); /* (leave buffer space for pointer + line terminator) */ - for (n = 0; (n<col) && (contextstr[n] != 0); n++) { + + for (n = 0; (n<col) && contextstr && contextstr[n]; n++) { if (contextstr[n] == '\t') virBufferAddChar(&buf, '\t'); else @@ -1184,21 +1185,36 @@ catchXMLError(void *ctx, const char *msg G_GNUC_UNUSED, ...) pointerstr = virBufferContentAndReset(&buf); - if (filename) { - virGenericReportError(domcode, VIR_ERR_XML_DETAIL, - _("%1$s:%2$d: %3$s%4$s\n%5$s"), - filename, - lastError->line, - lastError->message, - contextstr, - pointerstr); + if (contextstr) { + if (filename) { + virGenericReportError(domcode, VIR_ERR_XML_DETAIL, + _("%1$s:%2$d: %3$s%4$s\n%5$s"), + filename, + lastError->line, + lastError->message, + contextstr, + pointerstr); + } else { + virGenericReportError(domcode, VIR_ERR_XML_DETAIL, + _("at line %1$d: %2$s%3$s\n%4$s"), + lastError->line, + lastError->message, + contextstr, + pointerstr); + } } else { - virGenericReportError(domcode, VIR_ERR_XML_DETAIL, - _("at line %1$d: %2$s%3$s\n%4$s"), - lastError->line, - lastError->message, - contextstr, - pointerstr); + if (filename) { + virGenericReportError(domcode, VIR_ERR_XML_DETAIL, + _("%1$s:%2$d: %3$s"), + filename, + lastError->line, + lastError->message); + } else { + virGenericReportError(domcode, VIR_ERR_XML_DETAIL, + _("at line %1$d: %2$s"), + lastError->line, + lastError->message); + } } } -- 2.55.0

2 1

[PATCH] qemu: qemuDomainRenameCallback: tidy up
by Roman Bogorodskiy 14 Jul '26

14 Jul '26

A few non-functional changes improving overall readability: - Use g_steal_pointer() for domain name switch code. - Clean up the 'cleanup' handler. - Fix indent for virDomainEventLifecycleNewFromObj() arguments. Signed-off-by: Roman Bogorodskiy <bogorodskiy(a)gmail.com> --- src/qemu/qemu_driver.c | 26 ++++++++++++++------------ 1 file changed, 14 insertions(+), 12 deletions(-) diff --git a/src/qemu/qemu_driver.c b/src/qemu/qemu_driver.c index 3d57de389b..6c124672d4 100644 --- a/src/qemu/qemu_driver.c +++ b/src/qemu/qemu_driver.c @@ -19064,9 +19064,8 @@ qemuDomainRenameCallback(virDomainObj *vm, } /* Switch name in domain definition. */ - old_dom_name = vm->def->name; - vm->def->name = new_dom_name; - new_dom_name = NULL; + old_dom_name = g_steal_pointer(&vm->def->name); + vm->def->name = g_steal_pointer(&new_dom_name); if (virDomainSnapshotForEach(vm->snapshots, qemuDomainSnapshotWriteMetadataIter, @@ -19085,22 +19084,25 @@ qemuDomainRenameCallback(virDomainObj *vm, VIR_DOMAIN_EVENT_UNDEFINED, VIR_DOMAIN_EVENT_UNDEFINED_RENAMED); event_new = virDomainEventLifecycleNewFromObj(vm, - VIR_DOMAIN_EVENT_DEFINED, - VIR_DOMAIN_EVENT_DEFINED_RENAMED); + VIR_DOMAIN_EVENT_DEFINED, + VIR_DOMAIN_EVENT_DEFINED_RENAMED); virObjectEventStateQueue(driver->domainEventState, event_old); virObjectEventStateQueue(driver->domainEventState, event_new); ret = 0; cleanup: - if (old_dom_name && ret < 0) { - new_dom_name = vm->def->name; - vm->def->name = old_dom_name; - old_dom_name = NULL; - } + if (ret < 0) { + if (old_dom_name) { + new_dom_name = vm->def->name; + vm->def->name = old_dom_name; + old_dom_name = NULL; + } - if (ret < 0) virErrorPreserveLast(&err); - qemuDomainNamePathsCleanup(cfg, ret < 0 ? new_dom_name : old_dom_name, true); + qemuDomainNamePathsCleanup(cfg, new_dom_name, true); + } else { + qemuDomainNamePathsCleanup(cfg, old_dom_name, true); + } virErrorRestore(&err); return ret; } -- 2.52.0

2 1

[PATCH] qemu: Pass driver to qemuDomainRestoreInternal explicitly
by Daniel Golle 13 Jul '26

13 Jul '26

qemuAutostartDomain() starts domains with conn=NULL as there is no client connection during driver initialisation. Since the managed save restore path of qemuDomainObjStart() was switched to qemuDomainRestoreInternal(), which obtains the driver by dereferencing conn->privateData, any domain with both a managed save image and the autostart (or autostart-once) flag crashes virtqemud/libvirtd with SIGSEGV on daemon startup. The session daemon's auto-shutdown feature creates exactly this combination on logout with a running VM (auto_shutdown_try_save saves the domain and auto_shutdown_restore marks it autostart-once), so the first daemon start of every subsequent boot segfaults and clients such as GNOME Boxes fail with "Cannot recv data: Connection reset by peer", showing an empty machine list. Pass the driver as an explicit parameter, as qemuDomainObjRestore() did before it was merged into qemuDomainRestoreInternal(), and keep @conn only for use by the ACL check callbacks, which are not used in the autostart code path. Fixes: 0e2ab427782c ("qemu: driver: Merge 'qemuDomainRestoreInternal' and 'qemuDomainObjRestore'") Signed-off-by: Daniel Golle <daniel(a)makrotopia.org> --- Observed with libvirt 12.5.0 and QEMU 11.0.2 on Arch Linux; the code in current git master is identical. Reproducer (any session domain, regular autostart takes the same path): $ virsh -c qemu:///session managedsave DOMAIN $ virsh -c qemu:///session autostart DOMAIN --once # simulate the first daemon start of a boot: $ rm "$XDG_RUNTIME_DIR/libvirt/qemu/run/autostarted" $ pkill -x virtqemud $ virsh -c qemu:///session list --all error: failed to connect to the hypervisor error: Cannot recv data: Connection reset by peer Backtrace of the crashing thread (12.5.0, distro debug symbols): #0 qemuDomainRestoreInternal (conn=conn@entry=0x0, ...) at ../src/qemu/qemu_driver.c:5940 #1 qemuDomainObjStart.constprop.0 (conn=conn@entry=0x0, ...) at ../src/qemu/qemu_driver.c:6509 #2 qemuAutostartDomain at ../src/qemu/qemu_driver.c:185 #3 virDomainDriverAutoStartOne at ../src/hypervisor/domain_driver.c:700 #7 virDomainDriverAutoStart at ../src/hypervisor/domain_driver.c:728 #8 qemuStateInitialize at ../src/qemu/qemu_driver.c:962 #9 virStateInitialize at ../src/libvirt.c:667 Tested on current master in an isolated session environment with a minimal diskless domain: unpatched, the daemon reproducibly segfaults on startup after the steps above; patched, it starts cleanly and restores the domain from its managed save image. The explicit restore APIs (virDomainRestore*) behave as before. src/qemu/qemu_driver.c | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) diff --git a/src/qemu/qemu_driver.c b/src/qemu/qemu_driver.c index 3d57de38..d478d383 100644 --- a/src/qemu/qemu_driver.c +++ b/src/qemu/qemu_driver.c @@ -5901,7 +5901,8 @@ qemuNodeGetSecurityModel(virConnectPtr conn, /** * qemuDomainRestoreInternal: - * @conn: connection object + * @driver: QEMU driver + * @conn: connection object (optional if @ensureACL is NULL) * @vmRestore: Domain object (optional; see below) * @path: path to the save image file * @unlink_corrupt: remove corrupted save image file @path @@ -5926,7 +5927,8 @@ qemuNodeGetSecurityModel(virConnectPtr conn, * corrupted image was removed 1 is returned. */ static int -qemuDomainRestoreInternal(virConnectPtr conn, +qemuDomainRestoreInternal(virQEMUDriver *driver, + virConnectPtr conn, virDomainObj *vmRestore, const char *path, bool unlink_corrupt, @@ -5937,7 +5939,6 @@ qemuDomainRestoreInternal(virConnectPtr conn, int (*ensureACL)(virConnectPtr, virDomainDef *), virDomainAsyncJob asyncJob) { - virQEMUDriver *driver = conn->privateData; qemuDomainObjPrivate *priv = NULL; g_autoptr(virDomainDef) def = NULL; virDomainObj *vm = NULL; @@ -6096,7 +6097,8 @@ qemuDomainRestoreFlags(virConnectPtr conn, { virCheckFlags(QEMU_DOMAIN_RESTORE_FLAGS, -1); - return qemuDomainRestoreInternal(conn, NULL, path, false, dxml, NULL, 0, + return qemuDomainRestoreInternal(conn->privateData, conn, NULL, path, + false, dxml, NULL, 0, flags, virDomainRestoreFlagsEnsureACL, VIR_ASYNC_JOB_START); } @@ -6105,7 +6107,8 @@ static int qemuDomainRestore(virConnectPtr conn, const char *path) { - return qemuDomainRestoreInternal(conn, NULL, path, false, NULL, NULL, 0, + return qemuDomainRestoreInternal(conn->privateData, conn, NULL, path, + false, NULL, NULL, 0, 0, virDomainRestoreEnsureACL, VIR_ASYNC_JOB_START); } @@ -6141,7 +6144,8 @@ qemuDomainRestoreParams(virConnectPtr conn, return -1; } - ret = qemuDomainRestoreInternal(conn, NULL, path, false, dxml, params, nparams, + ret = qemuDomainRestoreInternal(conn->privateData, conn, NULL, path, + false, dxml, params, nparams, flags, virDomainRestoreParamsEnsureACL, VIR_ASYNC_JOB_START); return ret; @@ -6506,7 +6510,7 @@ qemuDomainObjStart(virConnectPtr conn, restore_flags |= bypass_cache ? VIR_DOMAIN_SAVE_BYPASS_CACHE : 0; restore_flags |= reset_nvram ? VIR_DOMAIN_SAVE_RESET_NVRAM : 0; - ret = qemuDomainRestoreInternal(conn, vm, managed_save, true, NULL, NULL, 0, + ret = qemuDomainRestoreInternal(driver, conn, vm, managed_save, true, NULL, NULL, 0, restore_flags, NULL, asyncJob); -- 2.55.0

1 0

[PATCH 0/3] bhyve: improve domain startup error handling
by Roman Bogorodskiy 13 Jul '26

13 Jul '26

Roman Bogorodskiy (3): bhyve: error handling for monitor opening bhyve: improve domain startup error handling bhyve: clear monitor reference on close src/bhyve/bhyve_driver.c | 2 +- src/bhyve/bhyve_monitor.c | 6 ++-- src/bhyve/bhyve_process.c | 73 ++++++++++++++++++++++++--------------- src/bhyve/bhyve_process.h | 3 +- 4 files changed, 51 insertions(+), 33 deletions(-) -- 2.52.0

2 6

[PATCH v2 0/6] Add TLS-PSK support for migration
by Abhisek Panda 13 Jul '26

13 Jul '26

QEMU provides the capability to encrypt the migration data stream using two transport layer security (TLS) authentication schemes: X.509 certificates and pre-shared keys (PSK). Currently, Libvirt only supports the X.509-based TLS authentication scheme. In TLS X.509 certificates, a set of live migrations utilize a fixed set of static certificates for encrypted migration. In this authentication scheme, users require to deploy a certificate authority and monitor the certificate expiration window. In case certificates are compromised all the future live migrations are vulnerable. To resolve this, this patch series introduce the support for pre-shared key-based authentication scheme. This mechanism relies on symmetric pre-shared keys (a secret key that is known to both sender and receiver prior to secure communication) for providing secure transfer of data. Libvirt solely manages the lifecycle of the ephemeral pre-shared keys, including, generation, persistent storage, and cleanup. Libvirt generates the key on the source machine, then transfers it to the destination machine using the migration cookie. To allow users to configure the size of the key, Libvirt provides the migrate_tls_psk_length configuration parameter in qemu.conf. To avoid introduction of an additional VIR_MIGRATE_* flag, we rely on existing the VIR_MIGRATE_TLS flag. If the VIR_MIGRATE_TLS flag is set but the ca-cert.pem file is missing on the source, then we fallback to using PSK-based authentication scheme during migration. v2: 1. Libvirt manages the lifecycle of pre-shared keys. 2. Transfer of keys to the destination via the migration cookie 3. Remove the VIR_MIGRATE_TLS_PSK flag instead rely on VIR_MIGRATE_TLS and availability of ca-cert.pem on source. 4. Drop VIR_MIGRATE_PARAM_TLS_PSK_DIRECTORY, Libvirt solely manages the pre-shared keys. Abhisek Panda (6): conf: Add a configuration param for TLS-PSK qemu: Manage a pre-shared key's lifecycle qemu: Add support to build the tls-creds-psk object qemu: rename tls-creds-x509 obj related functions qemu: Manage tls-creds-psk object lifecycle qemu: Set up the migrate TLS-PSK objects include/libvirt/libvirt-domain.h | 13 +- src/qemu/libvirtd_qemu.aug | 1 + src/qemu/qemu.conf.in | 8 ++ src/qemu/qemu_alias.c | 19 ++- src/qemu/qemu_alias.h | 5 +- src/qemu/qemu_backup.c | 2 +- src/qemu/qemu_command.c | 28 +++- src/qemu/qemu_command.h | 7 + src/qemu/qemu_conf.c | 10 ++ src/qemu/qemu_conf.h | 1 + src/qemu/qemu_domain.c | 2 +- src/qemu/qemu_hotplug.c | 124 +++++++++++----- src/qemu/qemu_hotplug.h | 42 ++++-- src/qemu/qemu_migration.c | 135 ++++++++++++++---- src/qemu/qemu_migration_cookie.c | 125 ++++++++++++++++ src/qemu/qemu_migration_cookie.h | 5 + src/qemu/qemu_migration_params.c | 109 ++++++++++---- src/qemu/qemu_migration_params.h | 22 ++- src/qemu/qemu_postparse.c | 2 +- src/qemu/test_libvirtd_qemu.aug.in | 1 + tests/qemumigparamsdata/tls-enabled.json | 2 +- tests/qemumigparamsdata/tls-enabled.reply | 2 +- tests/qemumigparamsdata/tls-enabled.xml | 2 +- tests/qemumigparamsdata/tls-hostname.json | 2 +- tests/qemumigparamsdata/tls-hostname.reply | 2 +- tests/qemumigparamsdata/tls-hostname.xml | 2 +- tests/qemumigrationcookiexmltest.c | 12 +- tests/qemumonitorjsontest.c | 4 +- tests/qemustatusxml2xmldata/upgrade-out.xml | 2 +- .../chardev-backends-json.x86_64-9.1.0.args | 8 +- .../chardev-backends-json.x86_64-latest.args | 8 +- .../chardev-backends.x86_64-9.1.0.args | 8 +- .../chardev-backends.x86_64-latest.args | 8 +- ...rk-tlsx509-nbd-hostname.x86_64-latest.args | 6 +- ...isk-network-tlsx509-nbd.x86_64-latest.args | 6 +- ...-tlsx509-chardev-verify.x86_64-latest.args | 4 +- ...ial-tcp-tlsx509-chardev.x86_64-latest.args | 4 +- ...-tlsx509-secret-chardev.x86_64-latest.args | 4 +- 38 files changed, 576 insertions(+), 171 deletions(-) -- 2.43.7

2 13

[PATCH v18 03/14] net/tap: deprecate "no" as special value for script/downscript
by Vladimir Sementsov-Ogievskiy 13 Jul '26

13 Jul '26

The interface is ambiguous, as "no" is valid file name. So, using "no" as a special value to disable script is deprecated. Use an empty string ("script=" / "downscript=") instead. In a future version, "no" will be treated as a plain file name, just like any other non-empty value. Document the deprecation in docs/about/deprecated.rst, qapi/net.json, and qemu-options.hx. Update other docs to use empty string instead of "no". Add a warning. Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov(a)yandex-team.ru> --- docs/about/deprecated.rst | 18 ++++++++++++++++++ docs/system/i386/microvm.rst | 4 ++-- docs/system/i386/xenpvh.rst | 2 +- docs/system/ppc/ppce500.rst | 4 ++-- docs/system/riscv/microchip-icicle-kit.rst | 2 +- docs/system/riscv/sifive_u.rst | 2 +- net/tap.c | 2 ++ qapi/net.json | 12 ++++++++---- qemu-options.hx | 7 +++++-- 9 files changed, 40 insertions(+), 13 deletions(-) diff --git a/docs/about/deprecated.rst b/docs/about/deprecated.rst index 0c656a968fc..c4929317e3a 100644 --- a/docs/about/deprecated.rst +++ b/docs/about/deprecated.rst @@ -71,6 +71,15 @@ flexible enough. The monitor objects have been converted to QOM, so ``-mon mode=control`` is replaced by ``-object monitor-qmp``. The short convenience options are not deprecated, only ``-mon``. +``script=no`` and ``downscript=no`` for ``-netdev tap`` (since 11.2) +''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' + +The special value ``"no"`` for the ``script`` and ``downscript`` +parameters of ``-netdev tap`` disables script execution. This special +treatment of ``"no"`` is deprecated. Use an empty string (``script=`` +or ``downscript=``) to disable script execution instead. In a future +version, ``"no"`` will be treated as a plain file name. + QEMU Machine Protocol (QMP) commands ------------------------------------ @@ -164,6 +173,15 @@ Use ``job-finalize`` instead. Use ``query-accelerators`` instead. +``"no"`` as value of ``script``/``downscript`` for tap in ``netdev_add`` (since 11.2) +''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' + +The special value ``"no"`` for the ``script`` and ``downscript`` +parameters of ``netdev_add`` with ``type=tap`` disables script +execution. This special treatment of ``"no"`` is deprecated. Use an +empty string instead. In a future version, ``"no"`` will be treated as +a plain file name. + Human Machine Protocol (HMP) commands ------------------------------------- diff --git a/docs/system/i386/microvm.rst b/docs/system/i386/microvm.rst index 1675e37d3e7..077ea15751e 100644 --- a/docs/system/i386/microvm.rst +++ b/docs/system/i386/microvm.rst @@ -79,7 +79,7 @@ legacy ``ISA serial`` device as console:: -serial stdio \ -drive id=test,file=test.img,format=raw,if=none \ -device virtio-blk-device,drive=test \ - -netdev tap,id=tap0,script=no,downscript=no \ + -netdev tap,id=tap0,script=,downscript= \ -device virtio-net-device,netdev=tap0 While the example above works, you might be interested in reducing the @@ -103,7 +103,7 @@ disabled:: -device virtconsole,chardev=virtiocon0 \ -drive id=test,file=test.img,format=raw,if=none \ -device virtio-blk-device,drive=test \ - -netdev tap,id=tap0,script=no,downscript=no \ + -netdev tap,id=tap0,script=,downscript= \ -device virtio-net-device,netdev=tap0 diff --git a/docs/system/i386/xenpvh.rst b/docs/system/i386/xenpvh.rst index 904778e3f5c..862f38830b1 100644 --- a/docs/system/i386/xenpvh.rst +++ b/docs/system/i386/xenpvh.rst @@ -42,7 +42,7 @@ case you need to construct one manually: -vnc none \ -display none \ -device virtio-net-pci,id=nic0,netdev=net0,mac=00:16:3e:5c:81:78 \ - -netdev type=tap,id=net0,ifname=vif3.0-emu,br=xenbr0,script=no,downscript=no \ + -netdev type=tap,id=net0,ifname=vif3.0-emu,br=xenbr0,script=,downscript= \ -smp 4,maxcpus=4 \ -nographic \ -machine xenpvh,ram-low-base=0,ram-low-size=2147483648,ram-high-base=4294967296,ram-high-size=2147483648,pci-ecam-base=824633720832,pci-ecam-size=268435456,pci-mmio-base=4026531840,pci-mmio-size=33554432,pci-mmio-high-base=824902156288,pci-mmio-high-size=68719476736 \ diff --git a/docs/system/ppc/ppce500.rst b/docs/system/ppc/ppce500.rst index c9fe0915dc5..ec5aaf14fd9 100644 --- a/docs/system/ppc/ppce500.rst +++ b/docs/system/ppc/ppce500.rst @@ -158,14 +158,14 @@ interface at PCI address 0.1.0, but we can switch that to an e1000 NIC by: $ qemu-system-ppc64 -M ppce500 -smp 4 -m 2G \ -display none -serial stdio \ -bios u-boot \ - -nic tap,ifname=tap0,script=no,downscript=no,model=e1000 + -nic tap,ifname=tap0,script=,downscript=,model=e1000 The QEMU ``ppce500`` machine can also dynamically instantiate an eTSEC device if “-device eTSEC” is given to QEMU: .. code-block:: bash - -netdev tap,ifname=tap0,script=no,downscript=no,id=net0 -device eTSEC,netdev=net0 + -netdev tap,ifname=tap0,script=,downscript=,id=net0 -device eTSEC,netdev=net0 Root file system on flash drive ------------------------------- diff --git a/docs/system/riscv/microchip-icicle-kit.rst b/docs/system/riscv/microchip-icicle-kit.rst index 9809e94b84b..7fdb96601ad 100644 --- a/docs/system/riscv/microchip-icicle-kit.rst +++ b/docs/system/riscv/microchip-icicle-kit.rst @@ -84,7 +84,7 @@ Then we can boot the machine by: $ qemu-system-riscv64 -M microchip-icicle-kit -smp 5 -m 2G \ -sd path/to/sdcard.img \ -nic user,model=cadence_gem \ - -nic tap,ifname=tap,model=cadence_gem,script=no \ + -nic tap,ifname=tap,model=cadence_gem,script= \ -display none -serial stdio \ -kernel path/to/u-boot/build/dir/u-boot.bin \ -dtb path/to/u-boot/build/dir/u-boot.dtb diff --git a/docs/system/riscv/sifive_u.rst b/docs/system/riscv/sifive_u.rst index 8f55ae8e313..0e4dcf3e70c 100644 --- a/docs/system/riscv/sifive_u.rst +++ b/docs/system/riscv/sifive_u.rst @@ -199,7 +199,7 @@ To boot the VxWorks kernel in QEMU with the ``sifive_u`` machine, use: $ qemu-system-riscv64 -M sifive_u -smp 5 -m 2G \ -display none -serial stdio \ - -nic tap,ifname=tap0,script=no,downscript=no \ + -nic tap,ifname=tap0,script=,downscript= \ -kernel /path/to/vxWorks \ -append "gem(0,0)host:vxWorks h=192.168.200.1 e=192.168.200.2:ffffff00 u=target pw=vxTarget f=0x01" diff --git a/net/tap.c b/net/tap.c index fedd48c48d2..1ec9e5ebe6f 100644 --- a/net/tap.c +++ b/net/tap.c @@ -103,6 +103,8 @@ static bool tap_is_explicit_no_script(const char *script_arg) } if (strcmp(script_arg, "no") == 0) { + warn_report("script=no/downscript=no is deprecated; " + "use script=/downscript= instead"); return true; } diff --git a/qapi/net.json b/qapi/net.json index 8f0915c4d86..ada0329ef9d 100644 --- a/qapi/net.json +++ b/qapi/net.json @@ -399,15 +399,19 @@ # @fds: multiple file descriptors of already opened multiqueue capable # tap # -# @script: script to initialize the interface. An empty string or -# "no" disables script execution. Defaults to +# @script: script to initialize the interface. An empty string +# disables script execution. Defaults to # ``<sysconfdir>/qemu-ifup``, where ``<sysconfdir>`` is the # system configuration directory at build time (typically /etc). +# Using "no" to disable script execution is deprecated (since +# 11.2); use an empty string instead. # -# @downscript: script to shut down the interface. An empty string or -# "no" disables script execution. Defaults to +# @downscript: script to shut down the interface. An empty string +# disables script execution. Defaults to # ``<sysconfdir>/qemu-ifdown``, where ``<sysconfdir>`` is the # system configuration directory at build time (typically /etc). +# Using "no" to disable script execution is deprecated (since +# 11.2); use an empty string instead. # # @br: bridge name (since 2.8) # diff --git a/qemu-options.hx b/qemu-options.hx index 200949655ea..7b9a14f5b38 100644 --- a/qemu-options.hx +++ b/qemu-options.hx @@ -3014,7 +3014,8 @@ DEF("netdev", HAS_ARG, QEMU_OPTION_netdev, " use network scripts 'file' (default=" DEFAULT_NETWORK_SCRIPT ")\n" " to configure it and 'dfile' (default=" DEFAULT_NETWORK_DOWN_SCRIPT ")\n" " to deconfigure it\n" - " use '[down]script=no' or '[down]script=' to disable script execution\n" + " use '[down]script=' to disable script execution\n" + " ('[down]script=no' is deprecated and will be treated as a file name in future)\n" " use network helper 'helper' (default=" DEFAULT_BRIDGE_HELPER ") to\n" " configure it\n" " use 'fd=h' to connect to an already opened TAP interface\n" @@ -3553,7 +3554,9 @@ SRST ``<sysconfdir>/qemu-ifup`` and the default network deconfigure script is ``<sysconfdir>/qemu-ifdown``, where ``<sysconfdir>`` is the system configuration directory at build time (typically ``/etc``). - Use ``[down]script=no`` or ``[down]script=`` to disable script execution. + Use ``[down]script=`` to disable script execution. + Using ``[down]script=no`` is deprecated; in a future version it will + be treated as a plain file name. If running QEMU as an unprivileged user, use the network helper to configure the TAP interface and attach it to the bridge. -- 2.43.0

3 4

[PATCH v2 0/5] virsh: Add missing TAB completers for several commands
by rsmigiel＠redhat.com 13 Jul '26

13 Jul '26

From: Radoslaw Smigielski <rsmigiel(a)redhat.com> These changes add missing virsh TAB completion callbacks for several commands. Fixed or added completers covers command grouped by similar options: output paths: - dump --file - save --file - blockcopy --dest - screenshot --file (fixes pre-existing wrong annotation) display / native format: - domdisplay --type - domxml-from-native --format - domxml-to-native --format storage volume formats: - vol-create-as --format - vol-create-as --backing-vol-format attach-disk: - targetbus, type, cache, io, mode, sourcetype, subdriver - source-host-socket In patch 1/5 added vshCompletePathLocalCreate, a new noop completer for local file paths used as command output where the target file may not exist yet. This is the counterpart to vshCompletePathLocalExisting, which is for existing files used as input. In patch 2/5 adds a completer for domdisplay --type using virDomainGraphicsTypeToString and VIR_DOMAIN_GRAPHICS_TYPE_LAST so the options stays in sync with libvirt graphics types. Replaced the static list from first patch set. In patch 3/5 adds virshDomainXMLNativeFormatCompleter for domxml-from-native --format (hypervisor-dependent native config format list). In virshDomainXMLNativeFormatCompleter() added 4 new "static const char[]" variables, follow the same pattern appears in the same file. Even though these variables could be a non-static local arrays. In patch 4/5 reuses existing completers for domxml-to-native --format and vol-create-as --format / --backing-vol-format. In 5/5 adds few enum and static-list completers for attach-disk options targetbus, type, cache, io, mode, and sourcetype, and reuses the storage file format completer for subdriver. In virshDomainAttachDiskSourceTypeCompleter, I added a static list of element types, I did not find any existing variable with the same list content. Partially-fixes: https://gitlab.com/libvirt/libvirt/-/work_items/9 Radoslaw Smigielski (5): virsh: Add vshCompletePathLocalCreate completer for output paths virsh: Add completer for '--type' option of 'domdisplay' command virsh: Add completer for '--format' option of 'domxml-from-native' command virsh: Add missing TAB completers for several options virsh: Add missing TAB completers for 'attach-disk' command tools/virsh-completer-domain.c | 122 +++++++++++++++++++++++++++++++++ tools/virsh-completer-domain.h | 40 +++++++++++ tools/virsh-domain.c | 16 ++++- tools/virsh-volume.c | 2 + tools/vsh-completer.c | 18 +++++ tools/vsh-completer.h | 5 ++ 6 files changed, 202 insertions(+), 1 deletion(-) -- 2.54.0

1 5

[PATCH 0/2] bhyve: implement the virDomainRename API
by Roman Bogorodskiy 13 Jul '26

13 Jul '26

Roman Bogorodskiy (2): bhyve: implement the virDomainRename API qemu: qemuDomainRenameCallback: remove unused variables src/bhyve/bhyve_domain.c | 27 +++++++++ src/bhyve/bhyve_domain.h | 1 + src/bhyve/bhyve_driver.c | 122 +++++++++++++++++++++++++++++++++++++++ src/qemu/qemu_driver.c | 4 -- 4 files changed, 150 insertions(+), 4 deletions(-) -- 2.52.0

2 6

[PATCH 0/3] bhyve: implement virDomainSetLifecycleAction() API
by Roman Bogorodskiy 12 Jul '26

12 Jul '26

Roman Bogorodskiy (3): bhyve: add validation for lifecycle actions bhyve: monitor: respect on_poweroff / on_reboot settings bhyve: implement virDomainSetLifecycleAction() API src/bhyve/bhyve_domain.c | 36 +++++++++++++ src/bhyve/bhyve_domain.h | 3 ++ src/bhyve/bhyve_driver.c | 110 ++++++++++++++++++++++++++++++++++++++ src/bhyve/bhyve_monitor.c | 20 +++++-- 4 files changed, 165 insertions(+), 4 deletions(-) -- 2.52.0

1 3

[PATCH 0/6] conf: add vlen tag for RISC-V CPUs
by Heinrich Schuchardt 10 Jul '26

10 Jul '26

RISC-V CPUs may provide a scalable vector extension. The length of the vector registers is implementation specific. QEMU allows to set the vector length as a CPU property, e.g. '-cpu rva23s64,vlen=256'. To describe this feature a new CPU tag is introduced: <vlen value='N'> According to the RISC-V ISA specification vlen must be a power of 2 in the range 8 to 65536. A configuration test is provided. Heinrich Schuchardt (6): conf: add vlen tag for RISC-V CPUs schemas: add cpuVlen definition for RISC-V vector length qemu: validate that CPU vlen is only used with RISC-V qemu: emit vlen= CPU property on the command line tests: provide vlen configuration test docs: add vlen to formatdomain documentation docs/formatdomain.rst | 13 ++++++++ src/conf/cpu_conf.c | 25 +++++++++++++++ src/conf/cpu_conf.h | 1 + src/conf/schemas/cputypes.rng | 11 +++++++ src/qemu/qemu_command.c | 3 ++ src/qemu/qemu_validate.c | 9 ++++++ .../riscv64-virt-vlen.riscv64-latest.args | 31 +++++++++++++++++++ .../riscv64-virt-vlen.riscv64-latest.xml | 26 ++++++++++++++++ tests/qemuxmlconfdata/riscv64-virt-vlen.xml | 26 ++++++++++++++++ tests/qemuxmlconftest.c | 2 ++ 10 files changed, 147 insertions(+) create mode 100644 tests/qemuxmlconfdata/riscv64-virt-vlen.riscv64-latest.args create mode 100644 tests/qemuxmlconfdata/riscv64-virt-vlen.riscv64-latest.xml create mode 100644 tests/qemuxmlconfdata/riscv64-virt-vlen.xml -- 2.53.0

1 6

[PATCH 0/6] virsh: Add missing TAB completers for several commands
by rsmigiel＠redhat.com 10 Jul '26

10 Jul '26

From: Radoslaw Smigielski <rsmigiel(a)redhat.com> This series adds missing virsh TAB completion callbacks for six command options: - dump --file - blockcopy --dest - detach-interface --type - domdisplay --type - domxml-from-native --format - save --file This is a small step towards closing the missing completers tracked in: https://gitlab.com/libvirt/libvirt/-/work_items/9 As of now there are 29 missing bash completers, the one fixed in this patch is first batch. As some of the patches change only one line, I would apprecate your feedback if these small one should be combined into a single patch? Radoslaw Smigielski (6): virsh: Add completer for '--file' option of 'dump' subcommand virsh: Add completer for '--dest' option of 'blockcopy' command virsh: Add completer for '--type' option of 'detach-interface' command virsh: Add completer for '--type' option of 'domdisplay' command virsh: Add completer for '--format' option of 'domxml-from-native' command virsh: Add completer for '--file' option of 'save' command tools/virsh-completer-domain.c | 49 ++++++++++++++++++++++++++++++++++ tools/virsh-completer-domain.h | 10 +++++++ tools/virsh-domain.c | 6 +++++ 3 files changed, 65 insertions(+) -- 2.54.0

2 11

Limit USB 1.0 (UHCI/OCHI) and 2.0 (EHCI) to non-virt use cases
by Daniel P. Berrangé 09 Jul '26

09 Jul '26

QEMU has implemented four generic USB controllers * UHCI - USB 1.0 only * OHCI - USB 1.0 only * EHCI - USB 2.0 only (must have UHCI companions for 1.0 compat) * XHCI - All of USB 3.0, 2.0, 1.0 in one controller We have two variants of XHCI, the generic one (hcd-xhci.c) and the NEC one (hcd-xhci-nec.c) Historically for security reports we have considered all of them in scope of virtualization, since initially with KVM the XHCI impl was not present in QEMU & thus KVM guests used UHCI/EHCI with USB tablet for a period of time All of the USB subsystem is currently orphaned, so we have no dedicated maintainer available to deal with bug reports (volunteers welcome to step up here...) While the need for USB is reduced given the availability of virtio-input, not all guests have drivers out of the box, so at least USB tablet is still interesting for KVM use cases with some modern OS. It is also not that unusual for people to need USB host device assignment with KVM virt to make various pieces of specialized hardware (security tokens, smart cards, custom dongles, etc) available directly to guests. IOW, we can't entirely exclude USB from virtualization use cases IMHO. In terms of virtualization, XHCI is the only impl that is sensible to use. UHCI/OHCI/EHCI all impose an unreasonable CPU load on any guest usage of USB. XHCI should be supported by any guest OS approx the last 15 years, which should be sufficient for virtualization use cases with OS that are not EOL by their vendor. Thus to reduce our maint burden around security bug handling, it is proposed henceforth to classify UHCI, OHCI and EHCI under the non- virtualization use case and thus be excluded from security bug triage processes. No CVEs would be assigned, bugs would be reported publically in gitlab: https://www.qemu.org/docs/master/system/security.html#non-virtualization-us… The XHCI controller (specifically the hcd-xhci.c variant) would remain as our only option for the virtualization use case, with security process applied to bugs & eligible for CVE assignment: https://www.qemu.org/docs/master/system/security.html#virtualization-use-ca… The other NEC XHCI variant (hcd-xhci-nec.c) would also be treated as non-virtualization use case, since it needlessly duplicates hcd-xhci.c impl and thus is only interesting for emulation of this specific HW variant. NB, there are no functional limitations / restrictions from this policy, it is largely just a semantic exercise. From a management application POV, however, it would strongly suggest that guests be configured with XHCI as the default choice if the user asks for USB, and in turn also imply that '-usb' not be used since that is UHCI/OHCI typically. CC'ing libvirt, though it is really a matter for virt-install/virt-manager/ openstack/kubevirt etc above libvirt to pick their defaults for USB controllers. None the less XHCI would still be in search of a maintainer to step forward and handle ongoing development and maint work. With regards, Daniel -- |: https://berrange.com ~~ https://hachyderm.io/@berrange :| |: https://libvirt.org ~~ https://entangle-photo.org :| |: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|

5 7

[PATCH] docs: drvbhyve: document newly added pf check
by Nimish Jain 09 Jul '26

09 Jul '26

Reflects that the pf firewall check was added in virt-host-validate. Signed-off-by: Nimish Jain <unauthorizen(a)gmail.com> --- docs/drvbhyve.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/drvbhyve.rst b/docs/drvbhyve.rst index 2e5e361115..51782f8090 100644 --- a/docs/drvbhyve.rst +++ b/docs/drvbhyve.rst @@ -11,8 +11,8 @@ recommended to use the `latest supported release <https://www.freebsd.org/releases/>`__ to make sure all new features of bhyve are supported. In order to enable bhyve on your FreeBSD host, you'll need -to load the ``vmm`` kernel module. Additionally, ``if_tap`` and ``if_bridge`` -modules should be loaded for networking support. Also, :since:`since 3.2.0` the +to load the ``vmm`` kernel module. Additionally, ``if_tap``, ``if_bridge`` +and ``pf`` modules should be loaded for networking support. Also, :since:`since 3.2.0` the ``virt-host-validate(1)`` supports the bhyve host validation and could be used like this: @@ -21,6 +21,7 @@ like this: $ virt-host-validate bhyve BHYVE: Checking for vmm module : PASS BHYVE: Checking for if_tap module : PASS + BHYVE: Checking for pf module : PASS BHYVE: Checking for if_bridge module : PASS BHYVE: Checking for nmdm module : PASS $ -- 2.39.5 (Apple Git-154)

2 1

[PATCH] docs: drvnetwork: Update sample pf.conf to include NAT forwarding for FreeBSD
by Nimish Jain 09 Jul '26

09 Jul '26

This is beneficial for new users using the 'default' libvirt network configuration on FreeBSD, to get a VM up and running quickly. Also fixes a typo ('netowork') Signed-off-by: Nimish Jain <unauthorizen(a)gmail.com> --- docs/drvnetwork.rst | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/drvnetwork.rst b/docs/drvnetwork.rst index 23082310ba..881b828d5f 100644 --- a/docs/drvnetwork.rst +++ b/docs/drvnetwork.rst @@ -10,14 +10,17 @@ Platform-specific notes FreeBSD ------- -FreeBSD netowork driver uses the pf firewall. Libvirt managed pf rules +FreeBSD network driver uses the pf firewall. Libvirt managed pf rules are created within anchors. Anchors need to be configured manually by -the user. Sample ``/etc/pf.conf`` might look like: +the user. Sample ``/etc/pf.conf`` with a basic NAT configuration +might look like: :: scrub all + nat on em0 from {192.168.122.0/24} to any -> (em0) + nat-anchor "libvirt\*" anchor "libvirt\*" -- 2.39.5 (Apple Git-154)

2 1

[PATCH 0/6] qemu: Support AF_VSOCK transport for QGA communication
by Polina Vishneva 09 Jul '26

09 Jul '26

This series add support for talking to QEMU guest agent via a vsock transport. This transport is attempted when there's no ready virtio-serial channels **and** the domain has a usable vsock CID. AF_VSOCK are sockets too, so most of the virtio-serial/UNIX socket code is reused for everything except the connection lifecycle management (that is, initial connection etc.). Since QGA has no readiness notification mechanism for vsock transport, unlike for virtio-serial transport, we have to knock on the port to probe for readiness. For that, a custom backoff logic with cancellation support is implemented. Both the new virVsockConnectQuiet helper and the vsock QGA connection logic itself are covered by new tests. Polina Vishneva (6): util: Add virVsockConnectQuiet helper qemu: Extract qemuProcessResetAgent helper qemu: Add qemuDomainVsockHasGuestCid helper qemu: Support AF_VSOCK transport for QGA communication tests: Add a unit test for virVsockConnectQuiet() tests: Add a test for qemuConnectAgent() to cover the vsock path src/hypervisor/qemu_agent.c | 73 +++++---- src/hypervisor/qemu_agent.h | 9 ++ src/libvirt_private.syms | 2 + src/qemu/qemu_domain.c | 28 +++- src/qemu/qemu_domain.h | 8 + src/qemu/qemu_driver.c | 16 +- src/qemu/qemu_hotplug.c | 6 + src/qemu/qemu_process.c | 305 +++++++++++++++++++++++++++++++---- src/qemu/qemu_process.h | 2 + src/util/virvsock.c | 71 +++++++- src/util/virvsock.h | 10 ++ tests/meson.build | 3 + tests/qemuagenttest.c | 43 ++++- tests/qemumonitortestutils.c | 119 +++++++++++++- tests/qemumonitortestutils.h | 4 + tests/qemuvsockagentmock.c | 65 ++++++++ tests/virvsockmock.c | 143 ++++++++++++++++ tests/virvsocktest.c | 133 +++++++++++++++ 18 files changed, 963 insertions(+), 77 deletions(-) create mode 100644 tests/qemuvsockagentmock.c create mode 100644 tests/virvsockmock.c create mode 100644 tests/virvsocktest.c -- 2.54.0

1 6

[PATCH v2] vbox: fix memory leak in vboxStartMachine()
by Elizaveta Tereshkina 09 Jul '26

09 Jul '26

vboxStartMachine() allocates sdlDisplay via g_strdup() and doesn't free it. Replace VIR_FREE calls in the function with g_autofree macro. Fixes: 3f4f0ef47d (vbox: Fix starting domains) Signed-off-by: Elizaveta Tereshkina <teryoshkina.ea(a)gmail.com> --- src/vbox/vbox_common.c | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/src/vbox/vbox_common.c b/src/vbox/vbox_common.c index 65ae9cc651..63401613d5 100644 --- a/src/vbox/vbox_common.c +++ b/src/vbox/vbox_common.c @@ -2162,8 +2162,8 @@ vboxStartMachine(virDomainPtr dom, int maxDomID, IMachine *machine) int vrdpPresent = 0; int sdlPresent = 0; int guiPresent = 0; - char *guiDisplay = NULL; - char *sdlDisplay = NULL; + g_autofree char *guiDisplay = NULL; + g_autofree char *sdlDisplay = NULL; PRUnichar *keyTypeUtf16 = NULL; PRUnichar *valueTypeUtf16 = NULL; char *valueTypeUtf8 = NULL; @@ -2233,7 +2233,7 @@ vboxStartMachine(virDomainPtr dom, int maxDomID, IMachine *machine) if (guiPresent || sdlPresent) { const char *display = NULL; const char *sessType = NULL; - char *displayutf8; + g_autofree char *displayutf8 = NULL; if (guiPresent) { sessType = "gui"; @@ -2250,8 +2250,6 @@ vboxStartMachine(virDomainPtr dom, int maxDomID, IMachine *machine) displayutf8 = g_strdup_printf("DISPLAY=%s", display); VBOX_UTF8_TO_UTF16(displayutf8, &env); - VIR_FREE(displayutf8); - VIR_FREE(guiDisplay); VBOX_UTF8_TO_UTF16(sessType, &sessionType); } else if (vrdpPresent) { -- 2.39.2

1 0

[PATCH 0/2] virt-host-validate-bhyve: Improve checks
by Nimish Jain 08 Jul '26

08 Jul '26

Nimish Jain (2): replace if_tap check with if_tuntap check add pf check tools/virt-host-validate-bhyve.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) -- 2.39.5 (Apple Git-154)

2 3

RFC: GitLab confidential issues for security disclosures ?
by Daniel P. Berrangé 08 Jul '26

08 Jul '26

The QEMU project has just changed to use GitLab confidential issues for security disclosures. https://www.qemu.org/contribute/security-process/ While libvirt isn't (yet) suffering the same massive AI powered bug tsunami, I'm not seeing an especially compelling reason to continue using email for security disclosures with such limited need-to-know practices. While using GitLab theoretically exposes us to greater risk of exposure via the GitLab's own staff / infra compromise, in practice they likely do a better job securing their infra than we do for our mailman install. Submissions are also guaranteed TLS protection which we can't so confidently assume for email. We don't tend to apply any long embargo times. Our maintainers are all trusted with commit access to libvirt.git, so from a trust POV I feel it acceptable to have scurity disclosures visible to all of them instead of restricted to a handful of maintainers. The security list has a handful of people from the distro present who in theory can watch it for early access to disclosures. I'm not sure if that makes a difference in practice though, especially with all the distros suffering an AI bug tsunami leading to greatly extended fix times. IOW, overall a lighter weight process using GitLab confidential issues feels like it should be sufficient for libvirt too. With regards, Daniel -- |: https://berrange.com ~~ https://hachyderm.io/@berrange :| |: https://libvirt.org ~~ https://entangle-photo.org :| |: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|

2 2

[PATCH v7 00/35] monitor: turn QMP and HMP into QOM objects
by Daniel P. Berrangé 07 Jul '26

07 Jul '26

Conceptually -object and object_add/object_del should be sufficient for essentially all QEMU configuration....if only we ported all our internal custom backends/devices/etc to QOM. That is of course a big job which is why it hasn't happened. This series started with the premise that the monitor is one of the easier areas to convert since we have no more than three classes, a common base, and QMP and HMP subclasses[1]. So why not give it a go and thus unlock the ability to dynamically create/delete monitors in QMP/HMP. This series does the conversion in a great many small steps to better understand the implications at each stage. The high level outcome of this series is * HMP and QMP monitors are QOM objects, 'monitor-hmp' and 'monitor-qmp' respectively * Both can be cold plugged and hot plugged. QMP only, can also be hot unplugged. * '-mon' is obsolete, deprecated and replaced by '-object', but -monitor, -qmp and kept as high level syntax sugar * QMP gains a concept of "close-action" which makes it possible to mark a monitor for auto-delete. The monitor hot-unplug code and the qtest and functional testing code is heavily derived from a series sent by Christian Brauner which proposed new monitor_add/monitor_del commands: https://lists.nongnu.org/archive/html/qemu-devel/2026-04/msg01349.html I left Christian's authorship & SoB on the patches which were derived from his code, though the code has been refactored quite a bit in places, so bugs are quite possibly my own. Note that Christian's series allowed the use of "monitor_del" commands against the current monitor session. ie a client could delete the very monitor it was using. This is an awkward concept as it needs special casing to delay the deletion to happen in the background, such that that the QMP response to 'monitor_del' could still be sent back. This also left the chardev was orphaned as there's no way to run 'chardev_dev' in that usage pattern. To provide an alternative mechanism to address the same use case, this series introduces the 'close-action' concept mentioned above, that allows hotplugging a monitor to service a specific task, with the monitor being purged when the script closes its connection. This avoids the special casing that an explicit "self deletion" paradigm required. While supporting hotplug of HMP was trivial, I didn't do any work to think about hotunplug of HMP, since IMHO it is of limited value given HMP's typical use cases. [1] ~~~ we did all this not because it was easy, but because we thought it would be easy ~~~ Changed in v7: - Split Chardev -> const char *chardev_id change into separate patch from QOM property addition - Copy editting of qemu-options docs - Updating of commit messages with improved wording - Remove redundant ERRP_GUARD - Improve error message wording when rejecting delete requests - Don't hardcode "gdbchrdev0" ID, allow default logic Changed in v6: - Present "ID" from QemuOpts to use for the QOM object - Use 'compat_monitorNNN' as ID if QemuOpts lacks an ID, for compat with -monitor/-qmp arg naming - Mark the Monitor class abstract when first defined - Tweaks to formatting of QAPI docs - Expand CLI docs to describe relation between -monitor and -qmp and -object. - Present object ID in error messages for prepare_delete callback - Drop API which dupes object_get_canonical_path_component - Dropped R-B on patches 01, 05, 34 Changed in v5: - Address another race when looking up monitor by ID - Refer to "line editting" when talking about HMP readline feature - Misc typos - Fix mis-placed setting of 'delete_pending' - Add test case to validate reconnecting to QMP Changed in v4: - Hold reference into BH to avoid race with auto-delete Changed in v3: - Removed unused 'dead' struct field - Make use of 'setup_pending' struct field across BH - Add missing free of chardev_id - Add missnig ERRP_GUARD in monitor_new_qmp - Misc docs typos / rephrasing - Moved docs patch to the end - Fixed docs about the default QOM ID naming for legacy monitor syntax - Fixed random sleep time calculation in tests Christian Brauner (6): monitor: convert from oneshot BH to persistent BH monitor: reject attempts to delete the current monitor monitor: protect qemu_chr_fe_accept_input with monitor lock monitor: implement support for deleting QMP objects tests/qtest: add tests for dynamic monitor add/remove tests/functional: add e2e test for dynamic QMP monitor hotplug Daniel P. Berrangé (29): qom: replace 'can_be_deleted' with 'prepare_delete' monitor: replace 'common' with 'parent_obj' in MonitorHMP monitor: replace 'common' with 'parent_obj' in MonitorQMP monitor: rename monitor_init* to monitor_new* monitor: minimal conversion of monitors to QOM monitor: pass chardev ID into monitor constructor instead of object monitor: add 'chardev' property to Monitor base class monitor: add 'readline' property to HMP Monitor class monitor: add 'pretty' property to QMP Monitor class monitor: remove 'skip_flush' field monitor: move monitor_data_(init|destroy) into QOM init/finalize monitor: use class methods for monitor_vprintf monitor: use class methods for monitor_qapi_event_emit monitor: use class methods for monitor_accept_input monitor: use class method for I/O thread request monitor: use dynamic cast in monitor_qmp_requests_pop_any_with_lock util: use dynamic cast in error vreport monitor: drop unused monitor_cur_is_qmp monitor: use dynamic cast in QMP commands monitor: use dynamic cast in monitor_is_hmp_non_interactive monitor: drop unused monitor_is_qmp method monitor: eliminate monitor_is_hmp_non_interactive method monitor: implement "user creatable" interface for adding monitors tests/functional: add a stress test for monitor hot unplug qom: add trace events for user creatable create/delete APIs monitor: add support for auto-deleting monitors upon close tests: switch from -mon to -object monitor-qmp qemu-options: document new monitor-hmp and monitor-qmp objects docs: mark '-mon' as deprecated in favour of -object MAINTAINERS | 1 + backends/cryptodev.c | 12 +- backends/hostmem.c | 7 +- backends/iommufd.c | 11 +- block/throttle-groups.c | 12 +- chardev/char.c | 3 +- docs/about/deprecated.rst | 10 + docs/devel/writing-monitor-commands.rst | 4 +- docs/system/arm/xenpvh.rst | 4 +- docs/system/i386/xen.rst | 3 +- docs/system/i386/xenpvh.rst | 4 +- event-loop-base.c | 8 +- gdbstub/system.c | 2 +- include/monitor/monitor.h | 26 +- include/qom/object_interfaces.h | 26 +- include/system/event-loop-base.h | 2 +- migration/migration-hmp-cmds.c | 5 +- monitor/hmp-cmds.c | 7 +- monitor/hmp.c | 181 ++++++++-- monitor/monitor-internal.h | 73 ++-- monitor/monitor.c | 271 ++++++++------- monitor/qmp-cmds-control.c | 12 +- monitor/qmp-cmds.c | 14 +- monitor/qmp.c | 323 +++++++++++++++--- net/can/can_core.c | 6 +- python/qemu/machine/machine.py | 4 +- qapi/qom.json | 63 ++++ qemu-options.hx | 65 +++- qom/object_interfaces.c | 20 +- qom/trace-events | 5 + storage-daemon/qemu-storage-daemon.c | 2 +- stubs/monitor-core.c | 5 - stubs/monitor-internal.c | 4 +- system/vl.c | 19 +- tests/functional/generic/meson.build | 1 + .../generic/test_monitor_hotplug.py | 305 +++++++++++++++++ tests/qemu-iotests/245 | 4 +- tests/qtest/libqtest.c | 2 +- tests/qtest/qmp-test.c | 174 ++++++++++ tests/unit/test-util-sockets.c | 1 - tools/qemu-vnc/stubs.c | 5 - ui/ui-hmp-cmds.c | 2 +- util/error-report.c | 13 +- util/main-loop.c | 6 +- 44 files changed, 1395 insertions(+), 332 deletions(-) create mode 100755 tests/functional/generic/test_monitor_hotplug.py -- 2.55.0

3 46

[PATCH] node_device_udev: fix deadlock joining udev thread under lock
by Christopher Johannimloh 07 Jul '26

07 Jul '26

From: Christopher Johannimloh <C.Johannimloh(a)beckhoff.com> In our CI environment we install and purge all packages we use during a single test. During testing of libvirtd we observed intermittent hangs during apt purge of the libvirt packages. After investigation I found out that the hang is caused by a deadlock in nodeStateShutdownWait() which joins the udev thread while holding the lock of the udevEventData object. The udev thread needs the same lock to make progress and exit, so if the shutdown thread wins the race for the lock the join can never complete and the shutdown thread will later be killed by the 30s timeout [1]. [1] https://gitlab.com/libvirt/libvirt/-/blob/364977b94a776230037aa159be55bb95f… Fixes: e89d39f5b8f30f0b3284ed2bd71cee1a8a3d707d Signed-off-by: Christopher Johannimloh <C.Johannimloh(a)beckhoff.com> --- src/node_device/node_device_udev.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/src/node_device/node_device_udev.c b/src/node_device/node_device_udev.c index 104433fb88..28c8f00361 100644 --- a/src/node_device/node_device_udev.c +++ b/src/node_device/node_device_udev.c @@ -2482,10 +2482,8 @@ nodeStateShutdownWait(void) if (!priv) return 0; - VIR_WITH_OBJECT_LOCK_GUARD(priv) { - if (priv->udevThread) - virThreadJoin(priv->udevThread); - } + if (priv->udevThread) + virThreadJoin(priv->udevThread); if (priv->workerPool) virThreadPoolDrain(priv->workerPool); -- 2.47.3 This email contains confidential information. If you have received it in error, you must not read, use, copy or pass on this e-mail or its attachments. If you have received the e-mail in error, please inform me immediately by reply e-mail and then delete this e-mail from your system. Thank you Diese E-Mail enthält vertrauliche Informationen. Sollten Sie sie irrtümlich erhalten haben, dürfen Sie diese E-Mail oder ihre Anhänge nicht lesen, verwenden, kopieren oder weitergeben. Sollten Sie die Mail versehentlich erhalten haben, teilen Sie mir dies bitte umgehend per Antwort-E-Mail mit und löschen Sie diese E-Mail dann aus Ihrem System. Vielen Dank Beckhoff Automation GmbH & Co. KG Managing Director: Dipl. Phys. Hans Beckhoff Registered office: Verl, Germany Register court: Guetersloh HRA 7075 DisclaimerID:x9d5u140

1 0