May 2026 - Devel - libvirt List Archives

[PATCH pushed] vircgroup: Fix fallback implementation of 'virCgroupGetFreezerState'
by Peter Krempa 04 May '26

04 May '26

From: Peter Krempa <pkrempa(a)redhat.com> Fix the implementation according to the change to the declaration. Fixes: 289e69d95e6fc843499d15003365596fbfe3500a Signed-off-by: Peter Krempa <pkrempa(a)redhat.com> --- src/util/vircgroup.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/util/vircgroup.c b/src/util/vircgroup.c index e7c93cd010..00949bcca5 100644 --- a/src/util/vircgroup.c +++ b/src/util/vircgroup.c @@ -3737,7 +3737,7 @@ virCgroupSetFreezerState(virCgroup *group G_GNUC_UNUSED, int virCgroupGetFreezerState(virCgroup *group G_GNUC_UNUSED, - virCgroupFreezerState **state G_GNUC_UNUSED) + virCgroupFreezerState *state G_GNUC_UNUSED) { virReportSystemError(ENOSYS, "%s", _("Control groups not supported on this platform")); -- 2.54.0

1 0

[PATCH] docs: bhyve: document virtio-console and blkiotune
by Roman Bogorodskiy 04 May '26

04 May '26

Add sections describing usage of the virtio-console device and about block I/O tuning. Signed-off-by: Roman Bogorodskiy <bogorodskiy(a)gmail.com> --- docs/drvbhyve.rst | 38 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+) diff --git a/docs/drvbhyve.rst b/docs/drvbhyve.rst index e9eceb8740..79418537df 100644 --- a/docs/drvbhyve.rst +++ b/docs/drvbhyve.rst @@ -819,6 +819,44 @@ Example: Every NUMA domain must have `memory` and `cpus` specified. Bhyve allows configuring up to 8 NUMA domains. +Virtio-console device +~~~~~~~~~~~~~~~~~~~~~ + +:since:`Since 12.4.0`, it is possible to use the virtio console device. +Example:: + + <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> + +Bhyve supports up to 16 ports per console. + +Block I/O Tuning +~~~~~~~~~~~~~~~~ +:since:`Since 12.3.0`, it is possible to tune domain I/O. +This works on top of the +`rctl(4) <https://man.freebsd.org/cgi/man.cgi?query=rctl&sektion=4>`__ +framework. +Sample configuration:: + + <blkiotune> + <device> + <path>*</path> + <read_iops_sec>20000</read_iops_sec> + <write_iops_sec>20000</write_iops_sec> + <read_bytes_sec>10000</read_bytes_sec> + <write_bytes_sec>10000</write_bytes_sec> + </device> + </blkiotune> + +The ``*`` path here means that the limits are applied to the domain +as a whole. Currently, it is not possible to apply limits to the +individual devices of the domain. + Guest-specific considerations ----------------------------- -- 2.52.0

2 1

[PATCH] remote: install the secrets unit only for systemd
by Roman Bogorodskiy 04 May '26

04 May '26

Install the secrets unit only when the init script is systemd. Fixes: 2db552dc6ac17596720071fa91181055db7b82ee Signed-off-by: Roman Bogorodskiy <bogorodskiy(a)gmail.com> --- src/remote/meson.build | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/remote/meson.build b/src/remote/meson.build index dfd61df62f..25995fdbc2 100644 --- a/src/remote/meson.build +++ b/src/remote/meson.build @@ -345,7 +345,7 @@ endif # The monolithic libvirt daemon only attempts to load the # secrets encryption credentials if the secret driver is enabled -if conf.has('WITH_SECRETS') +if conf.has('WITH_SECRETS') and init_script == 'systemd' secret_dropin_conf = configuration_data({ 'localstatedir': localstatedir, }) -- 2.52.0

2 1

[PATCH] ZFS: fix incorrect volsize,refreservation on zvol creation
by George Melikov 03 May '26

03 May '26

From: George Melikov <mail(a)gmelikov.ru> Reproduce: ```bash # Order is crucial here, if we create zvol with name which won't be last - we'll get size from different zvol root@minime:~# virsh vol-list rpool Name Path ---------------------------------------------------------------------------------------------------- da52bdd9-eb75-5746-a2ce-a511067914f5 /dev/zvol/rpool/disks/da52bdd9-eb75-5746-a2ce-a511067914f5 faafd0f9-33c8-5b23-990c-fa7b4bfe8dcf /dev/zvol/rpool/disks/faafd0f9-33c8-5b23-990c-fa7b4bfe8dcf # Create zvol with name which will be before `faaf...` root@minime:~# cat > /tmp/vol <volume> <name>eeee</name> <capacity>4294967296</capacity> <allocation>4294967296</allocation> </volume> root@minime:~# virsh vol-create rpool /tmp/vol Vol eeee created from /tmp/vol root@minime:~# virsh vol-list rpool Name Path ---------------------------------------------------------------------------------------------------- da52bdd9-eb75-5746-a2ce-a511067914f5 /dev/zvol/rpool/disks/da52bdd9-eb75-5746-a2ce-a511067914f5 eeee /dev/zvol/rpool/disks/eeee faafd0f9-33c8-5b23-990c-fa7b4bfe8dcf /dev/zvol/rpool/disks/faafd0f9-33c8-5b23-990c-fa7b4bfe8dcf # Here we've got Capacity from last zvol (ordered by name) root@minime:~# virsh vol-info --pool rpool eeee Name: eeee Type: block Capacity: 10.00 GiB Allocation: 0.00 B # Full refresh fixes it root@minime:~# virsh pool-refresh --pool rpool Pool rpool refreshed root@minime:~# virsh vol-info --pool rpool eeee Name: eeee Type: block Capacity: 4.00 GiB Allocation: 4.06 GiB ``` Fix is trivial: check zvol by name and return early if this is different zvol. Signed-off-by: George Melikov <mail(a)gmelikov.ru> --- src/storage/storage_backend_zfs.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/storage/storage_backend_zfs.c b/src/storage/storage_backend_zfs.c index 33434d0cac..2cb555a6e6 100644 --- a/src/storage/storage_backend_zfs.c +++ b/src/storage/storage_backend_zfs.c @@ -132,8 +132,10 @@ virStorageBackendZFSParseVol(virStoragePoolObj *pool, if (vol == NULL) volume = virStorageVolDefFindByName(pool, vol_name); - else + else if (STREQ(vol_name, vol->name)) volume = vol; + else + return 0; if (volume == NULL) { volume = g_new0(virStorageVolDef, 1); -- 2.53.0

2 1

Release of libvirt-12.3.0
by Jiri Denemark 02 May '26

02 May '26

The 12.3.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: Add blkiotune support The bhyve driver now supports guest I/O throttling configuration:: <blkiotune> <device> <path>*</path> <read_iops_sec>20000</read_iops_sec> <write_iops_sec>20000</write_iops_sec> <read_bytes_sec>10000</read_bytes_sec> <write_bytes_sec>10000</write_bytes_sec> </device> </blkiotune> It uses the ``rctl(4)`` framework to apply these limits. * bhyve: Implement ``virDomainInterfaceAddresses()`` and ``virDomainGetHostname()`` The bhyve driver now implements APIs allowing to fetch address of VM's interfaces (accessible via ``virsh domifaddr``) and the hostname of the VM (``virsh domhostname``). * hyperv: Implement ``virDomainGetGuestInfo()`` The hyperv driver now implements API for fetching guest information (``virsh guestinfo``). * Improvements * security: Don't error out on security labels of type='none' Previously, libvirt reported an error if a domain with seclabel of type='none' (meaning do not take this security model into account for this domain) was being started and the model wasn't available (for instance, in case of SELinux it was disabled at boot). * Allow for multiple PCI root buses, not just for a single one numbered '0' `virPCIDeviceReset()` and `virPCIDeviceIsBehindSwitchLackingACS()` no longer use a hardcoded check (e.g bus == 0 ) to determine if a device is attached to a "root bus". This allows for better support on more complex PCI topologies. * Add mechanism to prevent accidental shrink of device with ``virsh blockresize`` A new flag ``VIR_DOMAIN_BLOCK_RESIZE_EXTEND`` was introduced which prevents accidental shrinking of the block device of the VM. The flag is exposed as ``virsh blockresize --extend``. * Expose ``MemAvailable`` field from kernel's meminfo as ``VIR_NODE_MEMORY_STATS_AVAILABLE`` * Bug fixes * virnetdevmacvlan: Wait for udev to settle after creating macvtap When starting a domain with a macvtap device (or when hotplugging one), libvirt creates the device and opens its ``/dev`` representation in order to set it according to the ``<interface/>`` XML (e.g. MAC address, queues, etc.). But if the system is under heavy load, it might happen that after the device creation the udev daemon was triggered, but did not have enough time to set the ``/dev`` representation fully. This may result in various misconfiguration or even failed ``open()``. Therefore, libvirt waits after device creation for udev daemon to settle down. * apparmor: Don't drop macvtap devices from profile on blockjobs Enjoy. Jirka

1 0