diff options
| author |   aliguori <aliguori@c046a42c-6fe2-441c-8c8c-71466251a162> | 2009-03-28 17:55:19 +0000 |
|---|---|---|
| committer | aliguori <aliguori@c046a42c-6fe2-441c-8c8c-71466251a162> | 2009-03-28 17:55:19 +0000 |
| commit | 9230eaf6797ffce465aef2a6c5b26d605c162a24 (patch) | |
| tree | 7ab0a286bd63e6715cc7eb13b6e6921464055ce8 /qemu-img.texi | |
| parent | block-qcow2: keep backing file format in a qcow2 extension (Uri Lublin) (diff) | |
| download | qemu-kvm-9230eaf6797ffce465aef2a6c5b26d605c162a24.tar.gz qemu-kvm-9230eaf6797ffce465aef2a6c5b26d605c162a24.tar.bz2 qemu-kvm-9230eaf6797ffce465aef2a6c5b26d605c162a24.zip | |
qemu-img: adding a "-F base_fmt" option to "qemu-img create -b" (Uri Lublin)
If the user specifies the backing file format,
then when opening the backing file, there is no need
to probe the (backing file) image to figure out its format.
This follows my previous patches implementing bdrv_create2
which keeps (for qcow2 only) the backing file format
as a qcow2-extension
Suggested by Daniel P. Berrange.
Signed-off-by: Uri Lublin <uril@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@6910 c046a42c-6fe2-441c-8c8c-71466251a162
Diffstat (limited to 'qemu-img.texi')
| -rw-r--r-- | qemu-img.texi | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/qemu-img.texi b/qemu-img.texi index a40f84168..deef2ab62 100644 --- a/qemu-img.texi +++ b/qemu-img.texi @@ -8,7 +8,7 @@ usage: qemu-img command [command options] The following commands are supported: @table @option -@item create [-e] [-6] [-b @var{base_image}] [-f @var{fmt}] @var{filename} [@var{size}] +@item create [-e] [-6] [-F @var{base_fmt}] [-b @var{base_image}] [-f @var{fmt}] @var{filename} [@var{size}] @item commit [-f @var{fmt}] @var{filename} @item convert [-c] [-e] [-6] [-f @var{fmt}] [-O @var{output_fmt}] [-B @var{output_base_image}] @var{filename} [@var{filename2} [...]] @var{output_filename} @item info [-f @var{fmt}] @var{filename} @@ -27,6 +27,8 @@ forces the output image to be created as a copy on write image of the specified base image; @code{output_base_image} should have the same content as the input's base image, however the path, image format, etc may differ +@item base_fmt +is the disk image format of @var{base_image}. for more information look at @var{fmt} @item fmt is the disk image format. It is guessed automatically in most cases. The following formats are supported: |