news: Update for 4.7.0 release

Signed-off-by: Andrea Bolognani <abologna@redhat.com>
Reviewed-by: Martin Kletzander <mkletzan@redhat.com>

diff --git a/docs/news.xml b/docs/news.xml
index 2b6d08dc0249d39cf580da783050dcd0d9b49e3b..ef7c0d68b4c0e3ea99b1dd575fac28d223bb5f38 100644 (file)
--- a/docs/news.xml
+++ b/docs/news.xml
@@ -71,8 +71,53 @@
           Support the vhost-vsock-ccw device on S390.
         </description>
       </change>
+      <change>
+        <summary>
+          qemu: Make default machine type independent of QEMU
+        </summary>
+        <description>
+          We can't control whether or not QEMU will change its default
+          machine type in the future, or whether downstream distributions
+          will decide to compile out some machine types, so our only option
+          to provide a predictable behavior is taking care of the default
+          ourselves; management applications and users are encouraged to
+          explicitly pick a machine type when creating new guests.
+        </description>
+      </change>
+      <change>
+        <summary>
+          apparmor: Various improvements
+        </summary>
+        <description>
+          Rules have been added to deal with a number of scenarios that
+          didn't work correctly.
+        </description>
+      </change>
     </section>
     <section title="Bug fixes">
+      <change>
+        <summary>
+          esx: Truncate CPU model name
+        </summary>
+        <description>
+          Some CPU model names are too long to be stored into the
+          corresponding property, and should be explicitly truncated
+          to avoid unexpected behavior in users of the
+          <code>virNodeGetInfo()</code> API such as
+          <code>virsh nodeinfo</code>.
+        </description>
+      </change>
+      <change>
+        <summary>
+          utils: Remove arbitrary limit on socket_id/core_id
+        </summary>
+        <description>
+          Both values were assumed to be smaller than 4096, but in fact
+          they are entirely hardware-dependent and there have been reports
+          of machines presenting much bigger values, preventing libvirt from
+          working correctly; all such limits have now been removed.
+        </description>
+      </change>
     </section>
   </release>
   <release version="v4.6.0" date="2018-08-06">