- Devel - libvirt List Archives

[PATCH 0/4] qemu: add API to ammounce guest interfaces to the network
by Laine Stump 05 Jun '26

05 Jun '26

This provides a supported method of executing QEMU's "self-announce" command, which injects gratuitous ARP packets into the outgoing data stream of guest interfaces. Resolves: https://redhat.atlassian.net/browse/RHEL-7047 Laine Stump (4): qemu: new monitor function qemuMonitorAnnounceSelf() API: Introduce virDomainAnnounceInterface qemu: implement virDomainAnnounceInterface() API virsh: new command "domifannounce" docs/manpages/virsh.rst | 41 +++++++++++++++ include/libvirt/libvirt-domain.h | 46 +++++++++++++++++ src/driver-hypervisor.h | 8 +++ src/libvirt-domain.c | 65 +++++++++++++++++++++++ src/libvirt_public.syms | 5 ++ src/qemu/qemu_driver.c | 81 ++++++++++++++++++++++++++++- src/qemu/qemu_monitor.c | 13 +++++ src/qemu/qemu_monitor.h | 8 +++ src/qemu/qemu_monitor_json.c | 55 ++++++++++++++++++++ src/qemu/qemu_monitor_json.h | 8 +++ src/remote/remote_driver.c | 1 + src/remote/remote_protocol.x | 19 ++++++- src/remote_protocol-structs | 10 ++++ tools/virsh-domain.c | 88 ++++++++++++++++++++++++++++++++ 14 files changed, 446 insertions(+), 2 deletions(-) -- 2.54.0

3 14

[PATCH RFC 0/6] Add qemu-vnc support
by marcandre.lureau＠redhat.com 04 Jun '26

04 Jun '26

From: Marc-André Lureau <marcandre.lureau(a)redhat.com> Hi, This series allows to run the QEMU VNC server in a standalone process. The qemu-vnc binary is aimed to be released with QEMU 11.1. It is still being reviewed (https://patchew.org/QEMU/20260410-qemu-vnc-v2-0-231416f76dc3@redhat.com/) The standalone VNC activates automatically when a domain has both <graphics type='dbus'/> (bus mode) and <graphics type='vnc'/>, and the qemu-vnc binary is available. Comments welcome! Marc-André Lureau (6): qemu: add standalone VNC state directory qemu: add qemu-vnc configuration qemu: add qemu-vnc helper unit qemu: integrate standalone VNC in domain lifecycle qemu: wire up standalone VNC in driver APIs qemu: add tests for standalone VNC graphics po/POTFILES | 1 + src/qemu/libvirtd_qemu.aug | 1 + src/qemu/meson.build | 1 + src/qemu/qemu.conf.in | 8 + src/qemu/qemu_command.c | 2 + src/qemu/qemu_conf.c | 8 + src/qemu/qemu_conf.h | 2 + src/qemu/qemu_domain.c | 1 + src/qemu/qemu_domain.h | 2 + src/qemu/qemu_driver.c | 68 ++- src/qemu/qemu_extdevice.c | 13 +- src/qemu/qemu_hotplug.c | 12 + src/qemu/qemu_process.c | 40 +- src/qemu/qemu_vnc.c | 407 ++++++++++++++++++ src/qemu/qemu_vnc.h | 41 ++ src/qemu/test_libvirtd_qemu.aug.in | 1 + ...hics-vnc-standalone-p2p.x86_64-latest.args | 34 ++ ...phics-vnc-standalone-p2p.x86_64-latest.xml | 40 ++ .../graphics-vnc-standalone-p2p.xml | 39 ++ ...s-vnc-standalone-socket.x86_64-latest.args | 33 ++ ...cs-vnc-standalone-socket.x86_64-latest.xml | 40 ++ .../graphics-vnc-standalone-socket.xml | 40 ++ ...graphics-vnc-standalone.x86_64-latest.args | 33 ++ .../graphics-vnc-standalone.x86_64-latest.xml | 40 ++ .../graphics-vnc-standalone.xml | 40 ++ tests/qemuxmlconftest.c | 4 + tests/testutilsqemu.c | 9 + 27 files changed, 950 insertions(+), 10 deletions(-) create mode 100644 src/qemu/qemu_vnc.c create mode 100644 src/qemu/qemu_vnc.h create mode 100644 tests/qemuxmlconfdata/graphics-vnc-standalone-p2p.x86_64-latest.args create mode 100644 tests/qemuxmlconfdata/graphics-vnc-standalone-p2p.x86_64-latest.xml create mode 100644 tests/qemuxmlconfdata/graphics-vnc-standalone-p2p.xml create mode 100644 tests/qemuxmlconfdata/graphics-vnc-standalone-socket.x86_64-latest.args create mode 100644 tests/qemuxmlconfdata/graphics-vnc-standalone-socket.x86_64-latest.xml create mode 100644 tests/qemuxmlconfdata/graphics-vnc-standalone-socket.xml create mode 100644 tests/qemuxmlconfdata/graphics-vnc-standalone.x86_64-latest.args create mode 100644 tests/qemuxmlconfdata/graphics-vnc-standalone.x86_64-latest.xml create mode 100644 tests/qemuxmlconfdata/graphics-vnc-standalone.xml -- 2.53.0

3 10

[PATCH 0/3] tests: Add capability dump data for the qemu-11.1 dev cycle
by Peter Krempa 03 Jun '26

03 Jun '26

Peter Krempa (3): qemublocktest: Skip schema validation on 'gluster' backend tests qemucapabilitiestest: Add data for the qemu-11.1 dev cycle (x86_64) qemucapabilitiestest: Add data for the qemu-11.1 dev cycle (aarch64) .../qemu_11.1.0-q35.x86_64-expanded.xml | 1856 + .../qemu_11.1.0-q35.x86_64-supported.xml | 1738 + .../domaincapsdata/qemu_11.1.0-q35.x86_64.xml | 1731 + .../domaincapsdata/qemu_11.1.0-tcg.x86_64.xml | 2856 + .../qemu_11.1.0-virt.aarch64.xml | 265 + tests/domaincapsdata/qemu_11.1.0.aarch64.xml | 265 + tests/domaincapsdata/qemu_11.1.0.x86_64.xml | 1729 + tests/qemublocktest.c | 31 +- .../caps_11.1.0_aarch64.replies | 39323 ++++++++++++ .../caps_11.1.0_aarch64.xml | 536 + .../caps_11.1.0_x86_64.replies | 49275 ++++++++++++++++ .../caps_11.1.0_x86_64.xml | 5767 ++ ...host-model-fallback-kvm.x86_64-11.0.0.args | 2 +- ...-host-model-fallback-kvm.x86_64-11.0.0.xml | 2 +- ...host-model-fallback-tcg.x86_64-11.0.0.args | 2 +- ...-host-model-fallback-tcg.x86_64-11.0.0.xml | 2 +- .../cpu-host-model-kvm.x86_64-11.0.0.args | 2 +- .../cpu-host-model-kvm.x86_64-11.0.0.xml | 2 +- ...st-model-nofallback-kvm.x86_64-11.0.0.args | 2 +- ...ost-model-nofallback-kvm.x86_64-11.0.0.xml | 2 +- ...st-model-nofallback-tcg.x86_64-11.0.0.args | 2 +- ...ost-model-nofallback-tcg.x86_64-11.0.0.xml | 2 +- .../cpu-host-model-tcg.x86_64-11.0.0.args | 2 +- .../cpu-host-model-tcg.x86_64-11.0.0.xml | 2 +- 24 files changed, 105373 insertions(+), 23 deletions(-) create mode 100644 tests/domaincapsdata/qemu_11.1.0-q35.x86_64-expanded.xml create mode 100644 tests/domaincapsdata/qemu_11.1.0-q35.x86_64-supported.xml create mode 100644 tests/domaincapsdata/qemu_11.1.0-q35.x86_64.xml create mode 100644 tests/domaincapsdata/qemu_11.1.0-tcg.x86_64.xml create mode 100644 tests/domaincapsdata/qemu_11.1.0-virt.aarch64.xml create mode 100644 tests/domaincapsdata/qemu_11.1.0.aarch64.xml create mode 100644 tests/domaincapsdata/qemu_11.1.0.x86_64.xml create mode 100644 tests/qemucapabilitiesdata/caps_11.1.0_aarch64.replies create mode 100644 tests/qemucapabilitiesdata/caps_11.1.0_aarch64.xml create mode 100644 tests/qemucapabilitiesdata/caps_11.1.0_x86_64.replies create mode 100644 tests/qemucapabilitiesdata/caps_11.1.0_x86_64.xml -- 2.54.0

2 8

[PATCH 0/3] hyperv: Add support for detecting nested virtualization capability
by Jonathon Jongsma 03 Jun '26

03 Jun '26

In order to support migrating hyperv vms to kubevirt, MTV needs to detect whether the vm has a nested virtualization capabilities. This series adds basic support for identifying this scenario by exposing cpu features on the libvirt domain xml. https://redhat.atlassian.net/browse/RHEL-147662 Jonathon Jongsma (3): hyperv: fix error handling of hypervGetProcessorsByName() hyperv: Rename hypervGetProcessorsByName() to hypervGetProcessorList() hyperv: report nested virtualization setting in domain XML src/hyperv/hyperv_driver.c | 48 +++++++++++++++++++++------ src/hyperv/hyperv_wmi_generator.input | 5 +++ 2 files changed, 43 insertions(+), 10 deletions(-) -- 2.54.0

2 4

[PATCH 0/3] ci: Remove cirrus jobs
by Peter Krempa 02 Jun '26

02 Jun '26

Cirrus CI ceased operation. Our jobs now fail: https://gitlab.com/libvirt/libvirt/-/jobs/14644398990 Peter Krempa (3): ci: README: Delete section about 'Cirrus CI' ci: Drop 'Cirrus CI' job defnitions ci: Regenerate with 'lcitool' ci/README.rst | 59 ----------------------------------- ci/cirrus/freebsd-14.vars | 16 ---------- ci/cirrus/freebsd-15.vars | 16 ---------- ci/cirrus/macos-14.vars | 16 ---------- ci/gitlab/build-templates.yml | 53 ------------------------------- ci/gitlab/builds.yml | 49 ----------------------------- ci/manifest.yml | 11 ------- 7 files changed, 220 deletions(-) delete mode 100644 ci/cirrus/freebsd-14.vars delete mode 100644 ci/cirrus/freebsd-15.vars delete mode 100644 ci/cirrus/macos-14.vars -- 2.54.0

2 9

[PATCH v2 00/16] qemu: Fix CPU feature reporting on AMD CPUs
by Jiri Denemark 02 Jun '26

02 Jun '26

See the last patch for detailed description and individual patches for specific changes in v2. Important changes in version 2: - tests - the functionality uses a new flag for virConnectGetDomainCapabilities Jiri Denemark (16): cpu_conf: Introduce virCPUDefSortFeatures qemu_capabilities: Split virQEMUCapsFillDomainCPUCaps qemu: Move domain caps flags handling to virQEMUCapsFillDomainCPUHostModel qemu_capabilities: Always sort features in host-model CPU qemu_capabilities: Use g_autoptr in virQEMUCapsInitHostCPUModel qemu_capabilities: Split conditions in virQEMUCapsInitHostCPUModel qemu_capabilities: Cache expanded CPU domaincapstest: Test EXPAND_CPU_FEATURES flag util: Publish and mock virHostCPUGetMSRFromKVM cpu_x86: Introduce virCPUx86DataAddMSR cpu: Introduce virCPUUpdateFeatures Fix documentation of VIR_CONNECT_GET_DOMAIN_CAPABILITIES_EXPAND_CPU_FEATURES Introduce VIR_CONNECT_GET_DOMAIN_CAPABILITIES_SUPPORTED_CPU_FEATURES flag virsh: Add --supported-cpu-features option for domcapabilities domaincapstest: Test SUPPORTED_CPU_FEATURES flag qemu_capabilities: Fix domain capabilities on AMD CPUs docs/manpages/virsh.rst | 12 +- include/libvirt/libvirt-domain.h | 3 + src/conf/cpu_conf.c | 20 + src/conf/cpu_conf.h | 3 + src/cpu/cpu.c | 48 +- src/cpu/cpu.h | 12 + src/cpu/cpu_x86.c | 54 +- src/cpu/cpu_x86.h | 4 + src/libvirt-domain.c | 14 +- src/libvirt_private.syms | 4 + src/qemu/qemu_capabilities.c | 214 +- src/qemu/qemu_capabilities.h | 6 +- src/qemu/qemu_conf.c | 6 +- src/qemu/qemu_conf.h | 3 +- src/qemu/qemu_driver.c | 18 +- src/util/virhostcpu.c | 16 +- src/util/virhostcpu.h | 3 + ...qemu_10.0.0-q35.x86_64+amdsev-expanded.xml | 1123 ++++++++ ...emu_10.0.0-q35.x86_64+amdsev-supported.xml | 1015 +++++++ .../qemu_10.0.0-q35.x86_64+amdsev.xml | 48 +- .../qemu_10.0.0-q35.x86_64-expanded.xml | 1979 ++++++++++++++ .../qemu_10.0.0-q35.x86_64-supported.xml | 1903 ++++++++++++++ .../domaincapsdata/qemu_10.0.0-q35.x86_64.xml | 50 +- .../qemu_10.0.0-tcg.x86_64+amdsev.xml | 60 +- .../domaincapsdata/qemu_10.0.0-tcg.x86_64.xml | 60 +- tests/domaincapsdata/qemu_10.0.0.s390x.xml | 94 +- .../qemu_10.0.0.x86_64+amdsev.xml | 48 +- tests/domaincapsdata/qemu_10.0.0.x86_64.xml | 50 +- ...mu_10.1.0-q35.x86_64+inteltdx-expanded.xml | 1250 +++++++++ ...u_10.1.0-q35.x86_64+inteltdx-supported.xml | 1064 ++++++++ .../qemu_10.1.0-q35.x86_64+inteltdx.xml | 56 +- .../qemu_10.1.0-q35.x86_64-expanded.xml | 2328 +++++++++++++++++ .../qemu_10.1.0-q35.x86_64-supported.xml | 2259 ++++++++++++++++ .../domaincapsdata/qemu_10.1.0-q35.x86_64.xml | 40 +- .../qemu_10.1.0-tcg.x86_64+inteltdx.xml | 66 +- .../domaincapsdata/qemu_10.1.0-tcg.x86_64.xml | 66 +- tests/domaincapsdata/qemu_10.1.0.s390x.xml | 106 +- .../qemu_10.1.0.x86_64+inteltdx.xml | 56 +- tests/domaincapsdata/qemu_10.1.0.x86_64.xml | 40 +- .../qemu_10.2.0-q35.x86_64+mshv-expanded.xml | 237 ++ .../qemu_10.2.0-q35.x86_64+mshv-supported.xml | 237 ++ .../qemu_10.2.0-q35.x86_64-expanded.xml | 1483 +++++++++++ .../qemu_10.2.0-q35.x86_64-supported.xml | 1365 ++++++++++ .../domaincapsdata/qemu_10.2.0-q35.x86_64.xml | 24 +- .../qemu_10.2.0-tcg.x86_64+mshv.xml | 66 +- .../domaincapsdata/qemu_10.2.0-tcg.x86_64.xml | 66 +- tests/domaincapsdata/qemu_10.2.0.x86_64.xml | 24 +- .../qemu_11.0.0-q35.x86_64+sgx-expanded.xml | 1865 +++++++++++++ .../qemu_11.0.0-q35.x86_64+sgx-supported.xml | 1747 +++++++++++++ .../qemu_11.0.0-q35.x86_64+sgx.xml | 24 +- .../qemu_11.0.0-q35.x86_64-expanded.xml | 1856 +++++++++++++ .../qemu_11.0.0-q35.x86_64-supported.xml | 1738 ++++++++++++ .../domaincapsdata/qemu_11.0.0-q35.x86_64.xml | 24 +- .../qemu_11.0.0-tcg.x86_64+sgx.xml | 66 +- .../domaincapsdata/qemu_11.0.0-tcg.x86_64.xml | 66 +- tests/domaincapsdata/qemu_11.0.0.s390x.xml | 106 +- .../domaincapsdata/qemu_11.0.0.x86_64+sgx.xml | 24 +- tests/domaincapsdata/qemu_11.0.0.x86_64.xml | 24 +- .../qemu_7.2.0-hvf.x86_64+hvf.xml | 36 +- .../qemu_7.2.0-q35.x86_64-expanded.xml | 1257 +++++++++ .../qemu_7.2.0-q35.x86_64-supported.xml | 1181 +++++++++ .../domaincapsdata/qemu_7.2.0-q35.x86_64.xml | 36 +- .../qemu_7.2.0-tcg.x86_64+hvf.xml | 46 +- .../domaincapsdata/qemu_7.2.0-tcg.x86_64.xml | 46 +- tests/domaincapsdata/qemu_7.2.0.x86_64.xml | 36 +- .../qemu_8.0.0-q35.x86_64-expanded.xml | 1366 ++++++++++ .../qemu_8.0.0-q35.x86_64-supported.xml | 1290 +++++++++ .../domaincapsdata/qemu_8.0.0-q35.x86_64.xml | 36 +- .../domaincapsdata/qemu_8.0.0-tcg.x86_64.xml | 54 +- tests/domaincapsdata/qemu_8.0.0.x86_64.xml | 36 +- .../qemu_8.1.0-q35.x86_64-expanded.xml | 1624 ++++++++++++ .../qemu_8.1.0-q35.x86_64-supported.xml | 1548 +++++++++++ .../domaincapsdata/qemu_8.1.0-q35.x86_64.xml | 38 +- .../domaincapsdata/qemu_8.1.0-tcg.x86_64.xml | 60 +- tests/domaincapsdata/qemu_8.1.0.s390x.xml | 62 +- tests/domaincapsdata/qemu_8.1.0.x86_64.xml | 38 +- .../qemu_8.2.0-q35.x86_64-expanded.xml | 1626 ++++++++++++ .../qemu_8.2.0-q35.x86_64-supported.xml | 1550 +++++++++++ .../domaincapsdata/qemu_8.2.0-q35.x86_64.xml | 40 +- .../domaincapsdata/qemu_8.2.0-tcg.x86_64.xml | 58 +- tests/domaincapsdata/qemu_8.2.0.s390x.xml | 62 +- tests/domaincapsdata/qemu_8.2.0.x86_64.xml | 40 +- .../qemu_9.0.0-q35.x86_64-expanded.xml | 1627 ++++++++++++ .../qemu_9.0.0-q35.x86_64-supported.xml | 1551 +++++++++++ .../domaincapsdata/qemu_9.0.0-q35.x86_64.xml | 40 +- .../domaincapsdata/qemu_9.0.0-tcg.x86_64.xml | 62 +- tests/domaincapsdata/qemu_9.0.0.x86_64.xml | 40 +- .../qemu_9.1.0-q35.x86_64-expanded.xml | 1763 +++++++++++++ .../qemu_9.1.0-q35.x86_64-supported.xml | 1687 ++++++++++++ .../domaincapsdata/qemu_9.1.0-q35.x86_64.xml | 48 +- .../domaincapsdata/qemu_9.1.0-tcg.x86_64.xml | 60 +- tests/domaincapsdata/qemu_9.1.0.s390x.xml | 94 +- tests/domaincapsdata/qemu_9.1.0.x86_64.xml | 48 +- .../qemu_9.2.0-q35.x86_64+amdsev-expanded.xml | 1003 +++++++ ...qemu_9.2.0-q35.x86_64+amdsev-supported.xml | 895 +++++++ .../qemu_9.2.0-q35.x86_64+amdsev.xml | 48 +- .../qemu_9.2.0-q35.x86_64-expanded.xml | 1821 +++++++++++++ .../qemu_9.2.0-q35.x86_64-supported.xml | 1745 ++++++++++++ .../domaincapsdata/qemu_9.2.0-q35.x86_64.xml | 50 +- .../qemu_9.2.0-tcg.x86_64+amdsev.xml | 60 +- .../domaincapsdata/qemu_9.2.0-tcg.x86_64.xml | 60 +- tests/domaincapsdata/qemu_9.2.0.s390x.xml | 94 +- .../qemu_9.2.0.x86_64+amdsev.xml | 48 +- tests/domaincapsdata/qemu_9.2.0.x86_64.xml | 50 +- tests/domaincapstest.c | 56 +- tests/qemucpumock.c | 22 + tools/virsh-host.c | 7 + 107 files changed, 48819 insertions(+), 1569 deletions(-) create mode 100644 tests/domaincapsdata/qemu_10.0.0-q35.x86_64+amdsev-expanded.xml create mode 100644 tests/domaincapsdata/qemu_10.0.0-q35.x86_64+amdsev-supported.xml create mode 100644 tests/domaincapsdata/qemu_10.0.0-q35.x86_64-expanded.xml create mode 100644 tests/domaincapsdata/qemu_10.0.0-q35.x86_64-supported.xml create mode 100644 tests/domaincapsdata/qemu_10.1.0-q35.x86_64+inteltdx-expanded.xml create mode 100644 tests/domaincapsdata/qemu_10.1.0-q35.x86_64+inteltdx-supported.xml create mode 100644 tests/domaincapsdata/qemu_10.1.0-q35.x86_64-expanded.xml create mode 100644 tests/domaincapsdata/qemu_10.1.0-q35.x86_64-supported.xml create mode 100644 tests/domaincapsdata/qemu_10.2.0-q35.x86_64+mshv-expanded.xml create mode 100644 tests/domaincapsdata/qemu_10.2.0-q35.x86_64+mshv-supported.xml create mode 100644 tests/domaincapsdata/qemu_10.2.0-q35.x86_64-expanded.xml create mode 100644 tests/domaincapsdata/qemu_10.2.0-q35.x86_64-supported.xml create mode 100644 tests/domaincapsdata/qemu_11.0.0-q35.x86_64+sgx-expanded.xml create mode 100644 tests/domaincapsdata/qemu_11.0.0-q35.x86_64+sgx-supported.xml create mode 100644 tests/domaincapsdata/qemu_11.0.0-q35.x86_64-expanded.xml create mode 100644 tests/domaincapsdata/qemu_11.0.0-q35.x86_64-supported.xml create mode 100644 tests/domaincapsdata/qemu_7.2.0-q35.x86_64-expanded.xml create mode 100644 tests/domaincapsdata/qemu_7.2.0-q35.x86_64-supported.xml create mode 100644 tests/domaincapsdata/qemu_8.0.0-q35.x86_64-expanded.xml create mode 100644 tests/domaincapsdata/qemu_8.0.0-q35.x86_64-supported.xml create mode 100644 tests/domaincapsdata/qemu_8.1.0-q35.x86_64-expanded.xml create mode 100644 tests/domaincapsdata/qemu_8.1.0-q35.x86_64-supported.xml create mode 100644 tests/domaincapsdata/qemu_8.2.0-q35.x86_64-expanded.xml create mode 100644 tests/domaincapsdata/qemu_8.2.0-q35.x86_64-supported.xml create mode 100644 tests/domaincapsdata/qemu_9.0.0-q35.x86_64-expanded.xml create mode 100644 tests/domaincapsdata/qemu_9.0.0-q35.x86_64-supported.xml create mode 100644 tests/domaincapsdata/qemu_9.1.0-q35.x86_64-expanded.xml create mode 100644 tests/domaincapsdata/qemu_9.1.0-q35.x86_64-supported.xml create mode 100644 tests/domaincapsdata/qemu_9.2.0-q35.x86_64+amdsev-expanded.xml create mode 100644 tests/domaincapsdata/qemu_9.2.0-q35.x86_64+amdsev-supported.xml create mode 100644 tests/domaincapsdata/qemu_9.2.0-q35.x86_64-expanded.xml create mode 100644 tests/domaincapsdata/qemu_9.2.0-q35.x86_64-supported.xml -- 2.54.0

2 32

[PATCH 0/2] ci: Bump to Debian 13 and drop Cirrus
by Michal Privoznik 02 Jun '26

02 Jun '26

Green(-ish) pipeline: https://gitlab.com/MichalPrivoznik/libvirt/-/pipelines/2569490163 Failed jobs are unrelated to this change. Michal Prívozník (2): ci: regenerate with 'lcitool manifest' ci: Drop cirrus ci/README.rst | 58 ------ ci/buildenv/debian-12-cross-mips64el.sh | 109 ----------- ci/buildenv/debian-12-cross-mipsel.sh | 109 ----------- ...-aarch64.sh => debian-13-cross-aarch64.sh} | 0 ...ss-armv6l.sh => debian-13-cross-armv6l.sh} | 2 - ...ss-armv7l.sh => debian-13-cross-armv7l.sh} | 3 - ...-cross-i686.sh => debian-13-cross-i686.sh} | 2 - ...-ppc64le.sh => debian-13-cross-ppc64le.sh} | 0 ci/buildenv/debian-13-cross-riscv64.sh | 109 +++++++++++ ...ross-s390x.sh => debian-13-cross-s390x.sh} | 0 ci/buildenv/{debian-12.sh => debian-13.sh} | 0 ci/buildenv/debian-sid-cross-mips64el.sh | 109 ----------- ci/buildenv/debian-sid-cross-riscv64.sh | 109 +++++++++++ ci/cirrus/build.yml | 30 --- ci/cirrus/freebsd-14.vars | 16 -- ci/cirrus/freebsd-15.vars | 16 -- ci/cirrus/macos-14.vars | 16 -- .../debian-12-cross-mips64el.Dockerfile | 115 ----------- .../debian-12-cross-mipsel.Dockerfile | 115 ----------- ...ile => debian-13-cross-aarch64.Dockerfile} | 2 +- ...file => debian-13-cross-armv6l.Dockerfile} | 4 +- ...file => debian-13-cross-armv7l.Dockerfile} | 5 +- ...erfile => debian-13-cross-i686.Dockerfile} | 4 +- ...ile => debian-13-cross-ppc64le.Dockerfile} | 2 +- .../debian-13-cross-riscv64.Dockerfile | 115 +++++++++++ ...rfile => debian-13-cross-s390x.Dockerfile} | 2 +- ...ian-12.Dockerfile => debian-13.Dockerfile} | 2 +- .../debian-sid-cross-mips64el.Dockerfile | 115 ----------- .../debian-sid-cross-riscv64.Dockerfile | 115 +++++++++++ ci/gitlab/build-templates.yml | 53 ------ ci/gitlab/builds.yml | 178 ++++++------------ ci/gitlab/containers.yml | 56 +++--- ci/manifest.yml | 32 +--- 33 files changed, 547 insertions(+), 1056 deletions(-) delete mode 100644 ci/buildenv/debian-12-cross-mips64el.sh delete mode 100644 ci/buildenv/debian-12-cross-mipsel.sh rename ci/buildenv/{debian-12-cross-aarch64.sh => debian-13-cross-aarch64.sh} (100%) rename ci/buildenv/{debian-12-cross-armv6l.sh => debian-13-cross-armv6l.sh} (98%) rename ci/buildenv/{debian-12-cross-armv7l.sh => debian-13-cross-armv7l.sh} (97%) rename ci/buildenv/{debian-12-cross-i686.sh => debian-13-cross-i686.sh} (98%) rename ci/buildenv/{debian-12-cross-ppc64le.sh => debian-13-cross-ppc64le.sh} (100%) create mode 100644 ci/buildenv/debian-13-cross-riscv64.sh rename ci/buildenv/{debian-12-cross-s390x.sh => debian-13-cross-s390x.sh} (100%) rename ci/buildenv/{debian-12.sh => debian-13.sh} (100%) delete mode 100644 ci/buildenv/debian-sid-cross-mips64el.sh create mode 100644 ci/buildenv/debian-sid-cross-riscv64.sh delete mode 100644 ci/cirrus/build.yml delete mode 100644 ci/cirrus/freebsd-14.vars delete mode 100644 ci/cirrus/freebsd-15.vars delete mode 100644 ci/cirrus/macos-14.vars delete mode 100644 ci/containers/debian-12-cross-mips64el.Dockerfile delete mode 100644 ci/containers/debian-12-cross-mipsel.Dockerfile rename ci/containers/{debian-12-cross-aarch64.Dockerfile => debian-13-cross-aarch64.Dockerfile} (99%) rename ci/containers/{debian-12-cross-armv6l.Dockerfile => debian-13-cross-armv6l.Dockerfile} (97%) rename ci/containers/{debian-12-cross-armv7l.Dockerfile => debian-13-cross-armv7l.Dockerfile} (96%) rename ci/containers/{debian-12-cross-i686.Dockerfile => debian-13-cross-i686.Dockerfile} (97%) rename ci/containers/{debian-12-cross-ppc64le.Dockerfile => debian-13-cross-ppc64le.Dockerfile} (99%) create mode 100644 ci/containers/debian-13-cross-riscv64.Dockerfile rename ci/containers/{debian-12-cross-s390x.Dockerfile => debian-13-cross-s390x.Dockerfile} (99%) rename ci/containers/{debian-12.Dockerfile => debian-13.Dockerfile} (98%) delete mode 100644 ci/containers/debian-sid-cross-mips64el.Dockerfile create mode 100644 ci/containers/debian-sid-cross-riscv64.Dockerfile -- 2.53.0

3 4

[PATCHv2] lxc: truncate LOOP_GET_STATUS64.lo_file_name for long loop backing paths
by Radoslaw Smigielski 01 Jun '26

01 Jun '26

From: Radoslaw Smigielski <rsmigiel(a)redhat.com> LXC domains using a file-backed filesystem with the loop driver fail to start when the backing image path is longer than LO_NAME_SIZE (64 bytes, 63 characters plus NUL). virFileLoopDeviceAssociate() treated a failed virStrcpy() into loop_info64.lo_file_name as fatal and reported a misleading virReportSystemError(errno, ...), so users saw errors such as "Unable to set backing file ...: Success" or ENOENT even when the file existed. The kernel only stores a short name in lo_file_name for LOOP_SET_STATUS64 metadata. The backing file is opened by full path. Copy the path with virStrcpy(), allow truncation into lo_file_name, and mark truncation with '*' at LO_NAME_SIZE - 2 to match losetup behavior. Log truncation at debug level only. XML example that failed before this change: <filesystem type='file' accessmode='passthrough'> <driver type='loop' format='raw'/> <source file='/root/demoaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa.raw'/> <target dir='/'/> </filesystem> Fixes: https://gitlab.com/libvirt/libvirt/-/work_items/63 Signed-off-by: Radoslaw Smigielski <rsmigiel(a)redhat.com> --- src/util/virfile.c | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/src/util/virfile.c b/src/util/virfile.c index a0c6cb804862..443d0ed9adab 100644 --- a/src/util/virfile.c +++ b/src/util/virfile.c @@ -995,11 +995,15 @@ int virFileLoopDeviceAssociate(const char *file, lo.lo_flags = LO_FLAGS_AUTOCLEAR; - /* Set backing file name for LOOP_GET_STATUS64 queries */ + /* lo_file_name is loop device name, max length is LO_NAME_SIZE bytes. + * Truncate loop device name if file path is longer than LO_NAME_SIZE, + * and still use the full path to open backing file. */ if (virStrcpy((char *) lo.lo_file_name, file, LO_NAME_SIZE) < 0) { - virReportSystemError(errno, - _("Unable to set backing file %1$s"), file); - goto cleanup; + /* virStrcpy() only returns -1 on truncation. Mark truncation with + * asterisk at position LO_NAME_SIZE-2 to match losetup behavior. */ + lo.lo_file_name[LO_NAME_SIZE - 2] = '*'; + VIR_DEBUG("lo_file_name for '%s' truncated to %d bytes in loop metadata", + file, LO_NAME_SIZE); } if ((fsfd = open(file, O_RDWR)) < 0) { -- 2.54.0

1 0

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

01 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

3 13

Release of libvirt-12.4.0
by Jiri Denemark 01 Jun '26

01 Jun '26

The 12.4.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: Bump minimum version to QEMU-7.2 The minimal required version of QEMU was bumped to 7.2.0. * New features * resctrl: Add energy monitoring via resctrl's PERF_PKG_MON Add support for Linux kernel 7.0 feature - energy monitoring via resctrl. This allows to monitor per-VM energy consumption on supported platforms. Implemented via ``energytune`` element in ``cputune`` . * Add channel lifecycle domain event Add support for a new domain event which can be used to track the state of any virtio channel. It is similar to guest agent lifecycle event. * bhyve: Add memory tuning support The bhyve driver now allows setting a domain's memory hard limit using the following syntax:: <memtune> <hard_limit unit='G'>1</hard_limit> </memtune> It also implements the ``virDomainGetMemoryParameters()`` and ``virDomainSetMemoryParameters()`` APIs for controlling the memory hard limit of a running domain. * bhyve: Add virtio-console device support Domain XML can now use ``virtio-console`` devices. Among other things, these devices can be used to configure a QEMU Guest Agent:: <devices> <channel type='unix'> <source mode='bind' path='/var/run/libvirt/bhyve/bhyve.agent'/> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> </devices> Additionally, the ``virDomainQemuAgentCommand()`` API which allows running arbitrary guest agent commands is now supported. The ``virDomainGetHostname()`` API, used to query the hostname of a guest, now supports using the guest agent as a source of information. * Improvements * vircgroupv2: Implement freezer controller The CGroupV2 code now supports freezer controller which allows suspending and resuming of LXC domains. * virnetdevbandwidth: Only clear qdisc for defined directions Setting a QoS on a vNIC no longer leads to clearing (preconfigured) root queuing discipline ('qdisc`) in both directions (egress, ingress), only the affected one. * Bug fixes * storage: ZFS: Fix incorrect volsize and refreservation on zvol creation When creating a zvol, the ZFS driver listed all volumes in the pool and updated the new volume's size with data from the last volume in the list rather than the matching one. Now it correctly returns on valid one. * esx/vmware: VMs are tracked under different UUIDs by default The VMWare-related drivers were using allegedly unique IDs for domains, but it turned out they were not completely unique, even for the same host. That caused an issue where a different domain could have been acted upon then requested. Unfortunately, to make this work, the UUIDs of all VMWare-related domains will change from this release. In order to use the pre-v12.4.0 behaviour there is a new URI query parameter ``legacy_uuid`` which, if set to ``1``, will revert to the older way of working. * virsh: Provide no auth callbacks for bash completer The bash completer script calls virsh to provide completions. In some cases the underlying virsh might get stuck waiting on input (e.g. password for SSH session). Not anymore. * virauth: Verify virConnectAuth::cb is set in virAuthGetPasswordPath() A check was missing in ``virAuthGetPasswordPath()`` which might lead to crash of the client library when NULL callback was provided. This is now fixed. Enjoy. Jirka

1 0