July 2026 - Devel - libvirt List Archives

Release of libvirt-12.5.0
by Jiri Denemark 01 Jul '26

01 Jul '26

The 12.5.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. * New features * bhyve: Extend the guest agent support The bhyve driver now supports several APIs on top of the guest agent: * Getting and setting guest OS SSH keys * Setting guest OS user's password * Getting and setting guest OS time Additionally, domain rebooting and shutting down using the agent is now supported. * bhyve: Support ``on_reboot`` and ``on_poweroff`` actions The bhyve driver now respects the domain's ``on_reboot`` and ``on_poweroff`` actions. * bhyve: Support populating SMBIOS fields Add support for populating the SMBIOS fields as defined by the ``<sysinfo type='smbios'>`` section of the domain's XML. * qemu: Add support for standalone VNC server Starting with this release, libvirt might spawn a standalone qemu-vnc process instead of QEMU's built-in VNC server, for enhanced security. * Improvements * Enable hyperv driver on RHEL The spec file now enables the Hyper-V driver when building on Red Hat Enterprise Linux. * remote: allow passing argv to the ext transport The ext transport not only allows spawning a process (via the ``command`` attribute), but as of this release also specifying additional arguments to it, via ``argv`` attribute. * Introduce ``VIR_CONNECT_GET_DOMAIN_CAPABILITIES_SUPPORTED_CPU_FEATURES`` flag Some CPU features may be enabled explicitly, but should not automatically become part of a host-model CPU and thus are not normally visible in domain capabilities. Users can now request such features to be shown in the host-model CPU in domain capabilities using the new flag. It is exposed as ``--supported-cpu-features`` option for ``virsh domcapabilities``. * Bug fixes * Ensure proper shutdown ordering of ``virtlogd`` and ``virtlockd`` The logging and locking helper daemons now shutdown after the daemon running the ``qemu`` hypervisor driver since their services may be needed to shutdown the VMs run by the qemu driver. * qemu: Record selected ``virtio`` video device model into the XML The ``qemu`` driver may depending on platform and installed QEMU modules pick one of two distinct virtio video device types for the primary device. The choice was not recorded in the XML and since the devices are incompatible it can cause failures on migration when the destination picks the wrong device. This version thus records the picked device both for running VMs on upgrade and for new devices to prevent this problem in the future. * bhyve: Guest agent related fixes A few bugs related to the guest agent communication are fixed, from not properly initializing an agent to crashing when the agent socket cannot be opened. * Fix domain capabilities on AMD CPUs QEMU 10.1 and newer does not automatically enable features from arch-capabilities MSR on AMD CPUs as they are specific for Intel CPUs and KVM is just emulating them on AMD. But advertising them on AMD CPUs can cause Windows guest OS to crash so they are hidden by default now. But the features are still supported and can be enabled explicitly, for example, when migrating existing domains. Libvirt now detects this scenario and properly shows the affected features as enabled in domain capabilities when requested by ``VIR_CONNECT_GET_DOMAIN_CAPABILITIES_SUPPORTED_CPU_FEATURES`` flag. * vmx: Properly show all 64 disks on a SCSI controller Due to an off-by-one error a last, 64th disk was not shown in a domain XML, which is now fixed. Enjoy. Jirka

1 0

[PATCH] NEWS: Document a fix for 64 disks on a SCSI controller with vmx
by Martin Kletzander 01 Jul '26

01 Jul '26

From: Martin Kletzander <mkletzan(a)redhat.com> Signed-off-by: Martin Kletzander <mkletzan(a)redhat.com> --- NEWS.rst | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/NEWS.rst b/NEWS.rst index f78a9d3057b1..e379dc78b6ac 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -82,6 +82,11 @@ v12.5.0 (unreleased) not properly initializing an agent to crashing when the agent socket cannot be opened. + * vmx: Properly show all 64 disks on a SCSI controller + + Due to an off-by-one error a last, 64th disk was not shown in a domain XML, + which is now fixed. + v12.4.0 (2026-06-01) ==================== -- 2.55.0

2 1

[PATCH] NEWS: Document improvements related to AMD CPU capabilities
by Jiri Denemark 01 Jul '26

01 Jul '26

From: Jiri Denemark <jdenemar(a)redhat.com> Signed-off-by: Jiri Denemark <jdenemar(a)redhat.com> --- NEWS.rst | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/NEWS.rst b/NEWS.rst index 07f539f996..53c2c205a3 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -54,6 +54,14 @@ v12.5.0 (2026-07-01) specifying additional arguments to it, via ``argv`` attribute. + * Introduce VIR_CONNECT_GET_DOMAIN_CAPABILITIES_SUPPORTED_CPU_FEATURES flag + + Some CPU features may be enabled explicitly, but should not automatically + become part of a host-model CPU and thus are not normally visible in domain + capabilities. Users can now request such features to be shown in the + host-model CPU in domain capabilities using the new flag. It is exposed as + ``--supported-cpu-features`` option for ``virsh domcapabilities``. + * **Bug fixes** * Ensure proper shutdown ordering of ``virtlogd`` and ``virtlockd`` @@ -78,6 +86,18 @@ v12.5.0 (2026-07-01) not properly initializing an agent to crashing when the agent socket cannot be opened. + * Fix domain capabilities on AMD CPUs + + QEMU 10.1 and newer does not automatically enable features from + arch-capabilities MSR on AMD CPUs as they are specific for Intel CPUs and + KVM is just emulating them on AMD. But advertising them on AMD CPUs can + cause Windows guest OS to crash so they are hidden by default now. But the + features are still supported and can be enabled explicitly, for example, + when migrating existing domains. Libvirt now detects this scenario and + properly shows the affected features as enabled in domain capabilities when + requested by VIR_CONNECT_GET_DOMAIN_CAPABILITIES_SUPPORTED_CPU_FEATURES + flag. + v12.4.0 (2026-06-01) ==================== -- 2.54.0

2 1

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

01 Jul '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

7 29

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

01 Jul '26

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

1 2