Signed-off-by: Fabiano Fidêncio <fidencio@xxxxxxxxxx>
---
I went through the commits since last release and added a few notes
which seem to be relevant for the news.
In case you notice there's something missing, please, either send me the
text to add it (and I'll re-sping this patch) and add the text before
merging this one.
---
docs/news.xml | 88 +++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 88 insertions(+)
diff --git a/docs/news.xml b/docs/news.xml
index 3ed6ff8aeb..29b12cb04d 100644
--- a/docs/news.xml
+++ b/docs/news.xml
@@ -44,6 +44,50 @@
and virDomainPMWakeup APIs.
</description>
</change>
+ <change>
+ utils: Introduce monitor capability interface
+ </change>
+ <description>
+ The resource monitor has been introduced and it creates the interface
+ for getting the host capability of the resource monitor from the system
+ resource control.
+ The resource monitor takes the role of RDT monitoring groups and could
+ be used to monitor the resource consumption information.
+ </description>
+ <change>
+ conf: Introduce RDT monitor host capability
+ </change>
+ <description>
+ Introduce cache monitor (CMT) and memory bandwidth monitor (MBM).
+ For the former (CMT), the host capability is shown like:
+ <host>
+ ...
+ <cache>
+ <bank id='0' level='3' type='both' size='15' unit='MiB' cpus='0-5'>
+ <control granularity='768' min='1536' unit='KiB' type='both' maxAllocs='4'/>
+ </bank>
+ <monitor level='3' 'reuseThreshold'='270336' maxMonitors='176'>
+ <feature name='llc_occupancy'/>
+ </monitor>
+ </cache>
+ ...
+ </host>
+
+ For the latter (MBM), the capability is shown like this:
+ <host>
+ ...
+ <memory_bandwidth>
+ <node id='1' cpus='6-11'>
+ <control granularity='10' min ='10' maxAllocs='4'/>
+ </node>
+ <monitor maxMonitors='176'>
+ <feature name='mbm_total_bytes'/>
+ <feature name='mbm_local_bytes'/>
+ </monitor>
+ </memory_bandwidth>
+ ...
+ </host>
+ </description>
</section>
<section title="Removed features">
<change>
@@ -55,6 +99,15 @@
Drop support for these older versions and require Xen >= 4.6.
</description>
</change>
+ <change>
+ <summary>
+ nwfilter: Disallow binding creation in session mode
+ </summary>
+ <description>
+ Ensure that a filter binding creation is not attempted in session
+ mode and generate the proper error message.
+ </description>
+ </change>
</section>
<section title="Improvements">
<change>
@@ -68,8 +121,43 @@
Guest Agent.
</description>
</change>
+ <change>
+ storage: Allow to use any format as input volume for encryption
+ </change>
+ <description>
+ Since v4.5.0 libvirt has support to use a 'raw' input volume for
+ encryption. From now on, let's not limit this to 'raw' only.
+ </description>
+ <change>
+ libxl: Add support to set shadow memory for any guest type, not only
+ HVM
+ </change>
+ <description>
+ PVH guests now can take advantage of using shadow memory.
+ </description>
</section>
<section title="Bug fixes">
+ <change>
+ <summary>
+ virsh: Require explicit --domain for domxml-to-native
+ </summary>
+ <description>
+ The domxml-to-native virsh command accepts either --xml or --domain
+ option followed by a file or domain name respectively, The --domain
+ option is documented as required, which means an argument with no
+ option is treated as --xml. Commit v4.3.0-127-gd86531daf2 broke this
+ by making --domain optional and thus an argument with no option was
+ treated as --domain.
+ </description>
+ </change>
+ <change>
+ lxc_monitor: Avoid AB / BA lock race
+ </change>
+ <description>
+ A dealock situation could occur when autostarting a LXC domain 'guest'
+ due to two threads attempting to take opposing locks while holding
+ opposing locks (AB BA problem).
+ </description>
</section>
</release>
<release version="v4.7.0" date="2018-09-03">
--
2.19.0
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list
