On Tue, May 02, 2017 at 18:23:08 +0200, Andrea Bolognani wrote:
These entries cover a number of features, improvements and bug fixes that had not been documented during the development cycle. --- docs/news.xml | 115 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+)
diff --git a/docs/news.xml b/docs/news.xml index 36d2ee3..38dc17f 100644 --- a/docs/news.xml +++ b/docs/news.xml
<section title="Bug fixes"> + <change> + <summary> + nss: Don't require a network restart for libvirt_guest + </summary> + <description> + Previously, the libvirt_guest NSS module would only work properly + after the corresponding network had been restarted; now newly + started guests will be reported correctly right away. + </description> + </change> + <change> + <summary> + storage: Remove unavailable transient pools after restart + </summary> + <description> + Solve an issue where transient storage pools would be stuck in an + unmanageable state if the source disappeared and libvirtd was + subsequently restarted. + </description> + </change> + <change> + <summary> + storage: Fix capacity value for LUKS encrypted volumes + </summary> + <description> + The 'capacity' value (e.g. guest logical size) for a LUKS volume is + smaller than the 'physical' value of the file in the file system, so + we need to account for that. + </description>
Rather than this I'd mention the bug in the padding of data passed to qemu: 71890992daf37ec78b00b4ce873369421dc99731
+ </change> + <change> + <summary> + qemu: Fix regression when hyperv/vendor_id feature is used + </summary> + <description> + Guests using the feature would not be started at all; it is now + possible to start them as expected. + </description> + </change> + <change> + <summary> + qemu: Do not crash on USB address with no port and invalid bus + </summary> + </change> + <change> + <summary> + virsh: Report initialization errors + </summary> + <description> + Sometimes virsh might be unable to start: when that happens, report + useful diagnostics instead of failing silently.
This does not seem to be a bugfix, but rather an improvement.
+ </description> + </change> </section> </release> <release version="v3.2.0" date="2017-04-02">
ACK