There are some features/improvements/bug fixes I've either contributed or reviewed/merged. Document them for upcoming release. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> --- NEWS.rst | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/NEWS.rst b/NEWS.rst index XXXXXXX..XXXXXXX 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -XXX,XX +XXX,XX @@ v10.10.0 (unreleased) required to keep data "raw" on disk, but the use case requires features of the QCOW2 format such as incremental backups. + * swtpm: Add support for profiles + + Upcoming swtpm release will have TPM profile support that allows to + restrict a TPM's provided set of crypto algorithms and commands. Users can + now select profile by using ``<profile/>`` in their TPM XML definition. + * **Improvements** * qemu: Support UEFI NVRAM images on block storage @@ -XXX,XX +XXX,XX @@ v10.10.0 (unreleased) qcow2 is used as the format, the images are now also auto-populated from the template. + * qemu: Automatically add IOMMU when needed + + When domain of 'qemu' or 'kvm' type has more than 255 vCPUs IOMMU with EIM + mode is required. Starting with this release libvirt automatically adds one + (or turns on the EIM mode if there's IOMMU without it). + + * ch: allow hostdevs in domain definition + + The Cloud Hypervisor driver (ch) now supports ``<hostdev/>``-s. + + * ch: Enable callbacks for ch domain events + + The Cloud Hypervisor driver (ch) now supports emitting events on domain + define, undefine, start, boot, stop and destroy. + * **Bug fixes** * qemu: Fix reversion and inactive deletion of internal snapshots with UEFI NVRAM @@ -XXX,XX +XXX,XX @@ v10.10.0 (unreleased) firmware was allowed, but certain operations such as reversion or inactive deletion didn't work properly as they didn't consider the NVRAM qcow2 file. + * virnetdevopenvswitch: Warn on unsupported QoS settings + + For OpenVSwitch vNICs libivrt does not set QoS directly using 'tc' but + offloads setting to OVS. But OVS is not as feature full as libvirt in this + regard and setting different 'peak' than 'average' results in vNIC always + sticking with 'peak'. Produce a warning if that's the case. + v10.9.0 (2024-11-01) ==================== -- 2.45.2 From: Michal Privoznik <mprivozn@redhat.com> There are some features/improvements/bug fixes I've either contributed or reviewed/merged. Document them for upcoming release. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> --- NEWS.rst | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/NEWS.rst b/NEWS.rst index XXXXXXX..XXXXXXX 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -XXX,XX +XXX,XX @@ v12.0.0 (unreleased) Notably, issues that were preventing the use of firmware designed for confidential VMs on aarch64 have been addressed. + * network: Introduce port for DNS forwarder + + In the ``<dns/>`` section of network configuration users can set up + forwarding of DNS requests to custom DNS servers. These are specified using + ``addr`` attribute. But configuring port wasn't possible, until now. New + ``port`` attribute is introduced, which allows overriding the default DNS + port for given address. + * **Bug fixes** * qemu: Fix startup of VMs with more than ~25 external snapshots @@ -XXX,XX +XXX,XX @@ v12.0.0 (unreleased) on a shared filesystem on the destination but on the source it's either on a different NFS or unshared completely. + * qemu: Treat memory device source nodemask as strict NUMA policy + + Until now, the NUMA policy for ``<memory/>`` devices was taken either from + the guest NUMA node or ``<numatune/>``. But this may lead to discrepancies, + where the memory device is configured to bind to a set of host NUMA nodes, + but the guest NUMA node is to bind to a disjoint set of host NUMA nodes. To + resolve this, specifying ``<nodemask/>`` for a memory device implies + ``strict`` policy. + + * qemu: Relax validation of some hyperv features + + Since 11.9.0 release, libvirt performs dependency checks for hyperv + features, for instance ``stimer`` requires ``synic``. But as it turned out, + for some ancient machine types (e.g. 'pc-i440fx-3.0' or 'pc-q35-3.0') some + dependencies are not true. Corresponding checks were removed. + + * esx: URI encode inventory objects twice + + Formatting domain XML for domains on an ESX server might fail if + corresponding datacenter or datastore contained special characters (e.g. + '+'). This is now fixed. + v11.10.0 (2025-12-01) ===================== -- 2.52.0