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

[Andrea Bolognani]

Signed-off-by: Andrea Bolognani <abologna at redhat.com>
---
I've CC'd all those who introduced the changes mentioned below,
both to give them a chance to point out any mistake I might have
made and to possibly annoy them into updating the release notes
themselves next time :)

 docs/news.xml | 83 +++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 83 insertions(+)

diff --git a/docs/news.xml b/docs/news.xml
index 468d34093a..65c23e51b6 100644
--- a/docs/news.xml
+++ b/docs/news.xml
@@ -61,6 +61,16 @@
           Support specifying extended TSEG size for SMM in QEMU.
         </description>
       </change>
+      <change>
+        <summary>
+          qemu: Add support for SEV guests
+        </summary>
+        <description>
+          SEV (Secure Encrypted Virtualization) is a feature available on AMD
+          CPUs that encrypts the guest memory and makes it inaccessible even
+          to the host OS.
+        </description>
+      </change>
     </section>
     <section title="Removed features">
       <change>
@@ -76,6 +86,24 @@
           secret objects, but that support was never added to libvirt.
         </description>
       </change>
+      <change>
+        <summary>
+          Make GnuTLS mandatory
+        </summary>
+        <description>
+          Building without GnuTLS is no longer possible.
+        </description>
+      </change>
+      <change>
+        <summary>
+          qemu: Remove allow_disk_format_probing configuration option
+        </summary>
+        <description>
+          The option represented a security risk when used with malicious
+          disk images, so users were recommended against enabling it; with
+          this release, it's been removed altogether.
+        </description>
+      </change>
     </section>
     <section title="Improvements">
       <change>
@@ -130,6 +158,41 @@
           or virStorageVolCreateXMLFrom.
         </description>
       </change>
+      <change>
+        <summary>
+          qemu: Add support for vsock hot (un)plug and cold (un)plug
+        </summary>
+      </change>
+      <change>
+        <summary>
+          qemu: Add support for NBD over TLS
+        </summary>
+        <description>
+          Securely accessing NBD volumes no longer requires tunnelling over
+          SSH or another secure protocol: the native TLS support can now be
+          used instead.
+        </description>
+      </change>
+      <change>
+        <summary>
+          qemu: Implement FD passing for Unix sockets
+        </summary>
+        <description>
+          Instead of having QEMU open the socket and then connecting to it,
+          which is inherently racy, starting with QEMU 2.12 we can open the
+          socket ourselves and pass it to QEMU, avoiding race conditions.
+        </description>
+      </change>
+      <change>
+        <summary>
+          virsh: Introduce --nowait option for domstat command
+        </summary>
+        <description>
+          When this option is specified, virsh will try to fetch the guest
+          stats but abort instead of stalling if they can't be retrieved right
+          away.
+        </description>
+      </change>
     </section>
     <section title="Bug fixes">
       <change>
@@ -143,6 +206,26 @@
           us getting to the worker pool initialization.
         </description>
       </change>
+      <change>
+        <summary>
+          qemu: Fix domain resume after failed migration
+        </summary>
+        <description>
+          Recent versions of QEMU activate block devices before the guest CPU
+          has been started, which makes it impossible to roll back a failed
+          migration. Use the <code>late-block-activate</code> migration
+          capability if supported to avoid the issue.
+        </description>
+      </change>
+      <change>
+        <summary>
+          vmx: Permit guests to have an odd number of vCPUs
+        </summary>
+        <description>
+          This was forbidden in the past, but current versions of ESX can
+          deal with a guest configured as such.
+        </description>
+      </change>
     </section>
   </release>
   <release version="v4.4.0" date="2018-06-04">
-- 
2.17.1