[PATCH for 6.7.0] NEWS: Document improvements/bug fixes for upcoming release
Neal Gompa
ngompa13 at gmail.com
Fri Aug 28 12:48:58 UTC 2020
On Fri, Aug 28, 2020 at 7:45 AM Michal Privoznik <mprivozn at redhat.com> wrote:
>
> Signed-off-by: Michal Privoznik <mprivozn at redhat.com>
> ---
> NEWS.rst | 34 ++++++++++++++++++++++++++++++++++
> 1 file changed, 34 insertions(+)
>
> diff --git a/NEWS.rst b/NEWS.rst
> index 852746eb2a..4ed4e45590 100644
> --- a/NEWS.rst
> +++ b/NEWS.rst
> @@ -33,6 +33,10 @@ v6.7.0 (unreleased)
>
> * **Improvements**
>
> + * Libvirt switch to Meson build system
> +
> + Libvirt abandoned autotools and switched to Meson build system.
> +
> * Allow sparse streams for block devices
>
> Sparse streams (e.g. ``virsh vol-download --sparse`` or ``virsh vol-upload
> @@ -58,6 +62,36 @@ v6.7.0 (unreleased)
> either don't have device mapper enabled or where the dm-mod module is not
> loaded yet. This is now fixed.
>
> + * resctrl: Use exclusive lock for /sys/fs/resctrl
> +
> + When two or more domains were attempted to start at once, due to a bug in
> + implementation, resctrl was not locked properly and thus threads did not
> + mutually exclude with each other resulting in not setting requested
> + limitations as requested.
> +
> + * mdev: Fix daemon crash when reattaching mdevs on assignment conflict
> +
> + If there's a list of mdevs to be assigned to a domain, but one of them (NOT
> + the first) is already assigned to a different domain then libvirtd would
> + crash. This is now fixed.
> +
> + * Fix logic in setting COW flag on btrfs
> +
> + When COW is not explicitly requested to be disabled or enabled, then
> + libvirt should do nothing on non-BTRFS file systems.
> +
> + * Avoid crash due to race in glib event loop code
> +
> + Libvirt switched to glib event loop in 6.1.0 but it was also tickling a bug
> + in glib code leading to the daemon crash. Libvirt way of calling glib was
> + changed so the daemon crashes no more.
> +
> + * virdevmapper: Handle kernel without device-mapper support
> +
> + In the previous release, Libvirt dropped libdevmapper in favor of its own
> + implementation. But the implementation did not handle kernels without
> + device-mapper support. This is now fixed.
> +
>
> v6.6.0 (2020-08-02)
> ===================
> --
> 2.26.2
>
Reviewed-by: Neal Gompa <ngompa13 at gmail.com>
--
真実はいつも一つ!/ Always, there's only one truth!
More information about the libvir-list
mailing list