[libvirt] [PATCH] news: Update for 5.7.0 release

Andrea Bolognani abologna at redhat.com
Tue Sep 3 12:26:23 UTC 2019


On Tue, 2019-09-03 at 14:09 +0200, Michal Privoznik wrote:
> Signed-off-by: Michal Privoznik <mprivozn at redhat.com>
> ---
>  docs/news.xml | 133 ++++++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 133 insertions(+)
> 
> diff --git a/docs/news.xml b/docs/news.xml
> index 0c79765fd0..f95af0f0e9 100644
> --- a/docs/news.xml
> +++ b/docs/news.xml
> @@ -50,6 +50,30 @@
[...]
> +        <summary>
> +          Split libvirtd into separate daemons
> +        </summary>
> +        <description>
> +          The big monolithic libvirtd daemon can now be replaced by smaller
> +          per-driver daemons. Distributions can chose if they want the former
> +          or the latter. The libvirtd is still kept around for backwards
> +          compatibility.

We might want to point out that things like SELinux support and
identity passing are not implemented yet, so distributions will
probably want to hold off using the split daemons by default for a
little while longer... Dan?

> +        <summary>
> +          Report RNG device in domain capabilities XML
> +        </summary>
> +        <description>
> +          Libvirt now reports if RNG device is supported by underlying
> +          hypervisor in domain capabilities XML.

Libvirt now reports if RNG devices are supported by the underlying
hypervisor in the domain capabilities XML.

> +        <summary>
> +          Stop linking virt-login-shell and NSS plugins with libvirt.so
> +        </summary>
> +        <description>
> +          In order to allow libvirt abort on out of memory, we need to stop
> +          link libvirt.so to virt-login-shell or the NSS plugins where we don't

In order to allow libvirt to abort on out of memory, we need to stop
linking...

> +        <summary>
> +          qemu: Allow migration with disk cache on
> +        </summary>
> +        <description>
> +          When QEMU supports flushing caches at the end of migration, we can
> +          safely allow migration even if <code>disk/driver/@cache</code> is not

s/not/neither/

> +        <summary>
> +          Various D-Bus fixes
> +        </summary>
> +        <description>
> +          When D-Bus is not available, Libvirt was reporting random errors.

s/Libvirt/libvirt/

> +        <summary>
> +          Prefer read only opening of PCI config files

s/read only/read-only/

> +        </summary>
> +        <description>
> +          When enumerating PCI bus, Libvirt opens config files under

s/Libvirt/libvirt/

> +        <summary>
> +          Fix AppArmor profile
> +        </summary>
> +        <description>
> +          Since the <code>5.6.0</code> release, Libvirt uses

s/Libvirt/libvirt/


With the nits above fixed,

  Reviewed-by: Andrea Bolognani <abologna at redhat.com>

and safe for freeze. Thanks a lot for agreeing to be volunteered to
take care of this ;)


And since you've already spent quite some time on this, I took the
liberty of addressing all of the above locally and pushing, so that
you don't have to do anything else. Thanks again!

-- 
Andrea Bolognani / Red Hat / Virtualization




More information about the libvir-list mailing list