From: Ján Tomko Date: Tue, 24 Mar 2015 16:13:24 +0000 (+0100) Subject: Document behavior of compat when creating qcow2 volumes X-Git-Tag: v1.2.9.3~22 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=5b08842d96a6af22571af091cb8b216b691e29de;p=thirdparty%2Flibvirt.git Document behavior of compat when creating qcow2 volumes Commit bab2eda changed the behavior for missing compat attribute, but failed to update the documentation. Before, the option was omitted from qemu-img command line and the qemu-img default was used. Now we always specify the compat value and the default is 0.10. Reported by Christophe Fergeau https://bugzilla.gnome.org/show_bug.cgi?id=746660#c4 (cherry picked from commit 7c8ae42d495d683f79ae4baf024f29f089eaa573) Signed-off-by: Ján Tomko --- diff --git a/docs/formatstorage.html.in b/docs/formatstorage.html.in index d3e6f05c2b..51e4d4296c 100644 --- a/docs/formatstorage.html.in +++ b/docs/formatstorage.html.in @@ -532,8 +532,9 @@ type='qcow2' volumes. Valid values are 0.10 and 1.1 so far, specifying QEMU version the images should be compatible with. If the feature element is present, - 1.1 is used. If omitted, qemu-img default is used. - Since 1.1.0 + 1.1 is used. + Since 1.1.0 If omitted, 0.10 is used. + Since 1.1.2
nocow
Turn off COW of the newly created volume. So far, this is only valid