]> git.proxmox.com Git - qemu.git/blame - qemu-img.texi
tcg-sparc: Use TCG_TARGET_REG_BITS in conditional compilation.
[qemu.git] / qemu-img.texi
CommitLineData
acd935ef
FB
1@example
2@c man begin SYNOPSIS
3usage: qemu-img command [command options]
4@c man end
5@end example
6
7@c man begin OPTIONS
8
9The following commands are supported:
153859be
SB
10
11@include qemu-img-cmds.texi
acd935ef
FB
12
13Command parameters:
14@table @var
15@item filename
16 is a disk image filename
5fafdf24 17@item fmt
f932c040
KW
18is the disk image format. It is guessed automatically in most cases. See below
19for a description of the supported disk formats.
acd935ef 20
5fafdf24 21@item size
eff44266
KW
22is the disk image size in bytes. Optional suffixes @code{k} or @code{K}
23(kilobyte, 1024) @code{M} (megabyte, 1024k) and @code{G} (gigabyte, 1024M)
24and T (terabyte, 1024G) are supported. @code{b} is ignored.
acd935ef
FB
25
26@item output_filename
5fafdf24 27is the destination disk image filename
acd935ef
FB
28
29@item output_fmt
30 is the destination format
eff44266
KW
31@item options
32is a comma separated list of format specific options in a
33name=value format. Use @code{-o ?} for an overview of the options supported
3e032364 34by the used format or see the format descriptions below for details.
eff44266 35
acd935ef
FB
36
37@item -c
38indicates that target image must be compressed (qcow format only)
d2c639d6
BS
39@item -h
40with or without a command shows help and lists the supported formats
41@end table
42
43Parameters to snapshot subcommand:
44
45@table @option
46
47@item snapshot
48is the name of the snapshot to create, apply or delete
49@item -a
50applies a snapshot (revert disk to saved state)
51@item -c
52creates a snapshot
53@item -d
54deletes a snapshot
55@item -l
56lists all snapshots in the given image
acd935ef
FB
57@end table
58
59Command description:
60
61@table @option
8063d0fe 62@item create [-f @var{fmt}] [-o @var{options}] @var{filename} [@var{size}]
acd935ef
FB
63
64Create the new disk image @var{filename} of size @var{size} and format
8063d0fe
KW
65@var{fmt}. Depending on the file format, you can add one or more @var{options}
66that enable additional features of this format.
acd935ef 67
8063d0fe
KW
68If the option @var{backing_file} is specified, then the image will record
69only the differences from @var{backing_file}. No size needs to be specified in
70this case. @var{backing_file} will never be modified unless you use the
71@code{commit} monitor command (or qemu-img commit).
acd935ef 72
eff44266
KW
73The size can also be specified using the @var{size} option with @code{-o},
74it doesn't need to be specified separately in this case.
75
acd935ef
FB
76@item commit [-f @var{fmt}] @var{filename}
77
78Commit the changes recorded in @var{filename} in its base image.
79
8063d0fe 80@item convert [-c] [-f @var{fmt}] [-O @var{output_fmt}] [-o @var{options}] @var{filename} [@var{filename2} [...]] @var{output_filename}
acd935ef
FB
81
82Convert the disk image @var{filename} to disk image @var{output_filename}
eff44266
KW
83using format @var{output_fmt}. It can be optionally compressed (@code{-c}
84option) or use any format specific options like encryption (@code{-o} option).
acd935ef 85
8063d0fe 86Only the formats @code{qcow} and @code{qcow2} support compression. The
acd935ef
FB
87compression is read-only. It means that if a compressed sector is
88rewritten, then it is rewritten as uncompressed data.
89
acd935ef
FB
90Image conversion is also useful to get smaller image when using a
91growable format such as @code{qcow} or @code{cow}: the empty sectors
92are detected and suppressed from the destination image.
93
8063d0fe
KW
94You can use the @var{backing_file} option to force the output image to be
95created as a copy on write image of the specified base image; the
96@var{backing_file} should have the same content as the input's base image,
97however the path, image format, etc may differ.
98
acd935ef
FB
99@item info [-f @var{fmt}] @var{filename}
100
101Give information about the disk image @var{filename}. Use it in
102particular to know the size reserved on disk which can be different
19d36792
FB
103from the displayed size. If VM snapshots are stored in the disk image,
104they are displayed too.
d2c639d6
BS
105
106@item snapshot [-l | -a @var{snapshot} | -c @var{snapshot} | -d @var{snapshot} ] @var{filename}
107
108List, apply, create or delete snapshots in image @var{filename}.
acd935ef
FB
109@end table
110
f932c040
KW
111Supported image file formats:
112
113@table @option
114@item raw
115
116Raw disk image format (default). This format has the advantage of
117being simple and easily exportable to all other emulators. If your
118file system supports @emph{holes} (for example in ext2 or ext3 on
119Linux or NTFS on Windows), then only the written sectors will reserve
120space. Use @code{qemu-img info} to know the real size used by the
121image or @code{ls -ls} on Unix/Linux.
122
123@item host_device
124
125Host device format. This format should be used instead of raw when
126converting to block devices or other devices where "holes" are not
127supported.
128
129@item qcow2
130QEMU image format, the most versatile format. Use it to have smaller
131images (useful if your filesystem does not supports holes, for example
132on Windows), optional AES encryption, zlib based compression and
133support of multiple VM snapshots.
8063d0fe 134
3e032364
KW
135Supported options:
136@table @code
137@item backing_file
138File name of a base image (see @option{create} subcommand)
139@item backing_fmt
140Image format of the base image
141@item encryption
142If this option is set to @code{on}, the image is encrypted.
143
8063d0fe
KW
144Encryption uses the AES format which is very secure (128 bit keys). Use
145a long password (16 characters) to get maximum protection.
3e032364
KW
146
147@item cluster_size
148Changes the qcow2 cluster size (must be between 512 and 2M). Smaller cluster
149sizes can improve the image file size whereas larger cluster sizes generally
150provide better performance.
151
152@item preallocation
153Preallocation mode (allowed values: off, metadata). An image with preallocated
154metadata is initially larger but can improve performance when the image needs
155to grow.
156
157@end table
158
159
f932c040
KW
160@item qcow
161Old QEMU image format. Left for compatibility.
3e032364
KW
162
163Supported options:
164@table @code
165@item backing_file
166File name of a base image (see @option{create} subcommand)
167@item encryption
168If this option is set to @code{on}, the image is encrypted.
169@end table
170
f932c040
KW
171@item cow
172User Mode Linux Copy On Write image format. Used to be the only growable
173image format in QEMU. It is supported only for compatibility with
174previous versions. It does not work on win32.
175@item vdi
176VirtualBox 1.1 compatible image format.
177@item vmdk
178VMware 3 and 4 compatible image format.
3e032364
KW
179
180Supported options:
181@table @code
182@item backing_fmt
183Image format of the base image
184@item compat6
185Create a VMDK version 6 image (instead of version 4)
186@end table
187
188@item vpc
189VirtualPC compatible image format (VHD).
190
f932c040
KW
191@item cloop
192Linux Compressed Loop image, useful only to reuse directly compressed
193CD-ROM images present for example in the Knoppix CD-ROMs.
194@end table
195
196
acd935ef
FB
197@c man end
198
199@ignore
200
201@setfilename qemu-img
202@settitle QEMU disk image utility
203
204@c man begin SEEALSO
205The HTML documentation of QEMU for more precise information and Linux
206user mode emulator invocation.
207@c man end
208
209@c man begin AUTHOR
210Fabrice Bellard
211@c man end
212
213@end ignore