mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2025-03-20 07:59:00 +00:00
news: Mention regression in virDomainBlockCopy with shallow+reuse flags
Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Kashyap Chamarthy <kchamart@redhat.com>
This commit is contained in:
parent
c43969e164
commit
1cf2f412ed
@ -48,6 +48,24 @@
|
|||||||
<section title="Improvements">
|
<section title="Improvements">
|
||||||
</section>
|
</section>
|
||||||
<section title="Bug fixes">
|
<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>
|
</section>
|
||||||
</release>
|
</release>
|
||||||
<release version="v6.1.0" date="2020-03-03">
|
<release version="v6.1.0" date="2020-03-03">
|
||||||
|
Loading…
x
Reference in New Issue
Block a user