From: Peter Krempa <pkrempa@redhat.com>
Date: Fri, 13 Mar 2020 13:24:35 +0000 (+0100)
Subject: news: Mention regression in virDomainBlockCopy with shallow+reuse flags
X-Git-Tag: v6.2.0-rc1~212
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=1cf2f412ed64027e570734beb53c275ae4566bcc;p=thirdparty%2Flibvirt.git

news: Mention regression in virDomainBlockCopy with shallow+reuse flags

Signed-off-by: Peter Krempa <pkrempa@redhat.com>
Reviewed-by: Kashyap Chamarthy <kchamart@redhat.com>
---

diff --git a/docs/news.xml b/docs/news.xml
index 7fd88f9998..ae4ee444d0 100644
--- a/docs/news.xml
+++ b/docs/news.xml
@@ -48,6 +48,24 @@
     <section title="Improvements">
     </section>
     <section title="Bug fixes">
+      <change>
+        <summary>
+          qemu: Open backing chain late for shallow block copy reusing external images
+        </summary>
+        <description>
+          With introduction of -blockdev for QEMU storage configuration
+          in libvirt-5.10 we've started opening the backing chain of the
+          destination/mirror of a virDomainBlockcopy started with
+          VIR_DOMAIN_BLOCK_COPY_REUSE_EXT | VIR_DOMAIN_BLOCK_COPY_SHALLOW flags
+          when starting the job rather than when virDomainBlockJobAbort with
+          VIR_DOMAIN_BLOCK_JOB_ABORT_PIVOT is issued. For users depending on
+          this undocumented quirky pre-blockdev behaviour this caused a
+          regression as the backing chain could not be modified while the copy
+          of the top image was progressing due to QEMU image locking. Note that
+          this fix also requires qemu-5.0 while -blockdev is used starting from
+          QEMU-4.2.
+        </description>
+      </change>
     </section>
   </release>
   <release version="v6.1.0" date="2020-03-03">