June 2026 - Devel - libvirt List Archives

[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

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