On Fri, Jun 28, 2024 at 10:54:14 +0200, Michal Privoznik wrote: > There are some features/improvements/bug fixes I've either > contributed or reviewed/merged. Document them for upcoming > release. > > Signed-off-by: Michal Privoznik <mpriv...@redhat.com> > --- > NEWS.rst | 30 ++++++++++++++++++++++++++++++ > 1 file changed, 30 insertions(+) > > diff --git a/NEWS.rst b/NEWS.rst > index bc8acc62d4..d675c869a4 100644 > --- a/NEWS.rst > +++ b/NEWS.rst > @@ -16,6 +16,10 @@ v10.5.0 (unreleased) > * **Removed features** > > * **New features** > + * Introduce SEV-SNP support > + > + SEV-SNP is introduced as another type of ``<launchSecurity/>``. Its > support > + is reported in both domain capabilities and ``virt-host-validate``. > > * **Improvements** > > @@ -26,8 +30,34 @@ v10.5.0 (unreleased) > the dependency on ``certtool`` and providing more comprehensive checks > of the certificate properties. > > + * qemu: implement iommu coldplug/unplug > + > + The ``<iommu/>`` device can be now cold plugged and/or cold unplugged. > + > + * 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 > + shutdown failure reason in release hook. String with this release the > last
s/String/Starting/ ? > + argument 'extra' is used to pass VM shutoff reason in the call to release > + hook. > + > + * nodedev: improve DASD detection > + > + In newer DASD driver versions the ID_TYPE tag is supported. This tag is > + missing after a system reboot but when the ccw device is set offline and > + online the tag is included. To fix this version independently we need to > + check if devices detected as type disk is actually a DASD to maintain s/if devices/if a device/ or alternatively s/disk is/disk are/ and s/a DASD/DASDs/ > + the node object consistency and not end up with multiple node objects > + for DASDs. > + > * **Bug fixes** > > + * remote_daemon_dispatch: Unref sasl session when closing client connection > + > + A memory leak was identified when a client started SASL but then suddenly > + closed connection. This is now fixed. > + > > v10.4.0 (2024-06-03) > ==================== Reviewed-by: Jiri Denemark <jdene...@redhat.com>
