qemu/qemu.git/qapi, branch stable-11.1

qapi/dump: add allowed-by-guest feature to win-dmp

2026-08-04T19:21:40+00:00

Commit 1c0e259c5a35 ("dump: make win_dump_available() check vmcoreinfo for a Windows dump header") changed two things in a way that is visible to QMP clients but not to introspection: query-dump-guest-memory-capability now lists win-dmp only for a guest that has published a Windows dump header through the vmcoreinfo device, and dump-guest-memory, which shares win_dump_available(), rejects the format otherwise. Before that, both accepted win-dmp on any x86 machine. A client that wants to select win-dmp automatically therefore cannot trust the capability query on its own: on an older QEMU it reports win-dmp for every x86 guest, Linux ones included, where the resulting dump is useless. libvirt ran into exactly this while picking a format for on_crash and watchdog triggered dumps, and has no way to tell the two behaviours apart. Add an 'allowed-by-guest' feature to the win-dmp member of DumpGuestMemoryFormat so the fixed behaviour becomes discoverable. DumpGuestMemoryFormat is reachable from both query-dump-guest-memory-capability's return type and dump-guest-memory's arguments, so a single flag covers both halves of the change. Where the feature is absent, a reported win-dmp says nothing about the guest, and a client that needs the dump to be loadable afterwards should fall back to elf. CC: Eric Blake CC: Markus Armbruster CC: "Marc-André Lureau" Suggested-by: Daniel P. Berrangé Signed-off-by: Denis V. Lunev Reviewed-by: Daniel P. Berrangé Reviewed-by: Marc-André Lureau Message-ID: <20260731155001.1204103-1-den@openvz.org>

spelling: happend

2026-07-23T14:57:09+00:00

Fixes: 44adb5fcc20d "target/riscv: Remove spike as default machine" Fixes: 48814111366b "migration: Always set DEVICE state" Fixes: 3345fb3b6d7f "migration/postcopy: Add latency distribution report for blocktime" Signed-off-by: Michael Tokarev

qapi: Fix misspelled section tags in doc comments

2026-07-14T08:53:03+00:00

Section tags are case sensitive and end with a colon. Screwing up either gets them interpreted as ordinary paragraph. Fix a few. Fixes: 4e88e7e340 (qapi/qom: Define cache enumeration and properties for machine, 2024-11-01) Fixes: 8eb6d39e22 (qom: qom-list-get, 2025-07-11) Signed-off-by: Markus Armbruster Message-ID: <20260701061136.798815-1-armbru@redhat.com> Reviewed-by: Philippe Mathieu-Daudé

Merge tag 'pull-monitor-2026-07-07' of https://repo.or.cz/qemu/armbru into staging

2026-07-07T17:17:41+00:00

Monitor patches for 2026-07-07 # -----BEGIN PGP SIGNATURE----- # # iQJGBAABCgAwFiEENUvIs9frKmtoZ05fOHC0AOuRhlMFAmpMylQSHGFybWJydUBy # ZWRoYXQuY29tAAoJEDhwtADrkYZTZR0QALmaLG//ZC/AihLLdHHYgQFWQD+2MQiP # l91oqTb+p40q0WhQYzCVYUc+8SMBY6pG6uuzn/qgpsP335uaFEk8c++znyXmbofy # eABrnVETv/SokrvCxwEIZaW49B2gfER2dZ59sLKbvDQN30Dg36dbppHgchWeLO4b # P2kP0veYHSnPx60JE4a0bcvLUO8aaEpb2dkvLOjJdaavJaF1iJURU5CP4hA979PM # xt74cxqhEB6bASLcCJNuGumjmuUHCJGvt0bIGU7L/7a18RAXCw6kJlqfniZWjapC # FMwN5OU8KSq2dy3SjbT6NotUQ8/fLgDqiCsd5gCRPROeAPQ8ZHHqBjyWsdPbHXOo # A5m/XGAqDmWtqBPQkM158RpK20IeGAvTs3LrNQHoFB5f+iLm6dJf0CqbFCj6a4tc # 0w9J7nMUPscEZrJRryjpuYKe82wLrsWTaT3/je/dj2MMDy/Rd6HvjXKhY5P9upHH # SOa8c4L0bG7PpT0paL2cUf03NmyOhWZFx583VID+R/TOQKjyOtdc//eMpuoqpfGU # ggiMDG6VY1+YUZ4/gZ84v/gZDeMJ/9R6rpKGiMJKCOJJUS9znPOPiKKBMI+5Vz0w # 5IrugNKhnfMwCbYS2xFjtop9OFSOQBgLz4/7epKBYltWd4Y3h2Y61WsxxFRg85TL # 4MnzmcrMvoK7 # =Lxcx # -----END PGP SIGNATURE----- # gpg: Signature made Tue 07 Jul 2026 11:43:48 CEST # gpg: using RSA key 354BC8B3D7EB2A6B68674E5F3870B400EB918653 # gpg: issuer "armbru@redhat.com" # gpg: Good signature from "Markus Armbruster " [full] # gpg: aka "Markus Armbruster " [full] # Primary key fingerprint: 354B C8B3 D7EB 2A6B 6867 4E5F 3870 B400 EB91 8653 * tag 'pull-monitor-2026-07-07' of https://repo.or.cz/qemu/armbru: (35 commits) docs: mark '-mon' as deprecated in favour of -object qemu-options: document new monitor-hmp and monitor-qmp objects tests: switch from -mon to -object monitor-qmp monitor: add support for auto-deleting monitors upon close qom: add trace events for user creatable create/delete APIs tests/functional: add a stress test for monitor hot unplug tests/functional: add e2e test for dynamic QMP monitor hotplug tests/qtest: add tests for dynamic monitor add/remove monitor: implement support for deleting QMP objects monitor: protect qemu_chr_fe_accept_input with monitor lock monitor: reject attempts to delete the current monitor monitor: convert from oneshot BH to persistent BH monitor: implement "user creatable" interface for adding monitors monitor: eliminate monitor_is_hmp_non_interactive method monitor: drop unused monitor_is_qmp method monitor: use dynamic cast in monitor_is_hmp_non_interactive monitor: use dynamic cast in QMP commands monitor: drop unused monitor_cur_is_qmp util: use dynamic cast in error vreport monitor: use dynamic cast in monitor_qmp_requests_pop_any_with_lock ... Signed-off-by: Stefan Hajnoczi

monitor: add support for auto-deleting monitors upon close

2026-07-07T09:16:27+00:00

The default monitor is usually a long lived object that will exist for the entire lifetime of the VM. A monitor can only service a single client at a time though, and so it might be desirable to hotplug additional monitors at runtime for specific tasks. If doing that, however, there is a need to remove the monitor when it is no longer needed. A use case for hotplugging a monitor can involve a user wishing to spawn an ad hoc script that uses a temporary monitor. The script can ask the management application to hotplug a monitor and pass back a pre-opened FD using SCM_RIGHTS. In this case the lifetime of the script is not tied to the management application and thus it is desirable to have automatic cleanup when the script exits. Allowing a client to run "object-del" against its own monitor adds complex edge cases, as it would be desirable to send the QMP response despite the monitor sending it being deleted. Doing "object-del" alone will also result in orphaning a character device backend instance, as there is no opportunity to run the companion "chardev-del" command. A simpler way to ensure cleanup is to add the concept of auto-deleting monitor objects. Specifically when the "CHR_EVENT_CLOSED" event is emitted, the equivalent of "object-del" + "chardev-del" can be run internally. Since the transient client has already droppped its monitor connection, there is no synchronization to be concerned about with sending QMP replies. There is still some internal synchronization needed, however, between the character device event callback and the bottom-half that runs the delete. There is a chance that an incoming client connection may arise before the bottom-half runs, which has to be checked. Once the monitor object is deleted, the event callback is unregistered from the character device, eliminating any further races before the character device is fully deleted. This is implemented via a new "close-action=none|delete" property on the 'monitor-qmp' object. This concept could be extended with further actions in future, for example: * close-action=shutdown - graceful guest shutdown * close-action=terminate - immediate guest poweroff * close-action=stop - pause guest CPUs while the monitor is not connected to any client This is left as an exercise for future interested contributors. Tested-by: Peter Krempa Reviewed-by: Marc-André Lureau Acked-by: Markus Armbruster Signed-off-by: Daniel P. Berrangé Message-ID: <20260706135824.2623960-33-berrange@redhat.com> [Commit message typos fixed] Signed-off-by: Markus Armbruster

monitor: implement "user creatable" interface for adding monitors

2026-07-07T09:16:25+00:00

Implement the user creatable QOM interface and define the monitor-qmp and monitor-hmp types in QAPI. This unlocks the ability to create them on the command line with -object or in HMP/QMP with object_add. For example: $QEMU -chardev stdio,id=monchr0 -object monitor-hmp,id=mon0,chrdev=monchr0 Initially the "prepare_delete" callback is hardcoded to return an error which means -object and object_add can be used, but object_del will fail. Support for deleting monitors will be introduced in subsequent commits. Reviewed-by: Marc-André Lureau Tested-by: Peter Krempa Acked-by: Markus Armbruster Signed-off-by: Daniel P. Berrangé Message-ID: <20260706135824.2623960-24-berrange@redhat.com> Signed-off-by: Markus Armbruster

migration: Fix "switchover" used as a verb in comments and docs

2026-07-07T05:12:46+00:00

"Switchover" is a noun; the verb form is "switch over". Replace all instances where "switchover" was incorrectly used as a verb in comments and documentation. Signed-off-by: Avihai Horon Reviewed-by: Cédric Le Goater Link: https://lore.kernel.org/qemu-devel/20260706085211.13905-17-avihaih@nvidia.com Signed-off-by: Cédric Le Goater

migration: Make switchover-ack re-usable

2026-07-07T05:12:46+00:00

Switchover-ack is a mechanism to synchronize between source and destination QEMU during migration to prevent the source from switching over prematurely. VFIO uses switchover-ack to ensure switchover happens only after destination side has loaded the precopy initial bytes. This is important for VFIO, as otherwise downtime could be impacted and be higher. In its current state, switchover-ack is a one-time mechanism, meaning that switchover is acked only once and past that another ACK cannot be requested again. This was sufficient until now, as VFIO precopy initial bytes was defined to be monotonically decreasing. Thus, when precopy initial bytes reached zero for all VFIO devices, a single ACK would be sent and its validity would hold. However, now the new VFIO_PRECOPY_INFO_REINIT feature allows precopy initial bytes to be re-initialized during precopy. Specifically, it means that initial bytes can grow after reaching zero, which would invalidate a previously sent switchover ACK. To solve this, make switchover-ack reusable and allow devices to request switchover ACKs when needed via the save_query_pending SaveVMHandler. Since now switchover ACK can be requested for a specific device and in different times, make switchover ACK per-device (instead of a single ACK for all devices) and let source side do the pending ACKs accounting. Keep the legacy switchover-ack mechanism for backward compatibility and turn it on by a compatibility property for older machines. Enable the property until VFIO implements the new switchover-ack. Acked-by: Markus Armbruster Signed-off-by: Avihai Horon Link: https://lore.kernel.org/qemu-devel/20260706085211.13905-8-avihaih@nvidia.com Signed-off-by: Cédric Le Goater

qapi, hmp: introspection for the sp-mem device

2026-07-04T01:21:07+00:00

Add a SpMemDeviceInfo variant to MemoryDeviceInfo so `query-memory-devices` reports each sp-mem instance (id, addr, size, node, memdev), and print it from HMP `info memory-devices`. Signed-off-by: FangSheng Huang Reviewed-by: Igor Mammedov Reviewed-by: David Hildenbrand (Arm) Reviewed-by: Michael S. Tsirkin Signed-off-by: Michael S. Tsirkin Message-ID: <20260623075051.3797975-3-FangSheng.Huang@amd.com>

qapi/migration: Remove @cpr-exec-command doc in MigrationParameter

2026-06-22T21:08:48+00:00

This parameter was developed during similar window when the deduplication work was done in commit 2220c2b9ef ("qapi/migration: Don't document MigrationParameter"), hence it was overlooked. Remove the leftover parameter. After all, MigrationParameter is already in the exception list of the doc sanity checker. Reviewed-by: Fabiano Rosas Reviewed-by: Markus Armbruster Link: https://lore.kernel.org/r/20260528201236.359452-1-peterx@redhat.com Signed-off-by: Peter Xu