On 03/27/2017 11:40 AM, Peter Krempa wrote: > Mention the hyperv notifier and the new API to set block thresholds. > --- > docs/news.xml | 25 +++++++++++++++++++++++++ > 1 file changed, 25 insertions(+) > > diff --git a/docs/news.xml b/docs/news.xml > index 814bd93fd..2dbd2335d 100644 > --- a/docs/news.xml > +++ b/docs/news.xml > @@ -70,6 +70,20 @@ > introducing a new host device type in the XML. > </description> > </change> > + <change> > + <summary> > + Add support for block device threshold event > + </summary> > + <description> > + When using thin provisioning, management tools need to resize the > + disk in certain cases. To avoid having them to poll disk usage > + this version introduces an event which will be fired when a given > + offset of the storage is written by the hypervisor. Together with the > + API it allows registering thresholds for given storage backing > + volumes and this event will then notify management if the threshold > + is exceeded. Currently only the qemu driver supports this. > + </description> > + </change> > </section> > <section title="Improvements"> > <change> > @@ -94,6 +108,17 @@ > applications running on the platform. > </description> > </change> > + <change> > + <summary> > + Write hyperv crash information into vm log > + </summary> > + <description> > + qemu's implementation of the hyperv panic notifier now reports > + information about the crash from the guest os. Libvirt starting from > + this version logs the information to the vm log file for possible Maybe "Starting with this version, libvirt logs the information..." ACK. > + debugging. > + </description> > + </change> > </section> > <section title="Bug fixes"> > <change> > -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
