[libvirt] [PATCH for 5.10.0] news: Update for 5.10.0 release
Signed-off-by: Michal Privoznik <mprivozn@redhat.com> --- docs/news.xml | 124 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 124 insertions(+) diff --git a/docs/news.xml b/docs/news.xml index 72c0edb317..b6782df136 100644 --- a/docs/news.xml +++ b/docs/news.xml @@ -81,8 +81,132 @@ </change> </section> <section title="Improvements"> + <change> + <summary> + Devices CGroup v2 support + </summary> + <description> + Libvirt supported all controllers of CGroup v2 but the devices + controller which is implemented in this release. + </description> + </change> + <change> + <summary> + Cold plug of sound device + </summary> + <description> + The QEMU driver now can handle cold plug of + <code><sound/></code> devices. + </description> + </change> + <change> + <summary> + More GLib integration + </summary> + <description> + More patches were merged that replace our internal functions with + GLib ones. Also some effort was invested in replacing gnulib modules + with GLib functions. + </description> + </change> + <change> + <summary> + Rewrite of Perl scripts into Python + </summary> + <description> + Libvirt used Perl scripts to check for coding style, generate some + code and things like that. To bring the number of languages used + down, these scripts were rewritten into Python. + </description> + </change> + <change> + <summary> + Probe for default CPU types + </summary> + <description> + With QEMU 4.2.0 we can probe for the default CPU model used by QEMU + for a particular machine type and store it in the domain XML. This + way the chosen CPU model is more visible to users and libvirt will + make sure the guest will see the exact same CPU after migration. + </description> + </change> + <change> + <summary> + Adaptation to qemu's blockdev + </summary> + <description> + QEMU introduced a new way of specifying disks on the command line + which enables fine-grained control over the block stack. Libvirt has + adapted to this. + </description> + </change> </section> <section title="Bug fixes"> + <change> + <summary> + Warn verbosely if using old loader:nvram pairs + </summary> + <description> + Some distributions still use <code>--with-loader-nvram</code> or + <code>nvram</code> variable in qemu.conf. This is now discouraged in + favour of FW descriptors. However, instead of silently ignoring user's + config, libvirt warns if outdated config is detected. + </description> + </change> + <change> + <summary> + Drop pconfig from Icelake-Server CPU model + </summary> + <description> + The pconfig feature was enabled in QEMU by accident in 3.1.0. All + other newer versions do not support it and it was removed from the + Icelake-Server CPU model in QEMU. + </description> + </change> + <change> + <summary> + Wait longer for device removal confirmation on PPC64 + </summary> + <description> + After sending device hot unplug request to QEMU, libvirt waits up to + 5 seconds for qemu to confirm the device removal. On some + architectures (like PPC64) this can take longer time and libvirt now + reflects that. + </description> + </change> + <change> + <summary> + Forcibly create nodes in domain's namespace + </summary> + <description> + The QEMU driver starts a domain in a namepsace with private + <code>/dev</code> and creates only those nodes there which the domain + is configured to have. However, it may have happened that if a node + changed its minor number this change wasn't propagated to the + namespace. + </description> + </change> + <change> + <summary> + Various AppArmor bugfixes + </summary> + <description> + The AppArmor driver now knows how to handle + <code><shmem/></code> devices and also snapshotting more disks + at once. + </description> + </change> + <change> + <summary> + Improved video model autoselection + </summary> + <description> + If a graphics device was added to XML that had no video device, + libvirt automatically added a video device which was always of type + 'cirrus' on x86_64, even if the underlying qemu didn't support + cirrus. Libvirt now bases the decision on qemu's capabilities. + </description> + </change> </section> </release> <release version="v5.9.0" date="2019-11-05"> -- 2.23.0
On Wed, Nov 27, 2019 at 11:24:56AM +0100, Michal Privoznik wrote:
Signed-off-by: Michal Privoznik <mprivozn@redhat.com> --- docs/news.xml | 124 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 124 insertions(+)
diff --git a/docs/news.xml b/docs/news.xml index 72c0edb317..b6782df136 100644 --- a/docs/news.xml +++ b/docs/news.xml @@ -81,8 +81,132 @@ </change> </section> <section title="Improvements">
[...]
+ <change> + <summary> + More GLib integration + </summary> + <description> + More patches were merged that replace our internal functions with + GLib ones. Also some effort was invested in replacing gnulib modules + with GLib functions. + </description> + </change> + <change> + <summary> + Rewrite of Perl scripts into Python + </summary> + <description> + Libvirt used Perl scripts to check for coding style, generate some + code and things like that. To bring the number of languages used + down, these scripts were rewritten into Python. + </description> + </change>
IIUC users are the target audience for the news. So far, these are just internal refactors that mostly benefit developers. Both will be user-visible changes only after we get rid of them. (Although I don't think the gnulib removal will be user-visible other than the build speedup) To the rest: Reviewed-by: Ján Tomko <jtomko@redhat.com> Jano
On Wed, Nov 27, 2019 at 01:05:04PM +0100, Ján Tomko wrote:
On Wed, Nov 27, 2019 at 11:24:56AM +0100, Michal Privoznik wrote:
Signed-off-by: Michal Privoznik <mprivozn@redhat.com> --- docs/news.xml | 124 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 124 insertions(+)
diff --git a/docs/news.xml b/docs/news.xml index 72c0edb317..b6782df136 100644 --- a/docs/news.xml +++ b/docs/news.xml @@ -81,8 +81,132 @@ </change> </section> <section title="Improvements">
[...]
+ <change> + <summary> + More GLib integration + </summary> + <description> + More patches were merged that replace our internal functions with + GLib ones. Also some effort was invested in replacing gnulib modules + with GLib functions. + </description> + </change> + <change> + <summary> + Rewrite of Perl scripts into Python + </summary> + <description> + Libvirt used Perl scripts to check for coding style, generate some + code and things like that. To bring the number of languages used + down, these scripts were rewritten into Python. + </description> + </change>
IIUC users are the target audience for the news. So far, these are just internal refactors that mostly benefit developers.
The target is also distro packagers, so they learn of things that might affect packaging design.
Both will be user-visible changes only after we get rid of them. (Although I don't think the gnulib removal will be user-visible other than the build speedup)
To the rest: Reviewed-by: Ján Tomko <jtomko@redhat.com>
Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
On Wed, Nov 27, 2019 at 12:08:01 +0000, Daniel Berrange wrote:
On Wed, Nov 27, 2019 at 01:05:04PM +0100, Ján Tomko wrote:
On Wed, Nov 27, 2019 at 11:24:56AM +0100, Michal Privoznik wrote:
Signed-off-by: Michal Privoznik <mprivozn@redhat.com> --- docs/news.xml | 124 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 124 insertions(+)
diff --git a/docs/news.xml b/docs/news.xml index 72c0edb317..b6782df136 100644 --- a/docs/news.xml +++ b/docs/news.xml @@ -81,8 +81,132 @@ </change> </section> <section title="Improvements">
[...]
+ <change> + <summary> + More GLib integration + </summary> + <description> + More patches were merged that replace our internal functions with + GLib ones. Also some effort was invested in replacing gnulib modules + with GLib functions. + </description> + </change> + <change> + <summary> + Rewrite of Perl scripts into Python + </summary> + <description> + Libvirt used Perl scripts to check for coding style, generate some + code and things like that. To bring the number of languages used + down, these scripts were rewritten into Python. + </description> + </change>
IIUC users are the target audience for the news. So far, these are just internal refactors that mostly benefit developers.
The target is also distro packagers, so they learn of things that might affect packaging design.
Well in this case we didn't really remove anything yet so even distro packagers may get saturated by these entries if we do it too often without any real change. https://en.wikipedia.org/wiki/The_Boy_Who_Cried_Wolf
On 11/27/19 1:19 PM, Peter Krempa wrote:
On Wed, Nov 27, 2019 at 12:08:01 +0000, Daniel Berrange wrote:
On Wed, Nov 27, 2019 at 01:05:04PM +0100, Ján Tomko wrote:
On Wed, Nov 27, 2019 at 11:24:56AM +0100, Michal Privoznik wrote:
Signed-off-by: Michal Privoznik <mprivozn@redhat.com> --- docs/news.xml | 124 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 124 insertions(+)
diff --git a/docs/news.xml b/docs/news.xml index 72c0edb317..b6782df136 100644 --- a/docs/news.xml +++ b/docs/news.xml @@ -81,8 +81,132 @@ </change> </section> <section title="Improvements">
[...]
+ <change> + <summary> + More GLib integration + </summary> + <description> + More patches were merged that replace our internal functions with + GLib ones. Also some effort was invested in replacing gnulib modules + with GLib functions. + </description> + </change> + <change> + <summary> + Rewrite of Perl scripts into Python + </summary> + <description> + Libvirt used Perl scripts to check for coding style, generate some + code and things like that. To bring the number of languages used + down, these scripts were rewritten into Python. + </description> + </change>
IIUC users are the target audience for the news. So far, these are just internal refactors that mostly benefit developers.
The target is also distro packagers, so they learn of things that might affect packaging design.
Well in this case we didn't really remove anything yet so even distro packagers may get saturated by these entries if we do it too often without any real change.
I view news.xml not only as a way of communicating changes to users/packagers but also as a way of giving credit to developers of some important features. If we don't want to advertise these two, that's fine. But then we should also consider blockdev paragraph - it's a change that's transparent to users, isn't it? Should they care that we implemented it? Michal
On Wed, Nov 27, 2019 at 01:34:12PM +0100, Michal Privoznik wrote:
On 11/27/19 1:19 PM, Peter Krempa wrote:
On Wed, Nov 27, 2019 at 12:08:01 +0000, Daniel Berrange wrote:
On Wed, Nov 27, 2019 at 01:05:04PM +0100, Ján Tomko wrote:
On Wed, Nov 27, 2019 at 11:24:56AM +0100, Michal Privoznik wrote:
Signed-off-by: Michal Privoznik <mprivozn@redhat.com> --- docs/news.xml | 124 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 124 insertions(+)
diff --git a/docs/news.xml b/docs/news.xml index 72c0edb317..b6782df136 100644 --- a/docs/news.xml +++ b/docs/news.xml @@ -81,8 +81,132 @@ </change> </section> <section title="Improvements">
[...]
+ <change> + <summary> + More GLib integration + </summary> + <description> + More patches were merged that replace our internal functions with + GLib ones. Also some effort was invested in replacing gnulib modules + with GLib functions. + </description> + </change> + <change> + <summary> + Rewrite of Perl scripts into Python + </summary> + <description> + Libvirt used Perl scripts to check for coding style, generate some + code and things like that. To bring the number of languages used + down, these scripts were rewritten into Python. + </description> + </change>
IIUC users are the target audience for the news. So far, these are just internal refactors that mostly benefit developers.
The target is also distro packagers, so they learn of things that might affect packaging design.
Well in this case we didn't really remove anything yet so even distro packagers may get saturated by these entries if we do it too often without any real change.
I view news.xml not only as a way of communicating changes to users/packagers but also as a way of giving credit to developers of some important features. If we don't want to advertise these two, that's fine. But then we should also consider blockdev paragraph - it's a change that's transparent to users, isn't it? Should they care that we implemented it?
Even though these changes are "internal" they can still be visible to users by virtue of having a high liklihood of introducing new bugs. I think it is worth highlight these kind of major internal refactorings for this reason. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
On Wed, Nov 27, 2019 at 12:38:00PM +0000, Daniel P. Berrangé wrote:
On Wed, Nov 27, 2019 at 01:34:12PM +0100, Michal Privoznik wrote:
On 11/27/19 1:19 PM, Peter Krempa wrote:
On Wed, Nov 27, 2019 at 12:08:01 +0000, Daniel Berrange wrote:
On Wed, Nov 27, 2019 at 01:05:04PM +0100, Ján Tomko wrote:
On Wed, Nov 27, 2019 at 11:24:56AM +0100, Michal Privoznik wrote:
Signed-off-by: Michal Privoznik <mprivozn@redhat.com> --- docs/news.xml | 124 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 124 insertions(+)
diff --git a/docs/news.xml b/docs/news.xml index 72c0edb317..b6782df136 100644 --- a/docs/news.xml +++ b/docs/news.xml @@ -81,8 +81,132 @@ </change> </section> <section title="Improvements">
[...]
+ <change> + <summary> + More GLib integration + </summary> + <description> + More patches were merged that replace our internal functions with + GLib ones. Also some effort was invested in replacing gnulib modules + with GLib functions. + </description> + </change> + <change> + <summary> + Rewrite of Perl scripts into Python + </summary> + <description> + Libvirt used Perl scripts to check for coding style, generate some + code and things like that. To bring the number of languages used + down, these scripts were rewritten into Python. + </description> + </change>
IIUC users are the target audience for the news. So far, these are just internal refactors that mostly benefit developers.
The target is also distro packagers, so they learn of things that might affect packaging design.
Well in this case we didn't really remove anything yet so even distro packagers may get saturated by these entries if we do it too often without any real change.
I view news.xml not only as a way of communicating changes to users/packagers but also as a way of giving credit to developers of some important features. If we don't want to advertise these two, that's fine. But then we should also consider blockdev paragraph - it's a change that's transparent to users, isn't it? Should they care that we implemented it?
On its own it should be transparent, but the switch to blockdev did fix some actual user-visible bugs that depended on it. Peter should have the list.
Even though these changes are "internal" they can still be visible to users by virtue of having a high liklihood of introducing new bugs. I think it is worth highlight these kind of major internal refactorings for this reason.
Okay, can we put them into a new "Refactors" section instead? Jano
Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
-- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
On Wed, Nov 27, 2019 at 02:21:14PM +0100, Ján Tomko wrote:
On Wed, Nov 27, 2019 at 12:38:00PM +0000, Daniel P. Berrangé wrote:
On Wed, Nov 27, 2019 at 01:34:12PM +0100, Michal Privoznik wrote:
On 11/27/19 1:19 PM, Peter Krempa wrote:
On Wed, Nov 27, 2019 at 12:08:01 +0000, Daniel Berrange wrote:
On Wed, Nov 27, 2019 at 01:05:04PM +0100, Ján Tomko wrote:
On Wed, Nov 27, 2019 at 11:24:56AM +0100, Michal Privoznik wrote: > Signed-off-by: Michal Privoznik <mprivozn@redhat.com> > --- > docs/news.xml | 124 ++++++++++++++++++++++++++++++++++++++++++++++++++ > 1 file changed, 124 insertions(+) > > diff --git a/docs/news.xml b/docs/news.xml > index 72c0edb317..b6782df136 100644 > --- a/docs/news.xml > +++ b/docs/news.xml > @@ -81,8 +81,132 @@ > </change> > </section> > <section title="Improvements">
[...]
> + <change> > + <summary> > + More GLib integration > + </summary> > + <description> > + More patches were merged that replace our internal functions with > + GLib ones. Also some effort was invested in replacing gnulib modules > + with GLib functions. > + </description> > + </change> > + <change> > + <summary> > + Rewrite of Perl scripts into Python > + </summary> > + <description> > + Libvirt used Perl scripts to check for coding style, generate some > + code and things like that. To bring the number of languages used > + down, these scripts were rewritten into Python. > + </description> > + </change>
IIUC users are the target audience for the news. So far, these are just internal refactors that mostly benefit developers.
The target is also distro packagers, so they learn of things that might affect packaging design.
Well in this case we didn't really remove anything yet so even distro packagers may get saturated by these entries if we do it too often without any real change.
I view news.xml not only as a way of communicating changes to users/packagers but also as a way of giving credit to developers of some important features. If we don't want to advertise these two, that's fine. But then we should also consider blockdev paragraph - it's a change that's transparent to users, isn't it? Should they care that we implemented it?
On its own it should be transparent, but the switch to blockdev did fix some actual user-visible bugs that depended on it. Peter should have the list.
Even though these changes are "internal" they can still be visible to users by virtue of having a high liklihood of introducing new bugs. I think it is worth highlight these kind of major internal refactorings for this reason.
Okay, can we put them into a new "Refactors" section instead?
Fine with me. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
participants (4)
-
Daniel P. Berrangé -
Ján Tomko -
Michal Privoznik -
Peter Krempa