10:12 p.m.
From: Ján Tomko <jtomko(a)redhat.com>
Signed-off-by: Ján Tomko <jtomko(a)redhat.com>
---
NEWS.rst | 64 +++++++++++++++++++++++++++++++++++---------------------
1 file changed, 40 insertions(+), 24 deletions(-)
diff --git a/NEWS.rst b/NEWS.rst
index 03efead80f..9a8611ccb0 100644
--- a/NEWS.rst
+++ b/NEWS.rst
@@ -8,7 +8,23 @@ the changes introduced by each of them.
For a more fine-grained view, use the `git log`_.
-v11.2.0 (unreleased)
+v11.3.0 (unreleased)
+
+* **Security**
+
+* **Removed features**
+
+ * Remove support for the QEMU driver
+
+ As of today, the QEMU driver is no more.
+
+* **New features**
+
+* **Improvements**
+
+* **Bug fixes**
+
+v11.2.0 (also unreleased)
====================
* **Security**
@@ -350,7 +366,7 @@ v10.10.0 (2024-12-02)
* **Improvements**
- * qemu: Support UEFI NVRAM images on block storage
+ * qemu: Support UEFI VRAM images on block storage
Libvirt now allows users to use block storage as backend for UEFI NVRAM
images and allows them to be in format different than the template. When
@@ -408,7 +424,7 @@ v10.9.0 (2024-11-01)
* qemu: internal snapshot improvements
- The qemu internal snapshot handling code was updated to use modern commands
+ The qmu internal snapshot handling code was updated to use modern commands
which avoid the problems the old ones had, preventing use of internal
snapshots on VMs with UEFI NVRAM. Internal snapshots of VMs using UEFI are
now possible provided that the NVRAM is in ``qcow2`` format.
@@ -446,7 +462,7 @@ v10.8.0 (2024-10-01)
It is now permissable to have a ``<forward mode='open'>`` network that
has no IP address assigned to the host's port of the bridge. This
is the only way to create a libvirt network where guests are
- unreachable from the host (and vice versa) and also 0 firewall
+ unreachable from the host (and vice ersa) and also 0 firewall
rules are added on the host.
It is now also possible for a ``<forward mode='open'/>`` network to
@@ -531,7 +547,7 @@ v10.7.0 (2024-09-02)
* CVE-2024-8235: Crash of ``virtinterfaced`` via ``virConnectListInterfaces()``
A refactor of the code fetching the list of interfaces for multiple APIs
- introduced corner case on platforms where allocating 0 bytes of memory
+ introduced cornr case on platforms where allocating 0 bytes of memory
results in a NULL pointer.
This corner case would lead to a NULL-pointer dereference and subsequent
@@ -578,7 +594,7 @@ v10.6.0 (2024-08-05)
* qemu: Require QEMU-5.2.0 or newer
- The minimal required version of QEMU was bumped to 5.2.0.
+ The minimal requied version of QEMU was bumped to 5.2.0.
* **New features**
@@ -652,7 +668,7 @@ v10.5.0 (2024-07-01)
* Pass shutoff reason to release hook
Sometimes in release hook it is useful to know if the VM shutdown was
- graceful or not. This is especially useful to do cleanup based on the VM
+ graceful or not. This is especially useful todo cleanup based on the VM
shutdown failure reason in release hook. Starting with this release the
last argument 'extra' is used to pass VM shutoff reason in the call to
release hook.
@@ -698,7 +714,7 @@ v10.4.0 (2024-06-03)
used in the virNetClientIOEventFD callback while the data pointer's stack frame
was concurrently being "freed" when returning from
virNetClientIOEventLoop().
This flaw allows a local, unprivileged user to access virtproxyd without
- authenticating.
+ authenticatin.
* **New features**
@@ -799,7 +815,7 @@ v10.3.0 (2024-05-02)
Some PCI devices have large non-prefetchable memory. This can be a problem
in case when such device needs to be hotplugged as the firmware can't
- foresee such situation. The user thus can override the value calculated at
+ foresee such situation. The user thus can verride the value calculated at
start to accomodate for such devices.
* **Improvements**
@@ -859,7 +875,7 @@ v10.2.0 (2024-04-02)
Fix the flaw of the RPC library APIs of libvirt. The RPC server
de-serialization code allocates memory for arrays before the non-negative
- length check is performed by the C API entry points. Passing a negative length
+ length check is performed by the C API entry poits. Passing a negative length
to the g_new0 function results in a crash due to the negative length being
treated as a huge positive number. A local unprivileged user could use this
flaw to perform a denial of service attack by causing the libvirt daemon to
@@ -947,7 +963,7 @@ v10.1.0 (2024-03-01)
In **libvirt-5.10** a check for non-NULL arrays has been adjusted to
allow for NULL arrays with size 0 instead of rejecting all NULL
- arrays. However that made the above issue significantly worse since
+ arrays. However that made the above issue sigificantly worse since
that off-by-one error now did not write beyond an array, but
dereferenced said NULL pointer making the crash certain in a
specific scenario in which a NULL array of size 0 was passed to the
@@ -1080,7 +1096,7 @@ v10.0.0 (2024-01-15)
* qemu: Allow automatic resize of block-device-backed disk to full size of the device
The new flag ``VIR_DOMAIN_BLOCK_RESIZE_CAPACITY`` for
- ``virDomainBlockResize`` allows resizing a block-device backed ``raw`` disk
+ ``virDominBlockResize`` allows resizing a block-device backed ``raw`` disk
of a VM without the need to specify the full size of the block device.
* qemu: automatic selection/binding of VFIO variant drivers
@@ -1097,7 +1113,7 @@ v10.0.0 (2024-01-15)
Since the new nbdkit support requires a recent selinux policy that is not
widely available yet, it is now possible to build libvirt with nbdkit
support for remote disks but disabled at runtime. This behavior is
- controlled via the storage_use_nbdkit option of the qemu driver
+ controlled viathe storage_use_nbdkit option of the qemu driver
configuration file. The option will default to being disabled, but this may
change in a future release and can be customized with the
nbdkit_config_default build option.
@@ -1121,7 +1137,7 @@ v10.0.0 (2024-01-15)
The phase of copying storage during migration without shared storage
requires that both the source and destination image are identical in size.
This may not be possible if the destination is backed by a block device
- and the source image size is not a multiple of the block device block size.
+ and the source imae size is not a multiple of the block device block size.
Libvirt aleviates this by automatically adding a ``<slice>`` to match the
size of the source image rather than failing the migration.
@@ -1139,7 +1155,7 @@ v10.0.0 (2024-01-15)
* qemu: Various migration bug fixes and debuggability improvement
- This release fixes multiple bugs in virsh and libvirt in handling of
+ This release fixes multiple bugs in virsh and lbvirt in handling of
migration arguments and XMLs and modifies error reporting for better
debugging.
@@ -1156,7 +1172,7 @@ v10.0.0 (2024-01-15)
* qemu: Be less aggressive when dropping channel source paths
- Another regression is resolved, (introduced in 9.7.0) when libvirt was too
+ Another regression is resoled, (introduced in 9.7.0) when libvirt was too
aggressive when dropping parsed paths for <channel/> sources
* qemuDomainChangeNet: Reflect trustGuestRxFilters change
@@ -1183,7 +1199,7 @@ v9.10.0 (2023-12-01)
QEMU allows creating images where the 'backing file format' is actually a
protocol name such as 'file'/'host_device'/'nbd'/etc.. Adapt
libvirt to
- properly handle such images and don't assume automatic format probing is
+ properly handle such imags and don't assume automatic format probing is
necessary, which is in many cases forbidden due to security implications.
* **Bug fixes**
@@ -1417,7 +1433,7 @@ v9.5.0 (2023-07-03)
The device removal handler callback function didn't re-check the state of
the unplug operation after a timeout, which could rarely cause that the
- device was removed from the VM but not the definition.
+ device was removed from the VM butnot the definition.
* qemu: Fix NUMA memory allocation logic
@@ -1533,14 +1549,14 @@ v9.3.0 (2023-05-02)
Recent changes to UEFI firmware handling resulted into breaking support
for inactive internal snapshots of VMs with UEFI which historically worked.
(Although the intention was to disallow them together with active ones, but
- the check did not work properly.)
+ the check did not work properl.)
Preserve existing functionality by allowing such snapshots explicitly.
* qemu: Properly configure locked memory limit for VMs with ``<disk
type='nvme'``
The NVMe driver in qemu requires some memory to be locked. This was not
- taken into account in the code which calculates the memory limits based
+ taken into account in the cde which calculates the memory limits based
on devices present in the configuration
* Fix native build on win32
@@ -1550,7 +1566,7 @@ v9.3.0 (2023-05-02)
* qemu: Properly detect tray of hotplugged CD-ROM devices
- Media in a CD-ROM device which was hotplugged could not be changed as the
+ Media in a CD-ROM device which was hotplgged could not be changed as the
presence of the tray was not detected properly on hotplug.
@@ -1579,7 +1595,7 @@ v9.2.0 (2023-04-01)
system could have translated to a different firmware being chosen for
subsequent startups of the same domain, potentially rendering it unbootable
or lowering the security guarantees. Firmware selection now happens once,
- when the domain is defined, and its results are stored in the domain XML
+ when the domain is defined, and its resultsare stored in the domain XML
to be reused, unchanged, for all subsequent boots.
* qemu: passt now works when SELinux/AppArmor is enabled
@@ -1650,7 +1666,7 @@ v9.1.0 (2023-03-01)
* qemu: support automatic restart of inadvertently terminated passt process
If the passt process that is serving as the backend of a -netdev
- stream is terminated unexpectedly, libvirt now listens to QEMU's
+ stream is terminated nexpectedly, libvirt now listens to QEMU's
notification of this, and starts up a new passt instance, thus
preserving network connectivity.
@@ -1779,7 +1795,7 @@ v9.0.0 (2023-01-16)
* tools: Fix install_mode for some scripts
Scripts from the following list were installed with group write bit set:
- virt-xml-validate, virt-pki-validate, virt-sanlock-cleanup,
+ virt-xml-validate, virt-ki-validate, virt-sanlock-cleanup,
libvirt-guests.sh. This was changed so that only the owner is able to write
them.
--
2.49.0