3 usage: qemu-img command [command options]
9 The following commands are supported:
11 @item create [-e] [-b @var{base_image}] [-f @var{fmt}] @var{filename} [@var{size}]
12 @item commit [-f @var{fmt}] @var{filename}
13 @item convert [-c] [-e] [-f @var{fmt}] @var{filename} [-O @var{output_fmt}] @var{output_filename}
14 @item info [-f @var{fmt}] @var{filename}
20 is a disk image filename
22 is the read-only disk image which is used as base for a copy on
23 write image; the copy on write image only stores the modified data
26 is the disk image format. It is guessed automatically in most cases. The following formats are supported:
31 Raw disk image format (default). This format has the advantage of
32 being simple and easily exportable to all other emulators. If your file
33 system supports @emph{holes} (for example in ext2 or ext3 on Linux),
34 then only the written sectors will reserve space. Use @code{qemu-img
35 info} to know the real size used by the image or @code{ls -ls} on
39 QEMU image format, the most versatile format. Use it to have smaller
40 images (useful if your filesystem does not supports holes, for example
41 on Windows), optional AES encryption and zlib based compression.
43 User Mode Linux Copy On Write image format. Used to be the only growable
44 image format in QEMU. It is supported only for compatibility with
45 previous versions. It does not work on win32.
47 VMware 3 and 4 compatible image format.
49 Linux Compressed Loop image, useful only to reuse directly compressed
50 CD-ROM images present for example in the Knoppix CD-ROMs.
54 is the disk image size in kilobytes. Optional suffixes @code{M}
55 (megabyte) and @code{G} (gigabyte) are supported
58 is the destination disk image filename
61 is the destination format
64 indicates that target image must be compressed (qcow format only)
66 indicates that the target image must be encrypted (qcow format only)
72 @item create [-e] [-b @var{base_image}] [-f @var{fmt}] @var{filename} [@var{size}]
74 Create the new disk image @var{filename} of size @var{size} and format
77 If @var{base_image} is specified, then the image will record only the
78 differences from @var{base_image}. No size needs to be specified in
79 this case. @var{base_image} will never be modified unless you use the
80 @code{commit} monitor command.
82 @item commit [-f @var{fmt}] @var{filename}
84 Commit the changes recorded in @var{filename} in its base image.
86 @item convert [-c] [-e] [-f @var{fmt}] @var{filename} [-O @var{output_fmt}] @var{output_filename}
88 Convert the disk image @var{filename} to disk image @var{output_filename}
89 using format @var{output_fmt}. It can be optionnaly encrypted
90 (@code{-e} option) or compressed (@code{-c} option).
92 Only the format @code{qcow} supports encryption or compression. The
93 compression is read-only. It means that if a compressed sector is
94 rewritten, then it is rewritten as uncompressed data.
96 Encryption uses the AES format which is very secure (128 bit keys). Use
97 a long password (16 characters) to get maximum protection.
99 Image conversion is also useful to get smaller image when using a
100 growable format such as @code{qcow} or @code{cow}: the empty sectors
101 are detected and suppressed from the destination image.
103 @item info [-f @var{fmt}] @var{filename}
105 Give information about the disk image @var{filename}. Use it in
106 particular to know the size reserved on disk which can be different
107 from the displayed size.
114 @setfilename qemu-img
115 @settitle QEMU disk image utility
118 The HTML documentation of QEMU for more precise information and Linux
119 user mode emulator invocation.