[libvirt] [PATCH v2] news: Prepare for 3.7.0 release

Documents some changes that have slipped through the cracks during the development cycle. Signed-off-by: Andrea Bolognani <abologna(a)redhat.com&gt; --- Changes from [v1]: * rebase on top of master * remove the part about guests no longer disappearing if the QEMU binary is missing, since Peter already documented that [v1] https://www.redhat.com/archives/libvir-list/2017-September/msg00030.html docs/news.xml | 76 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 76 insertions(+) diff --git a/docs/news.xml b/docs/news.xml index dd8967e25..141b1a42a 100644 --- a/docs/news.xml +++ b/docs/news.xml @@ -69,6 +69,18 @@ you can configure reconnect timeout if the connection is closed. </description> </change> + <change> + <summary> + qemu: Implement editing guest configuration for managed save files + </summary> + <description> + New <code>managedsave-define</code>, <code>managedsave-edit</code> + and <code>managedsave-dumpxml</code> commands have been added to + <code>virsh</code> to allow editing the guest configuration for + managed save files just like it was already possible for unmanaged + save files. + </description> + </change> </section> <section title="Improvements"> <change> @@ -81,6 +93,43 @@ indication for users (and devs). </description> </change> + <change> + <summary> + apparmor: Update for QEMU 2.10 compatibility + </summary> + <description> + Starting with version 2.10, QEMU locks disk images and NVRAM files + to prevent them from being corrupted; however, file locking needs to + be explicitly allowed through <code>virt-aa-helper</code> or AppArmor + will reject the requests and the guest will not be able to run. + </description> + </change> + <change> + <summary> + virsh: List Unix sockets in 'domdisplay' output + </summary> + <description> + VNC and SPICE graphics can use Unix sockets instead of TCP/IP sockets + as connection endpoints, but such a configuration was not handled + correctly by <code>virsh domdisplay</code>, causing the respective + endpoints to be missing from the output. + </description> + </change> + <change> + <summary> + qemu: Don't check whether offline migration is safe + </summary> + <description> + Since offline migration only copies the guest definition to the + destination host, data corruption is not a concern and the operation + can always be performed safely. + </description> + </change> + <change> + <summary> + virt-host-validate: Fix IOMMU detection on ppc64 + </summary> + </change> </section> <section title="Bug fixes"> <change> @@ -115,6 +164,33 @@ are missing during startup. </description> </change> + <change> + <summary> + qemu: Prevent pSeries guests from disappearing in some situations + </summary> + <description> + pSeries guest would disappear if any of the host devices they were + configured to use was not available during libvirtd startup, which + could easily happen for SR-IOV Virtual Functions. This scenario is + now handled correctly. + </description> + </change> + <change> + <summary> + qemu: Honor <code>&lt;on_reboot/&gt;</code> setting + </summary> + <description> + The setting was accepted by the parser, but not actually implemented. + </description> + </change> + <change> + <summary> + daemon: Fix <code>--verbose</code> option + </summary> + <description> + The option had not been working as intended from v3.0.0 onwards. + </description> + </change> </section> </release> <release version="v3.6.0" date="2017-08-02"> -- 2.13.5