ShuriZma
/
xemu
mirror of https://github.com/xemu-project/xemu.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

qemu-img: Document copy offloading implications with -S and -c 

Explicitly enabling zero detection or compression suppresses copy
offloading during convert. Document it.

Suggested-by: Kevin Wolf <kwolf@redhat.com>
Signed-off-by: Fam Zheng <famz@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
This commit is contained in:
Fam Zheng 2018-07-11 09:22:27 +08:00 committed by Kevin Wolf
parent 2f9d4083f7
commit eb461485f4
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
qemu-img.texi
View File

@ -96,7 +96,8 @@ will enumerate information about backing files in a disk image chain. Refer
below for further description.
@item -c
indicates that target image must be compressed (qcow format only)
indicates that target image must be compressed (qcow format only). If this
option is used, copy offloading will not be attempted.
@item -h
with or without a command shows help and lists the supported formats
@ -115,7 +116,8 @@ in case both @var{-q} and @var{-p} options are used.
indicates the consecutive number of bytes that must contain only zeros
for qemu-img to create a sparse image during conversion. This value is rounded
down to the nearest 512 bytes. You may use the common size suffixes like
@code{k} for kilobytes.
@code{k} for kilobytes. If this option is used, copy offloading will not be
attempted.
@item -t @var{cache}
specifies the cache mode that should be used with the (destination) file. See