NuKVM/libvirt
3
0
Fork 0
mirror of https://github.com/libvirt/libvirt.git synced 2026-08-09 12:38:27 -05:00
Code Issues Packages Projects Releases Wiki Activity

docs: Note that zero detection on migration sparsifies image only when discard='unmap' is set

Browse Source 
The mirroring job clears the destination to ensure that the guest
visible disk contents are identical to the state on the source. The
image itself is kept sparse only when the disk 'discard' option is set
to 'unmap' (Also the disks would eventually desparsify itself anyways
with disabled discards). Note it in the docs for the user.

Signed-off-by: Peter Krempa <pkrempa@redhat.com>
Acked-by: Eric Blake <eblake@redhat.com>
This commit is contained in:
Peter Krempa
2025-06-12 10:16:06 +02:00
parent 6733f02c40
commit cf24dc8baa
2 changed files with 8 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/manpages/virsh.rst
+3 -2
View File
@@ -3641,8 +3641,9 @@ host. By default only non-shared non-readonly images are transferred. Use
transfer via the comma separated ``disk-list`` argument.
The *--migrate-disks-detect-zeroes* option which takes a comma separated list of
disk target names enables zeroed block detection for the listed migrated disks.
These blocks are not transferred or allocated on destination, effectively
sparsifying the disk at the cost of CPU overhead.
These blocks are not transferred or allocated (requires that 'discard' option
on given disk is set to 'unmap') on destination, effectively sparsifying the
disk at the cost of CPU overhead.
With *--copy-storage-synchronous-writes* flag used the disk data migration will
synchronously handle guest disk writes to both the original source and the
destination to ensure that the disk migration converges at the price of possibly