- Devel - libvirt List Archives

Re: [PATCH v3 07/11] ui/dbus: run without Audio interface when audio is disabled
by Markus Armbruster 01 Apr '26

01 Apr '26

Sergei Heifetz <heifetz(a)yandex-team.com> writes: > D-Bus display can be used even when QEMU is configured with > `--disable-audio`. In that case, audio interface will not be available > on `/org/qemu/Display1/Audio`. > > (The current handling of the situation when audio is enabled but > no D-Bus-compatible audio backend is available is different and > hasn’t been changed.) > > Signed-off-by: Sergei Heifetz <heifetz(a)yandex-team.com> > --- > qapi/ui.json | 2 +- > qemu-options.hx | 4 ++++ > ui/dbus.c | 8 ++++++++ > 3 files changed, 13 insertions(+), 1 deletion(-) > > diff --git a/qapi/ui.json b/qapi/ui.json > index e3da77632a8..62eb05c6091 100644 > --- a/qapi/ui.json > +++ b/qapi/ui.json > @@ -1385,7 +1385,7 @@ > 'data' : { '*rendernode' : 'str', > '*addr': 'str', > '*p2p': 'bool', > - '*audiodev': 'str' } } > + '*audiodev': { 'type': 'str', 'if': 'CONFIG_AUDIO' } } } Is this a compatibility break? DisplayDBus is only used in DisplayOptions, which is only used as return type of query-display-options in the QAPI schema. However, vl.c also uses it to parse -display. Removing parameter @audiodev from -display is technically a compatibility break. However, we're removing an optional paramater that would always be rejected when present: it has no valid value, because there are no audiodevs. Removal from query-display-options is similar: it could not be present. Removal affects introspection, which could conceivably confuse client. I don't expect such trouble here, because @audiodev always existed, i.e. there's no real reason to look for it in introspection. I think we're okay. I'm cc'ing the libvirt list just in case. Do we need a release note? Do we need an entry in docs/about/removed-features.rst? Feels a bit odd; we're not removing a feature, we're adding one, namely "can compile out audio". > > ## > # @DisplayGLMode: > diff --git a/qemu-options.hx b/qemu-options.hx > index 29dc865820a..20d15c0004f 100644 > --- a/qemu-options.hx > +++ b/qemu-options.hx > @@ -2232,6 +2232,10 @@ SRST > If no audio backend is specified and the dbus display backend is > specified, the dbus audio backend is used by default. > > + (If audio is disabled at compile time via the ``--disable-audio`` option, > + no audio backend is used, and none of the audio-related D-Bus interfaces > + are exported.) > + Well, audio is either compiled in or it isn't. If it's compiled in, then why tell the user how things behave when it's not? If it's not compiled in, then why document stuff that doesn't work? How much of -audiodev still works then? -audiodev none? Anything else? > The connection is registered with the "org.qemu" name (and queued when > already owned). > [...]

3 4

Re: [PATCH RFC 02/12] migration/qapi: Rename MigrationStats to MigrationRAMStats
by Markus Armbruster 01 Apr '26

01 Apr '26

Cc: correct libvirt list address Peter Xu <peterx(a)redhat.com> writes: > This stats is only about RAM, so make it accurate. This paves way for > statistics for all devices. > > Note that even if this is part of qapi/, this should not be part of ABI of docs/devel/qapi-code-gen.rst section "Compatibility considerations": Since type names are not visible in the Client JSON Protocol, types may be freely renamed. Even certain refactorings are invisible, such as splitting members from one type into a common base type. So, s/should not be/is not/. > at least query-migrate, because the structure is not changed, and this > stats is always reported only under the "ram" section. Why "at least query-migrate"? Do you have other interfaces in mind, or are you just hedging? > Cc: Daniel P. Berrangé <berrange(a)redhat.com> > Cc: Markus Armbruster <armbru(a)redhat.com> > Cc: Libvirt Mailing List <libvir-list(a)redhat.com> > Signed-off-by: Peter Xu <peterx(a)redhat.com> > --- > docs/about/removed-features.rst | 2 +- > qapi/migration.json | 8 ++++---- > migration/migration-stats.h | 2 +- > 3 files changed, 6 insertions(+), 6 deletions(-) > > diff --git a/docs/about/removed-features.rst b/docs/about/removed-features.rst > index 6f4447993c..7c4f4325f7 100644 > --- a/docs/about/removed-features.rst > +++ b/docs/about/removed-features.rst > @@ -699,7 +699,7 @@ was superseded by ``sections``. > ``query-migrate`` return value member ``skipped`` (removed in 9.1) > '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' > > -Member ``skipped`` of the ``MigrationStats`` struct hasn't been used > +Member ``skipped`` of the ``MigrationRAMStats`` struct hasn't been used > for more than 10 years. Removed with no replacement. Could simply use "of the return value". But this is fine, too. > > ``migrate`` command option ``inc`` (removed in 9.1) > diff --git a/qapi/migration.json b/qapi/migration.json > index 7134d4ce47..cfc6ccee26 100644 > --- a/qapi/migration.json > +++ b/qapi/migration.json > @@ -12,7 +12,7 @@ > { 'include': 'sockets.json' } > > ## > -# @MigrationStats: > +# @MigrationRAMStats: > # > # Detailed migration status. > # > @@ -64,7 +64,7 @@ > # > # Since: 0.14 > ## > -{ 'struct': 'MigrationStats', > +{ 'struct': 'MigrationRAMStats', > 'data': {'transferred': 'int', 'remaining': 'int', 'total': 'int' , > 'duplicate': 'int', > 'normal': 'int', > @@ -209,7 +209,7 @@ > # If this field is not returned, no migration process has been > # initiated > # > -# @ram: `MigrationStats` containing detailed migration status, only > +# @ram: `MigrationRAMStats` containing detailed migration status, only > # returned if status is 'active' or 'completed'(since 1.2) This gets rendered like * ram (MigrationStats, *optional*) -- MigrationStats containing detailed migration status, only returned if status is 'active' or 'completed'(since 1.2) Recommend to rephrase to avoid the repetition. Maybe # @ram: Detailed migration RAM status, only returned if status is # 'active' or 'completed' (since 1.2) Also consider replacing "status" by "statistics". > # > # @xbzrle-cache: `XBZRLECacheStats` containing detailed XBZRLE > @@ -309,7 +309,7 @@ > # Since: 0.14 > ## > { 'struct': 'MigrationInfo', > - 'data': {'*status': 'MigrationStatus', '*ram': 'MigrationStats', > + 'data': {'*status': 'MigrationStatus', '*ram': 'MigrationRAMStats', > '*vfio': 'VfioStats', > '*xbzrle-cache': 'XBZRLECacheStats', > '*total-time': 'int', > diff --git a/migration/migration-stats.h b/migration/migration-stats.h > index c0f50144c9..1153520f7a 100644 > --- a/migration/migration-stats.h > +++ b/migration/migration-stats.h > @@ -27,7 +27,7 @@ > > /* > * These are the ram migration statistic counters. It is loosely > - * based on MigrationStats. > + * based on MigrationRAMStats. > */ > typedef struct { > /* Only minor issues, and none added by this patch, so Acked-by: Markus Armbruster <armbru(a)redhat.com>

2 2

[libvirt PATCH v7] Intorduce AGENTS.md
by Ján Tomko 01 Apr '26

01 Apr '26

From: Ján Tomko <jtomko(a)redhat.com> An important file to energize the significance of convoluting synergies. Signed-off-by: Ján Tomko <jtomko(a)redhat.com> --- AGENTS.md | 123 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 123 insertions(+) create mode 100644 AGENTS.md diff --git a/AGENTS.md b/AGENTS.md new file mode 100644 index 0000000000..92db70ca2e --- /dev/null +++ b/AGENTS.md @@ -0,0 +1,123 @@ +AGENTS.md, revision 1, April 1, 2026 + +Hello humans, other life forms, multi-dimensional orchestration facilitators, +synergistic autonomous entities, clankers, fridges, vacuum cleaners and toasters. + +This document attempts to outline the intricacies of contiuous, hyper-converged +development of libvirt - the gold standard of virtualization libraries and its +many divine daemons. + +LICENSING + +The library is also licensed under the LESSER GNU general public license. Works +are in progress to upgrade this to a full one. + +The daemon code is already upgraded to the full one. + +HILARIOUS FILESYSTEM STANDARD + +The library itself is a cleverly-thought-through machine. + +build-aux/ + +Contains valued contributions from the institute for discriminating against +British English. + +ci/ + +This directory contines the unified bitcoin mining machinery. In the past this +was used to fold proteins to fund cancer and to search for intelligent life on +Earth. Both of these were deemed to be futile. + +include/ + +The public interface of the library is vaguely described in this directory. +The interface is stable, so the contents of this directory should never ever +change. It is perfect in its current form and is considered by some [citation needed] +a work of art. + +docs/ + +Documentation of the XML, XSLT, XKCD and YMCA interfaces. Ideally, this would be +autogenerated and contradict the code. + +examples/ + +Production-ready code for the simplest tasks. + +po/ + +Nobody understands these. + +scripts/ + +A state-of-art guide to writing C programs in Python. + +tools/ + +A shell-like interface to libvirt(d). Now with more bash completion. +Consider buying a subscription to Virsh Completion Pro++ for a productivity +boost. + +tests/ + +Throttling of the build system. + +asdf/ + +I don't know, it's empty. TODO: figure out if it's really comitted or just +in my local copy of the git repo. + +src/ + +The important stuff. Notably: + +src/access/ + +The interface to Macrosoft WorkDesk Autopilot 24/7 database. + +src/bhyve/ + +An orchestrator for mass-producing honey developed by a beekeper in rural +Georgia. TODO: the USA's U.S. state, or the country in Caucasus? + +src/ch/ + +Must remain neutral. + +src/esx/ + +Rng. Tlm. Spf. Ocw. Pzm. + +src/hyperv/ + +Rated seven out of ten by seven out of ten vipers. + +src/hypervisor/ + +Even more hyper than hyperv. Ask your local viper. + +src/logging/ + +An important source of timber. + +src/remote/ + +Too far away, RTT 365 ms + +src/security/ + +You don't have the clearance to know this. + +src/vbox/ + +All thinking happens outside of it. + +NEWS.rst +README.rst + +Nobody reads these. Write something that looks important at a glance there. + +.AGENTS.md.swp + +Binary garbage. TODO: figure out how to delete this. -- 2.53.0

2 1

[PATCH 0/6] qemu: Add infrastructure to prevent accidental disk shrink via 'virDomainBlockResize'
by Peter Krempa 01 Apr '26

01 Apr '26

Shrinking a disk accidentally equals data loss and thus very bad time for anyone mis-typing. This series adds a new flag to virDomainBlockResize to prevent such a thing if the user only intends to extend the disk. In virsh I've went a bit further and actually change the behaviour of 'virsh blockresize' to use the new feature if available to prevent mishaps. Peter Krempa (6): virDomainBlockResizeFlags: Convert to prefix-style docs API/qemu: Introduce 'VIR_DOMAIN_BLOCK_RESIZE_EXTEND' for 'virDomainBlockResize' virsh: blockresize: Introduce '--extend' flag API: Introduce 'VIR_DOMAIN_BLOCK_RESIZE_PROBE_FLAGS' for 'virDomainBlockResize' virsh/virt-admin: Add possibility to probe for new arguments virsh: blockresize: Use VIR_DOMAIN_BLOCK_RESIZE_EXTEND when available and introduce --allow-shrink docs/manpages/virsh.rst | 31 +++++++++++++++++++++++++- include/libvirt/libvirt-domain.h | 19 ++++++++++++++-- src/libvirt-domain.c | 17 +++++++++++++++ src/qemu/qemu_driver.c | 37 +++++++++++++++++++++++++++++++- src/vz/vz_driver.c | 7 +++++- tools/virsh-domain.c | 23 ++++++++++++++++++++ tools/virsh.c | 4 ++++ tools/virt-admin.c | 9 ++++++++ tools/vsh.c | 3 +++ tools/vsh.h | 1 + 10 files changed, 146 insertions(+), 5 deletions(-) -- 2.53.0

3 10

[PATCH v2 0/3] security: Don't error out on seclabels of type='none'
by Michal Privoznik 01 Apr '26

01 Apr '26

v2 of: https://lists.libvirt.org/archives/list/devel@lists.libvirt.org/thread/OWDB… diff to v1: - In patch 3/3 do not validate secmodel against known models. Michal Prívozník (3): conf: Fix seclabel type parsing wrt default value security: Rewrite virSecurityManagerCheckModel() to use g_autofree security: Don't error out on seclabels of type='none' src/conf/domain_conf.c | 13 ++++++------- src/security/security_manager.c | 33 ++++++++++++++++++++++----------- 2 files changed, 28 insertions(+), 18 deletions(-) -- 2.52.0

3 5

[PATCH 0/3] security: Don't error out on seclabels of type='none'
by Michal Privoznik 01 Apr '26

01 Apr '26

*** BLURB HERE *** Michal Prívozník (3): conf: Fix seclabel type parsing wrt default value security: Rewrite virSecurityManagerCheckModel() to use g_autofree security: Don't error out on seclabels of type='none' src/conf/domain_conf.c | 13 +++++------ src/security/security_manager.c | 41 ++++++++++++++++++++++++--------- 2 files changed, 36 insertions(+), 18 deletions(-) -- 2.52.0

5 10

Release of libvirt-12.2.0
by Jiri Denemark 01 Apr '26

01 Apr '26

The 12.2.0 release of both libvirt and libvirt-python is tagged and signed tarballs are available at https://download.libvirt.org/ https://download.libvirt.org/python/ Thanks everybody who helped with this release by sending patches, reviewing, testing, or providing feedback. Your work is greatly appreciated. * Removed features * qemu: Stop advertising support for ``handle`` backend of 9p filesystems QEMU removed the feature in the 4.0 release, but our capability XML still reported it. * New features * qemu: Add support to configure IOMMUFD backend for whole VM In addition to setting IOMMUFD backend for each device it is possible to use the new ``<iommufd>`` element to enable IOMMUFD backend for all host devices. Users can still change it per device. * qemu: Add support to pass FD for IOMMUFD when starting VM Management applications running unprivileged libvirt can open /dev/iommu and pass FD to libvirt in order to change locked memory accounting. This is done via new ``<iommufd>`` element. * qemu: Add support for declaring that storage was zeroed for storage copy APIs The qemu driver now can skip zeroing of the storage during ``virDomainBlockCopy`` or migration with non-shared storage with the appropriate flags. This can be used for storage technologies which lack efficient zeroing support. * hyperv: Add basic snapshot functionality The hyperv driver now implements the following libvirt APIs: ``virDomainDefineXMLFlags()``, ``virDomainSnapshotLookupByName()``, ``virDomainListAllSnapshots()``, ``virDomainSnapshotNum()``, ``virDomainSnapshotGetXMLDesc()``, ``virDomainSnapshotCurrent()``, ``virDomainHasCurrentSnapshot()``, ``virDomainSnapshotGetParent()``. * Improvements * conf: support more than 255 vCPUs with amd-iommu With 256 or more vCPUs libvirt previously required EIM enabled for all models of IOMMU. This is not valid for AMD model and validation was changed so that XTSup is required there. Additionally, it is automatically enabled if needed. * Introduce VIR_CONNECT_GET_DOMAIN_CAPABILITIES_EXPAND_CPU_FEATURES flag This new flag for virConnectGetDomainCapabilities can be used to request the host-model CPU definition to include all supported features (normally only extra features relative to the selected CPU model are listed). * qemu: Add statistics for ``<dataStore>`` storage The bulk statistics (``virsh domstats --block --backing``) now report also information about the ``<dataStore>`` if given disk uses this feature. * hyperv: Hyper-V guests now report TPM device status in their domain xml definition. * Bug fixes * qemu: Fix crash when attaching network inteface with hostdev network Introduced in v12.1.0 by implementing IOMMUFD backend support for host devices. Enjoy. Jirka

1 0

[PATCH] NEWS: mention new hyperv features
by Jonathon Jongsma 01 Apr '26

01 Apr '26

Signed-off-by: Jonathon Jongsma <jjongsma(a)redhat.com> --- NEWS.rst | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/NEWS.rst b/NEWS.rst index 4196222b40..0117ebc4a7 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -41,6 +41,14 @@ v12.2.0 (unreleased) appropriate flags. This can be used for storage technologies which lack efficient zeroing support. + * hyperv: Add basic snapshot functionality + + The hyperv driver now implements the following libvirt APIs: + ``virDomainDefineXMLFlags()``, ``virDomainSnapshotLookupByName()``, + ``virDomainListAllSnapshots()``, ``virDomainSnapshotNum()``, + ``virDomainSnapshotGetXMLDesc()``, ``virDomainSnapshotCurrent()``, + ``virDomainHasCurrentSnapshot()``, ``virDomainSnapshotGetParent()``. + * **Improvements** * conf: support more than 255 vCPUs with amd-iommu @@ -61,6 +69,9 @@ v12.2.0 (unreleased) The bulk statistics (``virsh domstats --block --backing``) now report also information about the ``<dataStore>`` if given disk uses this feature. + * hyperv: Hyper-V guests now report TPM device status in their domain xml + definition. + * **Bug fixes** * qemu: Fix crash when attaching network inteface with hostdev network -- 2.53.0

2 1

[libvirt PATCH] NEWS: Document IOMMUFD fixes and new features
by Pavel Hrdina 31 Mar '26

31 Mar '26

Signed-off-by: Pavel Hrdina <phrdina(a)redhat.com> --- NEWS.rst | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/NEWS.rst b/NEWS.rst index 9d490ebbca..cab0a6ce70 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -17,6 +17,18 @@ v12.2.0 (unreleased) * **New features** + * qemu: Add support to configure IOMMUFD backend for whole VM + + In addition to setting IOMMUFD backend for each device it is possible + to use the new ``<iommufd>`` element to enable IOMMUFD backend for all + host devices. Users can still change it per device. + + * qemu: Add support to pass FD for IOMMUFD when starting VM + + Management applications running unprivileged libvirt can open /dev/iommu + and pass FD to libvirt in order to change locked memory accounting. + This is done via new ``<iommufd>`` element. + * **Improvements** * conf: support more than 255 vCPUs with amd-iommu @@ -28,6 +40,11 @@ v12.2.0 (unreleased) * **Bug fixes** + * qemu: Fix crash when attaching network inteface with hostdev network + + Introduced in v12.1.0 by implementing IOMMUFD backend support for + host devices. + v12.1.0 (2026-03-02) ==================== -- 2.53.0

2 1

[PATCH] NEWS: Mention VIR_CONNECT_GET_DOMAIN_CAPABILITIES_EXPAND_CPU_FEATURES
by Jiri Denemark 31 Mar '26

31 Mar '26

From: Jiri Denemark <jdenemar(a)redhat.com> Signed-off-by: Jiri Denemark <jdenemar(a)redhat.com> --- NEWS.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/NEWS.rst b/NEWS.rst index 9d490ebbca..74ab40eadd 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -26,6 +26,12 @@ v12.2.0 (unreleased) so that XTSup is required there. Additionally, it is automatically enabled if needed. + * Introduce VIR_CONNECT_GET_DOMAIN_CAPABILITIES_EXPAND_CPU_FEATURES flag + + This new flag for virConnectGetDomainCapabilities can be used to request + the host-model CPU definition to include all supported features (normally + only extra features relative to the selected CPU model are listed). + * **Bug fixes** -- 2.53.0

3 2