[PATCH for 6.6.0] NEWS: Document changes for upcoming release

Michal Privoznik posted 1 patch 2 weeks ago
Test syntax-check failed
Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/libvirt tags/patchew/ad1d38cd2ad1f5db819b859a5e47c0925432a11d.1596207147.git.mprivozn@redhat.com
NEWS.rst | 32 ++++++++++++++++++++++++++++++++
1 file changed, 32 insertions(+)

[PATCH for 6.6.0] NEWS: Document changes for upcoming release

Posted by Michal Privoznik 2 weeks ago
In contrast with other releases, this time NEWS is pretty much
updated. I've identified only a couple of features/bug fixes
worth mentioning that were not mentioned yet.

Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
---
 NEWS.rst | 32 ++++++++++++++++++++++++++++++++
 1 file changed, 32 insertions(+)

diff --git a/NEWS.rst b/NEWS.rst
index 1314f3e698..d97ca501dc 100644
--- a/NEWS.rst
+++ b/NEWS.rst
@@ -24,6 +24,12 @@ v6.6.0 (unreleased)
     MAC addresses that would generate a new one if they were in its OUI
     (00:0c:29).
 
+  * conf: add control over COW for storage pool directories
+
+    The storage pool code now attempts to disable COW by default on btrfs, but
+    management applications may wish to override this behaviour. This is now
+    possible via new ``cow`` element.
+
 * **Improvements**
 
   * esx: Change the NIC limit for recent virtualHW versions
@@ -41,6 +47,14 @@ v6.6.0 (unreleased)
     The event can now be used also for block copy destinations by using the
     index of the ``<mirror>`` image.
 
+  * qemu: consider available CPUs in ``vcpupin/emulatorpin`` output
+
+    This patch changes the default bitmap of ``vcpupin`` and ``emulatorpin``,
+    in the case of domains with static vcpu placement, all available CPUs
+    instead of all possible CPUs are returned making these APIs consistent with
+    the behavior of ``vcpuinfo``.
+
+
 * **Bug fixes**
 
   * virdevmapper: Don't use libdevmapper to obtain dependencies
@@ -61,6 +75,24 @@ v6.6.0 (unreleased)
     Starting from libvirt-6.5 an active layer block commit or a block copy could
     fail if the same destination was used more than once.
 
+  * qemu: Don't change ownership of restore file
+
+    When restoring a domain from a file, Libvirt no longer changes its ownership.
+
+  * qemu: Set SPAPR TPM default to 2.0 and prevent 1.2 choice
+
+    The firmware (SLOF) on QEMU for ppc64 does not support TPM 1.2, so prevent
+    the choice of TPM 1.2 when the SPAPR device model is chosen and use a
+    default of '2.0' (TPM 2) for the backend.
+
+  * qemu: Do not set ``//cpu/@migratable`` for running domains
+
+    Libvirt release of 6.4.0 started to fill the default value for
+    ``//cpu/@migratable`` attribute according to QEMU support. However, active
+    domains either have the migratable attribute already set or they were
+    started with older Libvirt which doesn't support the attribute.
+
+
 v6.5.0 (2020-07-03)
 ===================
 
-- 
2.26.2

Re: [PATCH for 6.6.0] NEWS: Document changes for upcoming release

Posted by Neal Gompa 1 week ago
On Fri, Jul 31, 2020 at 10:53 AM Michal Privoznik <mprivozn@redhat.com> wrote:
>
> In contrast with other releases, this time NEWS is pretty much
> updated. I've identified only a couple of features/bug fixes
> worth mentioning that were not mentioned yet.
>
> Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
> ---
>  NEWS.rst | 32 ++++++++++++++++++++++++++++++++
>  1 file changed, 32 insertions(+)
>
> diff --git a/NEWS.rst b/NEWS.rst
> index 1314f3e698..d97ca501dc 100644
> --- a/NEWS.rst
> +++ b/NEWS.rst
> @@ -24,6 +24,12 @@ v6.6.0 (unreleased)
>      MAC addresses that would generate a new one if they were in its OUI
>      (00:0c:29).
>
> +  * conf: add control over COW for storage pool directories
> +
> +    The storage pool code now attempts to disable COW by default on btrfs, but
> +    management applications may wish to override this behaviour. This is now
> +    possible via new ``cow`` element.
> +
>  * **Improvements**
>
>    * esx: Change the NIC limit for recent virtualHW versions
> @@ -41,6 +47,14 @@ v6.6.0 (unreleased)
>      The event can now be used also for block copy destinations by using the
>      index of the ``<mirror>`` image.
>
> +  * qemu: consider available CPUs in ``vcpupin/emulatorpin`` output
> +
> +    This patch changes the default bitmap of ``vcpupin`` and ``emulatorpin``,
> +    in the case of domains with static vcpu placement, all available CPUs
> +    instead of all possible CPUs are returned making these APIs consistent with
> +    the behavior of ``vcpuinfo``.
> +
> +
>  * **Bug fixes**
>
>    * virdevmapper: Don't use libdevmapper to obtain dependencies
> @@ -61,6 +75,24 @@ v6.6.0 (unreleased)
>      Starting from libvirt-6.5 an active layer block commit or a block copy could
>      fail if the same destination was used more than once.
>
> +  * qemu: Don't change ownership of restore file
> +
> +    When restoring a domain from a file, Libvirt no longer changes its ownership.
> +
> +  * qemu: Set SPAPR TPM default to 2.0 and prevent 1.2 choice
> +
> +    The firmware (SLOF) on QEMU for ppc64 does not support TPM 1.2, so prevent
> +    the choice of TPM 1.2 when the SPAPR device model is chosen and use a
> +    default of '2.0' (TPM 2) for the backend.
> +
> +  * qemu: Do not set ``//cpu/@migratable`` for running domains
> +
> +    Libvirt release of 6.4.0 started to fill the default value for
> +    ``//cpu/@migratable`` attribute according to QEMU support. However, active
> +    domains either have the migratable attribute already set or they were
> +    started with older Libvirt which doesn't support the attribute.
> +
> +
>  v6.5.0 (2020-07-03)
>  ===================
>
> --
> 2.26.2
>

Looks great! Thank you for doing this. :)

Reviewed-by: Neal Gompa <ngompa13@gmail.com>

-- 
真実はいつも一つ!/ Always, there's only one truth!


Re: [PATCH for 6.6.0] NEWS: Document changes for upcoming release

Posted by Andrea Bolognani 2 weeks ago
On Fri, 2020-07-31 at 16:53 +0200, Michal Privoznik wrote:
> In contrast with other releases, this time NEWS is pretty much
> updated. I've identified only a couple of features/bug fixes
> worth mentioning that were not mentioned yet.
> 
> Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
> ---
>  NEWS.rst | 32 ++++++++++++++++++++++++++++++++
>  1 file changed, 32 insertions(+)

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

and safe for freeze. Thanks for your continued efforts in keeping the
release notes accurate, detailed and up to date :)

-- 
Andrea Bolognani / Red Hat / Virtualization

Re: [PATCH for 6.6.0] NEWS: Document changes for upcoming release

Posted by Ján Tomko 2 weeks ago
On a Friday in 2020, Michal Privoznik wrote:
>In contrast with other releases, this time NEWS is pretty much
>updated. I've identified only a couple of features/bug fixes
>worth mentioning that were not mentioned yet.
>
>Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
>---
> NEWS.rst | 32 ++++++++++++++++++++++++++++++++
> 1 file changed, 32 insertions(+)
>

Reviewed-by: Ján Tomko <jtomko@redhat.com>

Jano