docs/news.xml | 43 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 43 insertions(+)
Signed-off-by: Andrea Bolognani <abologna@redhat.com>
---
docs/news.xml | 43 +++++++++++++++++++++++++++++++++++++++++++
1 file changed, 43 insertions(+)
diff --git a/docs/news.xml b/docs/news.xml
index 2b6d08dc02..3233796f32 100644
--- a/docs/news.xml
+++ b/docs/news.xml
@@ -71,8 +71,51 @@
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.
+ </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">
--
2.17.1
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
On Mon, Sep 03, 2018 at 01:55:55PM +0200, Andrea Bolognani wrote: >Signed-off-by: Andrea Bolognani <abologna@redhat.com> >--- > docs/news.xml | 43 +++++++++++++++++++++++++++++++++++++++++++ > 1 file changed, 43 insertions(+) > >diff --git a/docs/news.xml b/docs/news.xml >index 2b6d08dc02..3233796f32 100644 >--- a/docs/news.xml >+++ b/docs/news.xml >@@ -71,8 +71,51 @@ > 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 case you are referring to 242b7c2d38afc88692065314f73c151f8bc345b2 (which I believe you are), then I'd suggest mentioning this happens in the output of virNodeGetInfo (or virsh nodeinfo). Reviewed-by: Martin Kletzander <mkletzan@redhat.com> >+ </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"> >-- >2.17.1 > >-- >libvir-list mailing list >libvir-list@redhat.com >https://www.redhat.com/mailman/listinfo/libvir-list -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
© 2016 - 2024 Red Hat, Inc.