From 5b08842d96a6af22571af091cb8b216b691e29de Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=A1n=20Tomko?= Date: Tue, 24 Mar 2015 17:13:24 +0100 Subject: [PATCH] Document behavior of compat when creating qcow2 volumes MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 --- docs/formatstorage.html.in | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) 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