June 2026 - Devel - libvirt List Archives

[PATCH 0/8] Testcase improvements and Power8E/NVL removal
by Aditya Gupta 24 Jun '26

24 Jun '26

Overview ======== This patch series merges two patch series sent earlier: "Testcase improvements for PowerNV" "Remove deprecated Power8E and 8NVL CPUs" since the Power8E removal series depended on the former due to pnv-spi test Broadly contains 3 changes: 1. Testcase improvements: Add a testcase to detect regression in remote interrupts when XIVE changes, since such regression had occurred during Power11 XIVE changes: https://lore.kernel.org/qemu-devel/baf6c854-832b-4a2e-922f-d34e6dadf821@red… Also add Power11 chip and testcase in qtests, and fadump functional test 2. Power8E/Power8NVL removal Power8E and Power8NVL were deprecated since QEMU 10.1, with commit 264a604e7163 ("target/ppc: Deprecate Power8E and Power8NVL") Hence, remove usage (chip and core types) of Power8E and 8NVL from PowerNV, PSeries as well as testcases. 3. Maintainer changes Add myself as maintainer for PowerNV machine Testing ======= * Git tree for testing: https://gitlab.com/adi-g15-ibm/qemu/tree/feat_maintainer_refresh * Gitlab pipeline: https://gitlab.com/adi-g15-ibm/qemu/-/pipelines/2622995621 * Successful ppc64 functional tests, qtests, boot tests, builds at all commits Changelog ========= from previous split series: + #1: added checks to see if network is up and interrupts happened, based on shivang's review + #3: replaced common if-else-if check for machine type with pnv_get_machine_type + #7: added doc in removed-features, as suggested by cedric + #6,7: added rb from philippe + #8: new patch, maintainer change Aditya Gupta (8): tests/functional: Add remote interrupts test for PowerNV tests/qtest/pnv_spi: Test Power11 PNV_SPI tests/qtest: Add Power11 chip & machine to qtests tests/functional: Use default powernv machine instead of power10 ppc/pnv: Replace Power8E with Power11 for 'none' machine test ppc/pnv: Remove Power8E and Power8NVL pnv chips ppc/pnv: Remove Power8E and Power8NVL CPUs MAINTAINERS: Add self as maintainer for PowerNV MAINTAINERS | 3 +- docs/about/deprecated.rst | 9 --- docs/about/removed-features.rst | 8 +++ docs/system/ppc/powernv.rst | 2 +- docs/system/ppc/pseries.rst | 2 +- hw/ppc/pnv.c | 62 ------------------- hw/ppc/pnv_core.c | 2 - hw/ppc/spapr_cpu_core.c | 2 - include/hw/ppc/pnv.h | 8 --- target/ppc/cpu-models.c | 6 -- target/ppc/cpu-models.h | 4 -- target/ppc/cpu_init.c | 6 -- target/ppc/kvm.c | 4 +- tests/functional/ppc64/test_fadump.py | 2 +- tests/functional/ppc64/test_powernv.py | 86 ++++++++++++++++++++++++++ tests/qtest/machine-none-test.c | 2 +- tests/qtest/pnv-host-i2c-test.c | 7 +-- tests/qtest/pnv-spi-seeprom-test.c | 21 +++++-- tests/qtest/pnv-xive2-test.c | 2 +- tests/qtest/pnv-xscom-test.c | 19 ++---- tests/qtest/pnv-xscom.h | 42 +++++++++---- 21 files changed, 154 insertions(+), 145 deletions(-) base-commit: b83371668192a705b878e909c5ae9c1233cbd5fb -- 2.54.0

3 12

[RFC PATCH 0/3] Arm CPU features with supported values
by sandesh.patel＠nutanix.com 24 Jun '26

24 Jun '26

From: Sandesh Patel <sandesh.patel(a)nutanix.com> Hi, This RFC series adds libvirt support for ARM CPU features that are exposed by QEMU as multi-valued properties, rather than the on/off booleans we are used to from x86. Background ========== On ARM, several CPU properties can take one of a small set of values (e.g. "0.0", "1.0", "1.1_base", "off"), and the set of values supported by each property is host-specific. This cannot be expressed using libvirt's existing boolean feature model. This series depends on a pending QEMU RFC [1] that introduces non-boolean feature handling for ARM CPUs. That series also adds a new QMP command, query-arm-cpu-props-info, which reports the values the host accelerator supports for each ARM CPU property. Example reply fragment: { "name": "hw_prop_WRPs", "supported-values": ["0-3"], "type": "number" } On top of that QEMU work, this libvirt RFC wires up the end-to-end flow: probing the host, caching the probed information, exposing the values in the guest CPU XML, and passing them through to the QEMU -cpu command line. I am posting this as an RFC primarily to get maintainer feedback on the overall approach before investing in the missing pieces (in particular, value validation, which is intentionally not yet implemented). See "Open questions" below. Overview of the series ====================== 1. "Query supported ARM CPU property values from QEMU" Adds the QMP wrapper for query-arm-cpu-props-info, a new QEMU_CAPS_QUERY_ARM_CPU_PROPS_INFO capability bit, and the qemuMonitorCPUPropsInfoList data structure. The command is issued on ARM + KVM hosts and the reply is stored in the per-accelerator capabilities. 2. "Cache ARM CPU property information" Persists the probed list into the on-disk QEMU capabilities cache as <cpuPropertyInfo>, so that subsequent libvirtd restarts do not need to re-issue the QMP query. 3. "Support 'value' attribute on CPU features" Extends the guest CPU XML with an optional 'value' attribute on <feature>: <cpu mode='host-passthrough'> <feature policy='require' name='feat_RAS' value='1.0'/> <feature policy='require' name='hw_prop_API' value='off'/> <feature policy='enable' name='hw_prop_WRPs' value='2'/> </cpu> When a feature carries a non-NULL 'value', libvirt emits '<name>=<value>' on the QEMU -cpu command line; in that case the policy must be 'require' or 'force'. The existing policy-driven '=on' / '=off' path is used only for features without an explicit value. All ARM property names returned by query-arm-cpu-props-info are registered in src/cpu_map/arm_features.xml so that the guest XML parser and validator accept them. With this change, the generated QEMU command line can look like: -cpu host-passthrough,hw_prop_API=off,hw_prop_WRPs=2 Open questions ============== - Value validation: should libvirt validate the requested value against the host's supported-values list at define time, at start time, or defer entirely to QEMU? - Policy vs. value conflicts: is requiring policy='require' / 'force' whenever 'value' is set the right rule? - Caching location: is the per-accelerator QEMU capabilities cache the right place to store the probed property list, or should this live alongside the CPU model data in cpu_map? [1] https://lore.kernel.org/qemu-arm/20260605083358.1320563-1-khushit.shah@nuta… Thanks Sandesh Patel (3): Query supported ARM CPU property values from QEMU Cache ARM CPU property information Support 'value' attribute on CPU features src/conf/cpu_conf.c | 21 ++- src/conf/cpu_conf.h | 1 + src/conf/schemas/cputypes.rng | 5 + src/cpu_map/arm_features.xml | 170 ++++++++++++++++++ src/qemu/qemu_capabilities.c | 133 +++++++++++++- src/qemu/qemu_capabilities.h | 1 + src/qemu/qemu_command.c | 13 ++ src/qemu/qemu_monitor.c | 51 ++++++ src/qemu/qemu_monitor.h | 26 +++ src/qemu/qemu_monitor_json.c | 66 +++++++ src/qemu/qemu_monitor_json.h | 5 + .../caps_11.1.0_aarch64.replies | 69 +++++++ .../caps_11.1.0_aarch64.xml | 14 ++ tests/qemumonitorjsontest.c | 91 ++++++++++ ...arch64-cpu-passthrough.aarch64-latest.args | 2 +- ...aarch64-cpu-passthrough.aarch64-latest.xml | 6 +- .../aarch64-cpu-passthrough.xml | 6 +- tests/testutilshostcpus.h | 74 ++++---- 18 files changed, 709 insertions(+), 45 deletions(-) -- 2.43.7

2 4

[PATCH] spec: Enable hyperv driver on RHEL
by Michal Privoznik 24 Jun '26

24 Jun '26

From: Michal Privoznik <mprivozn(a)redhat.com> Resolves: https://redhat.atlassian.net/browse/RHEL-187057 Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com> --- Green pipeline: https://gitlab.com/MichalPrivoznik/libvirt/-/pipelines/2625120614 libvirt.spec.in | 1 - 1 file changed, 1 deletion(-) diff --git a/libvirt.spec.in b/libvirt.spec.in index 2fddfcd606..f7f683e1c5 100644 --- a/libvirt.spec.in +++ b/libvirt.spec.in @@ -145,7 +145,6 @@ %define with_vbox 0 %define with_vmware 0 %define with_libxl 0 - %define with_hyperv 0 %define with_lxc 0 %define with_ch 0 %endif -- 2.53.0

2 1

Re: [PATCH v4 34/35] qemu-options: document new monitor-hmp and monitor-qmp objects
by Daniel P. Berrangé 23 Jun '26

23 Jun '26

On Tue, Jun 23, 2026 at 05:58:43PM +0000, Dr. David Alan Gilbert wrote: > * Daniel P. Berrangé (berrange(a)redhat.com) wrote: > > Add new docs for the `-object monitor-hmp` and `-object monitor-qmp` > > options, updating `-mon` to state that it is legacy syntax sugar > > for the new `-object` args. > > > > Signed-off-by: Daniel P. Berrangé <berrange(a)redhat.com> > > --- > > qemu-options.hx | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ > > 1 file changed, 50 insertions(+) > > > > diff --git a/qemu-options.hx b/qemu-options.hx > > index c799286153..98c74cc9ff 100644 > > --- a/qemu-options.hx > > +++ b/qemu-options.hx > > <snip> > > > @@ -5730,6 +5740,46 @@ SRST > > they are specified. Note that the 'id' property must be set. These > > objects are placed in the '/objects' path. > > > > + ``-object monitor-hmp,id=id,chardev=chardev_id,readline=on|off`` > > + Set up a monitor running the Human Monitor Protocol, > > + connected to the chardev ``chardev_id``. > > + > > + The ``id`` parameter is a unique ID that can be used > > + to dynamically delete the monitor at runtime. Note > > + that monitors created using the historical syntax > > + will be allocated IDs following the pattern ``hmpcompatNN``. > > + Mixing ``-object`` with the historical monitor syntax is > > + discouraged. > > + > > + The ``readline`` parameter, which defaults to ``on``, > > + controls whether the monitor provides interactive > > + prompts > > Missing full stop. > So are you allowing a mode that I don't think was previously possible; > HMP syntax but without readline? Yeah, I guess that's true - the non-interactive mode was always there internally but only accessible via the gdb stub. > 'interactive prompts' seems a strange way of putting it - 'line editing' > is more normal isn't it? Sure, I can change that. 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 :|

1 0

[PATCH 00/14] qemu: fix lock/log daemon shutdown ordering and issues with locking in paused VMs
by Peter Krempa 23 Jun '26

23 Jun '26

Patch 1 fixes ordering of shutdown of the helper daemons virtlogd/virtlockd. The rest of the series addresses few issues with locking of disk images via lockd/sanlock in terms of hotplug to a paused VM. The patches also prevent combination of automatic disk locking and blockjobs because it was historically broken and the usage of that is minimal, we thus just enforce the safe state. Peter Krempa (14): qemu: Ensure proper shutdown ordering of virtlockd/virtlogd daemons qemuDomainAttachLease: Directly insert the lease Remove virDomainLeaseInsertPreAlloc/virDomainLeaseInsertPreAlloced qemu.conf: Explain that no locking happens if 'lock_manager' is unset virDomainLeaseDefParseXML: Report error if '<lockspace>' element is missing virDomainLeaseDefParseXML: Avoid unneeded temporary variables qemuxmlconftest: Add <lease> with missing offset locking: Debug lockspace creation lock_daemon: Log arguments for all dispatched APIs lockd driver: Allow registering additional lockspaces for manual <lease>s qemu: hotplug: Don't acquire lock on hotplugged <lease> when VM is paused locking: Add API to query whether automatic disk leases are enabled qemu: Refuse block jobs if automatic disk leases are enabled in the locking plugin qemu: Fix lock manager usage for disks src/conf/domain_conf.c | 38 ++++--------- src/conf/domain_conf.h | 4 +- src/libvirt_private.syms | 3 +- src/locking/libvirt_lockd.aug | 8 +++ src/locking/lock_daemon.c | 3 + src/locking/lock_daemon_dispatch.c | 24 +++++++- src/locking/lock_driver.h | 10 ++++ src/locking/lock_driver_lockd.c | 22 ++++++++ src/locking/lock_driver_sanlock.c | 9 +++ src/locking/lock_manager.c | 10 ++++ src/locking/lock_manager.h | 2 + src/locking/lockd.conf | 14 +++++ src/locking/sanlock.conf | 4 ++ src/locking/test_libvirt_lockd.aug.in | 4 ++ src/qemu/qemu.conf.in | 5 ++ src/qemu/qemu_backup.c | 2 +- src/qemu/qemu_block.c | 2 +- src/qemu/qemu_checkpoint.c | 2 +- src/qemu/qemu_domain.c | 21 +++---- src/qemu/qemu_domain.h | 3 +- src/qemu/qemu_driver.c | 4 +- src/qemu/qemu_hotplug.c | 56 +++++++++++++++---- src/qemu/qemu_snapshot.c | 25 +++++---- src/qemu/virtqemud.service.extra.in | 4 ++ src/remote/libvirtd.service.in | 4 ++ src/util/virlockspace.c | 6 +- tests/qemuxmlconfdata/lease.x86_64-latest.xml | 5 ++ tests/qemuxmlconfdata/lease.xml | 5 ++ 28 files changed, 221 insertions(+), 78 deletions(-) -- 2.54.0

3 21

[PATCH v4 00/35] monitor: turn QMP and HMP into QOM objects
by Daniel P. Berrangé 23 Jun '26

23 Jun '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 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: 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 method for getting the "id" of a QOM object 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 | 10 +- backends/hostmem.c | 5 +- backends/iommufd.c | 10 +- block/throttle-groups.c | 10 +- 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 | 4 +- include/monitor/monitor.h | 23 +- include/qom/object.h | 10 + 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 | 262 ++++++++------- monitor/qmp-cmds-control.c | 12 +- monitor/qmp-cmds.c | 14 +- monitor/qmp.c | 312 +++++++++++++++--- net/can/can_core.c | 5 +- python/qemu/machine/machine.py | 4 +- qapi/qom.json | 62 ++++ qemu-options.hx | 57 +++- qom/object.c | 17 + 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 | 3 +- system/vl.c | 12 +- tests/functional/generic/meson.build | 1 + .../generic/test_monitor_hotplug.py | 277 ++++++++++++++++ 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 | 5 +- 46 files changed, 1352 insertions(+), 327 deletions(-) create mode 100755 tests/functional/generic/test_monitor_hotplug.py -- 2.54.0

4 44

[PATCH 0/7] qemu: Switch over to '-object monitor-qmp'
by Peter Krempa 23 Jun '26

23 Jun '26

Patches 1-4 are cleanups that can be applied right away. Patch 5 will be replaced by a proper capability update once the qemu patches hit upstream. Patches 6-7 are to be merged as-is once the qemu patches hit upstream. S-o-b for patches 5-7 will be applied once they are ready to be pushed (to prevent accidental push). Peter Krempa (7): qemucapabilitiestest: Update 'caps_11.1.0_x86_64' to 'v11.0.0-2279-gb833716681' qemucapabilitiestest: Update 'caps_11.1.0_aarch64' to 'v11.0.0-2279-gb833716681' qemuMonitorJSONIOProcessLine: Log monitor object pointer in debug message qemu: monitor: Standardize log format in QEMU_CHECK_MONITOR_FULL macro qeucapabilitiestest: Update data for 'monitor-qmp' object qemu: capabilities: Introduce QEMU_CAPS_OBJECT_MONITOR_QMP qemu: command: Use monitor via '-object monitor-qmp,...' 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 | 58 +- .../caps_11.1.0_aarch64.xml | 2 +- .../caps_11.1.0_x86_64.replies | 1905 +++++++++-------- .../caps_11.1.0_x86_64.xml | 5 +- .../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 +- .../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 +- .../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-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-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 +- ...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 +- ...-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 +- ...-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 +- ...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 +- ...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 +- ...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 +- ...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 +- ...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 +- ...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 +- .../iommufd-q35-fd.x86_64-latest.args | 2 +- .../iommufd-q35.x86_64-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 +- .../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 +- .../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.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-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 +- ...tomatic-unavailable-q35.x86_64-latest.args | 2 +- ...ntroller-default-i440fx.x86_64-latest.args | 2 +- ...-controller-default-q35.x86_64-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-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 +- 837 files changed, 1877 insertions(+), 1777 deletions(-) -- 2.54.0

1 7

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

23 Jun '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

1 6

[PATCH v1 0/7] Add TLS-PSK support for migration
by Abhisek Panda 23 Jun '26

23 Jun '26

QEMU provides the ability 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, the patch series introduce the alternative 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. During a migration, the parties negotiate which unique key to utilize for encrypting the migration data. To improve the security further, we utilize different key files for each migration session. Abhisek Panda (7): conf: Add configuration params for TLS-PSK include: define VIR_MIGRATE_TLS_PSK flag 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: define VIR_MIGRATE_PARAM_TLS_PSK_DIRECTORY include/libvirt/libvirt-domain.h | 31 ++- src/qemu/libvirtd_qemu.aug | 2 + src/qemu/qemu.conf.in | 27 ++- src/qemu/qemu_alias.c | 19 +- src/qemu/qemu_alias.h | 5 +- src/qemu/qemu_backup.c | 2 +- src/qemu/qemu_command.c | 31 ++- src/qemu/qemu_command.h | 8 + src/qemu/qemu_conf.c | 55 ++++- src/qemu/qemu_conf.h | 3 + src/qemu/qemu_domain.c | 2 +- src/qemu/qemu_driver.c | 24 ++- src/qemu/qemu_hotplug.c | 125 +++++++---- src/qemu/qemu_hotplug.h | 43 ++-- src/qemu/qemu_migration.c | 194 ++++++++++++------ src/qemu/qemu_migration.h | 3 + src/qemu/qemu_migration_params.c | 138 ++++++++++--- src/qemu/qemu_migration_params.h | 28 ++- src/qemu/qemu_postparse.c | 2 +- src/qemu/test_libvirtd_qemu.aug.in | 2 + 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/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 +- tests/testutilsqemu.c | 2 + tools/virsh-domain.c | 12 ++ 39 files changed, 623 insertions(+), 209 deletions(-) -- 2.39.3

4 18

[RFC] sanlock: Add option to check ownership of disk leases
by Jim Fehlig 22 Jun '26

22 Jun '26

From: Jim Fehlig <jfehlig(a)suse.com> In a clustered environment it may be desirable to provision disk leases for use by a specific domain. This patch adds a 'check_disk_lease_owner' option to the sanlock driver to check that leases are owned by the domain attempting to acquire them. sanlock's Lock Value Block (LVB) is used to store the owning domain UUID within the lease. When a domain is started and attempts to acquire its leases, the sanlock driver will ensure its UUID matches the UUID recorded in the leases. Any mismatches will cause lease acquisition and domain startup to fail. The 'check_disk_lease_owner' option is disabled by default. When enabled, it can be used with auto_disk_leases or leases managed by an external application. Signed-off-by: Jim Fehlig <jfehlig(a)suse.com> --- Inspired by Claudio, implemented by Jim :-) src/locking/libvirt_sanlock.aug | 1 + src/locking/lock_driver_sanlock.c | 78 ++++++++++++++++++++++++- src/locking/sanlock.conf | 23 ++++++++ src/locking/test_libvirt_sanlock.aug.in | 1 + 4 files changed, 102 insertions(+), 1 deletion(-) diff --git a/src/locking/libvirt_sanlock.aug b/src/locking/libvirt_sanlock.aug index 62d0672952..af6c25755f 100644 --- a/src/locking/libvirt_sanlock.aug +++ b/src/locking/libvirt_sanlock.aug @@ -25,6 +25,7 @@ module Libvirt_sanlock = | int_entry "io_timeout" | str_entry "user" | str_entry "group" + | bool_entry "check_disk_lease_owner" let comment = [ label "#comment" . del /#[ \t]*/ "# " . store /([^ \t\n][^\n]*)?/ . del /\n/ "\n" ] let empty = [ label "#empty" . eol ] diff --git a/src/locking/lock_driver_sanlock.c b/src/locking/lock_driver_sanlock.c index a07f3652c1..7ed1081cbd 100644 --- a/src/locking/lock_driver_sanlock.c +++ b/src/locking/lock_driver_sanlock.c @@ -67,6 +67,7 @@ struct _virLockManagerSanlockDriver { unsigned int hostID; bool autoDiskLease; char *autoDiskLeasePath; + bool checkDiskLeaseOwner; unsigned int io_timeout; /* under which permissions does sanlock run */ @@ -147,6 +148,10 @@ virLockManagerSanlockLoadConfig(virLockManagerSanlockDriver *driver, if (virConfGetValueBool(conf, "require_lease_for_disks", &driver->requireLeaseForDisks) < 0) return -1; + if (virConfGetValueBool(conf, "check_disk_lease_owner", + &driver->checkDiskLeaseOwner) < 0) + return -1; + if (virConfGetValueUInt(conf, "io_timeout", &driver->io_timeout) < 0) return -1; @@ -839,6 +844,73 @@ virLockManagerSanlockRegisterKillscript(int sock, return 0; } +static int virLockManagerSanlockCheckOwner(virLockManagerSanlockDriver *driver, + virLockManagerSanlockPrivate *priv) +{ + char lvb[VIR_UUID_STRING_BUFLEN] = {0}; + char vm_uuidstr[VIR_UUID_STRING_BUFLEN]; + int rv; + size_t i; + + if (!driver->checkDiskLeaseOwner) + return 0; + + virUUIDFormat(priv->vm_uuid, vm_uuidstr); + + for (i = 0; i < priv->res_count; i++) { + memset(lvb, 0, sizeof(lvb)); + + rv = sanlock_get_lvb(0, priv->res_args[i], lvb, sizeof(lvb)); + if (rv < 0) { + /* Failed to read LVB, treat as "legacy" lease + * without ownership tracking and skip the check. + */ + VIR_DEBUG("Failed to read LVB, skipping ownership check"); + continue; + } + + if (lvb[0] == '\0') { + VIR_DEBUG("Writing VM UUID to empty LVB"); + /* Empty LVB: this lease does not yet have an owner recorded. Write + * the domain's UUID so that subsequent acquire attempts by other + * domains will be rejected. This handles the auto_disk_leases case + * where lease files are created by libvirt. rather + */ + if ((rv = sanlock_set_lvb(0, priv->res_args[i], vm_uuidstr, + sizeof(vm_uuidstr))) < 0) { + char *err = NULL; + if (virLockManagerSanlockError(rv, &err)) { + virReportError(VIR_ERR_INTERNAL_ERROR, + _("Failed to set LVB for lease %1$s: %2$s"), + priv->res_args[i]->disks[0].path, NULLSTR(err)); + VIR_FREE(err); + } else { + virReportSystemError(-rv, + _("Failed to set LVB for lease %1$s"), + priv->res_args[i]->disks[0].path); + } + return -1; + } + continue; + } + + VIR_DEBUG("Comparing LVB UUID '%s' to VM UUID '%s'", lvb, vm_uuidstr); + if (STRNEQ(lvb, vm_uuidstr)) { + /* + * LVB contains a different domain UUID. This lease + * was provisioned for another domain and must not + * be acquired by this one. + */ + virReportError(VIR_ERR_RESOURCE_BUSY, + _("Disk lease %1$s is already assigned to domain %2$s, not %3$s"), + priv->res_args[i]->disks[0].path, lvb, vm_uuidstr); + return -1; + } + } + return 0; +} + + static int virLockManagerSanlockAcquire(virLockManager *lock, const char *state, unsigned int flags, @@ -934,7 +1006,8 @@ static int virLockManagerSanlockAcquire(virLockManager *lock, if (!(flags & VIR_LOCK_MANAGER_ACQUIRE_REGISTER_ONLY)) { VIR_DEBUG("Acquiring object %u", priv->res_count); - if ((rv = sanlock_acquire(sock, priv->vm_pid, 0, + if ((rv = sanlock_acquire(sock, priv->vm_pid, + driver->checkDiskLeaseOwner ? SANLK_ACQUIRE_LVB : 0, priv->res_count, priv->res_args, opt)) < 0) { char *err = NULL; @@ -949,6 +1022,9 @@ static int virLockManagerSanlockAcquire(virLockManager *lock, } goto error; } + + if (virLockManagerSanlockCheckOwner(driver, priv) < 0) + goto error; } VIR_FREE(opt); diff --git a/src/locking/sanlock.conf b/src/locking/sanlock.conf index 3c356bef9c..e7d6938e84 100644 --- a/src/locking/sanlock.conf +++ b/src/locking/sanlock.conf @@ -67,3 +67,26 @@ # access them. Accepted values are described in qemu.conf. #user = "root" #group = "root" + +# +# Flag to enable verifying if disk leases have been provisioned +# for domains attempting to acquire them. This is accomplished +# using sanlock's Lock Value Block (LVB), a 512 byte application +# specific block in the lease lockspace where the domain's UUID +# can be stored when the lease is created. When libvirt starts a +# domain, the sanlock driver will check for a valid and matching +# UUID in the LVB of all leases. This prevents a lease that was +# provisioned for one domain from accidentally being used by a +# different domain. +# +# When enabled, if a lease file has an empty LVB, the UUID of the +# acquiring domain is written into the LVB automatically, so that +# subsequent lease acquisition attempts by other domains will be +# rejected. This behavior accommodates the auto_disk_leases case, +# where leases are created by libvirt. If leases are managed by +# an external application, it must write the domain UUID into the +# LVB during lease creation. +# +# Defaults to disabled. +# +#check_disk_lease_owner = 0 diff --git a/src/locking/test_libvirt_sanlock.aug.in b/src/locking/test_libvirt_sanlock.aug.in index 5eabb6726d..e468a2cdcd 100644 --- a/src/locking/test_libvirt_sanlock.aug.in +++ b/src/locking/test_libvirt_sanlock.aug.in @@ -9,3 +9,4 @@ module Test_libvirt_sanlock = { "io_timeout" = "0" } { "user" = "root" } { "group" = "root" } +{ "check_disk_lease_owner" = "0" } -- 2.51.0

1 0