     usage: qemu-img command [command options]

The following commands are supported:

     [file qemu-img-cmds.texi not included]

Command parameters:

filename
     is a disk image filename

fmt
     is the disk image format. It is guessed automatically in most cases. See below for a description of the supported disk formats.

size
     is the disk image size in bytes. Optional suffixes k or K (kilobyte, 1024) M (megabyte, 1024k) and G (gigabyte, 1024M) and T (terabyte, 1024G) are supported.  b is ignored.

output_filename
     is the destination disk image filename

output_fmt
     is the destination format

options
     is a comma separated list of format specific options in a name=value format. Use -o ? for an overview of the options supported by the used format or see the format descriptions below for details.

-c
     indicates that target image must be compressed (qcow format only)

-h
     with or without a command shows help and lists the supported formats

-p
     display progress bar (convert and rebase commands only)

-S SIZE
     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 k for kilobytes.

-t CACHE
     specifies the cache mode that should be used with the (destination) file. See the documentation of the emulator's -drive cache=... option for allowed values.

Parameters to snapshot subcommand:

snapshot
     is the name of the snapshot to create, apply or delete

-a
     applies a snapshot (revert disk to saved state)

-c
     creates a snapshot

-d
     deletes a snapshot

-l
     lists all snapshots in the given image

Command description:

check [-f FMT] FILENAME

     Perform a consistency check on the disk image FILENAME.

     Only the formats qcow2, qed and vdi support consistency checks.

create [-f FMT] [-o OPTIONS] FILENAME [SIZE]

     Create the new disk image FILENAME of size SIZE and format FMT. Depending on the file format, you can add one or more OPTIONS that enable additional features of this format.

     If the option BACKING_FILE is specified, then the image will record only the differences from BACKING_FILE. No size needs to be specified in this case. BACKING_FILE will never be modified unless you use the commit monitor command (or qemu-img commit).

     The size can also be specified using the SIZE option with -o, it doesn't need to be specified separately in this case.

commit [-f FMT] [-t CACHE] FILENAME

     Commit the changes recorded in FILENAME in its base image.

convert [-c] [-p] [-f FMT] [-t CACHE] [-O OUTPUT_FMT] [-o OPTIONS] [-s SNAPSHOT_NAME] [-S SPARSE_SIZE] FILENAME [FILENAME2 [...]] OUTPUT_FILENAME

     Convert the disk image FILENAME or a snapshot SNAPSHOT_NAME to disk image OUTPUT_FILENAME using format OUTPUT_FMT. It can be optionally compressed (-c option) or use any format specific options like encryption (-o option).

     Only the formats qcow and qcow2 support compression. The compression is read-only. It means that if a compressed sector is rewritten, then it is rewritten as uncompressed data.

     Image conversion is also useful to get smaller image when using a growable format such as qcow or cow: the empty sectors are detected and suppressed from the destination image.

     You can use the BACKING_FILE option to force the output image to be created as a copy on write image of the specified base image; the BACKING_FILE should have the same content as the input's base image, however the path, image format, etc may differ.

info [-f FMT] FILENAME

     Give information about the disk image FILENAME. Use it in particular to know the size reserved on disk which can be different from the displayed size. If VM snapshots are stored in the disk image, they are displayed too.

snapshot [-l | -a SNAPSHOT | -c SNAPSHOT | -d SNAPSHOT ] FILENAME

     List, apply, create or delete snapshots in image FILENAME.

rebase [-f FMT] [-t CACHE] [-p] [-u] -b BACKING_FILE [-F BACKING_FMT] FILENAME

     Changes the backing file of an image. Only the formats qcow2 and qed support changing the backing file.

     The backing file is changed to BACKING_FILE and (if the image format of FILENAME supports this) the backing file format is changed to BACKING_FMT.

     There are two different modes in which rebase can operate:

     Safe mode
          This is the default mode and performs a real rebase operation. The new backing file may differ from the old one and qemu-img rebase will take care of keeping the guest-visible content of FILENAME unchanged.

          In order to achieve this, any clusters that differ between BACKING_FILE and the old backing file of FILENAME are merged into FILENAME before actually changing the backing file.

          Note that the safe mode is an expensive operation, comparable to converting an image. It only works if the old backing file still exists.

     Unsafe mode
          qemu-img uses the unsafe mode if -u is specified. In this mode, only the backing file name and format of FILENAME is changed without any checks on the file contents. The user must take care of specifying the correct new backing file, or the guest-visible content of the image will be corrupted.

          This mode is useful for renaming or moving the backing file to somewhere else. It can be used without an accessible old backing file, i.e. you can use it to fix an image whose backing file has already been moved/renamed.

     You can use rebase to perform a ``diff'' operation on two disk images.  This can be useful when you have copied or cloned a guest, and you want to get back to a thin image on top of a template or base image.

     Say that base.img has been cloned as modified.img by copying it, and that the modified.img guest has run so there are now some changes compared to base.img.  To construct a thin image called diff.qcow2 that contains just the differences, do:

          qemu-img create -f qcow2 -b modified.img diff.qcow2
          qemu-img rebase -b base.img diff.qcow2

     At this point, modified.img can be discarded, since base.img + diff.qcow2 contains the same information.

resize FILENAME [+ | -]SIZE

     Change the disk image as if it had been created with SIZE.

     Before using this command to shrink a disk image, you MUST use file system and partitioning tools inside the VM to reduce allocated file systems and partition sizes accordingly.  Failure to do so will result in data loss!

     After using this command to grow a disk image, you must use file system and partitioning tools inside the VM to actually begin using the new space on the device.

Supported image file formats:

raw

     Raw disk image format (default). This format has the advantage of being simple and easily exportable to all other emulators. If your file system supports holes (for example in ext2 or ext3 on Linux or NTFS on Windows), then only the written sectors will reserve space. Use qemu-img info to know the real size used by the image or ls -ls on Unix/Linux.

qcow2
     QEMU image format, the most versatile format. Use it to have smaller images (useful if your filesystem does not supports holes, for example on Windows), optional AES encryption, zlib based compression and support of multiple VM snapshots.

     Supported options:

     backing_file
          File name of a base image (see create subcommand)

     backing_fmt
          Image format of the base image

     encryption
          If this option is set to on, the image is encrypted.

          Encryption uses the AES format which is very secure (128 bit keys). Use a long password (16 characters) to get maximum protection.

     cluster_size
          Changes the qcow2 cluster size (must be between 512 and 2M). Smaller cluster sizes can improve the image file size whereas larger cluster sizes generally provide better performance.

     preallocation
          Preallocation mode (allowed values: off, metadata). An image with preallocated metadata is initially larger but can improve performance when the image needs to grow.

qcow
     Old QEMU image format. Left for compatibility.

     Supported options:

     backing_file
          File name of a base image (see create subcommand)

     encryption
          If this option is set to on, the image is encrypted.

cow
     User Mode Linux Copy On Write image format. Used to be the only growable image format in QEMU. It is supported only for compatibility with previous versions. It does not work on win32.

vdi
     VirtualBox 1.1 compatible image format.

vmdk
     VMware 3 and 4 compatible image format.

     Supported options:

     backing_fmt
          Image format of the base image

     compat6
          Create a VMDK version 6 image (instead of version 4)

vpc
     VirtualPC compatible image format (VHD).

cloop
     Linux Compressed Loop image, useful only to reuse directly compressed CD-ROM images present for example in the Knoppix CD-ROMs.