Lines Matching full:image
2 QEMU disk image utility
14 all image formats supported by QEMU.
17 machine or any other process; this may destroy the image. Also, be aware that
18 querying an image that is being modified by another process may encounter
46 *FILENAME* is a disk image filename.
48 *FMT* is the disk image format. It is guessed automatically in most
51 *SIZE* is the disk image size in bytes. Optional suffixes ``k`` or
55 *OUTPUT_FILENAME* is the destination disk image filename.
79 .. option:: --image-opts
85 .. option:: --target-image-opts
90 the *-n* parameter to skip image creation. This restriction may be relaxed
95 If specified, ``qemu-img`` will open the image in shared mode, allowing
97 get the image information (with 'info' subcommand) when the image is used by a
104 Will enumerate information about backing files in a disk image chain. Refer
109 Indicates that target image must be compressed (qcow/qcow2 and vmdk with
134 for ``qemu-img`` to create a sparse image during conversion. This value is
156 First image format
160 Second image format
164 Strict mode - fail on different image size or sector allocation
190 Try to use copy offloading to move data from source image to target. This may
193 allocated target image depending on the host support for getting allocation
208 Assume that reading the destination image will always return
209 zeros. This parameter is mutually exclusive with a destination image
211 parameter to skip image creation.
259 Lists all snapshots in the given image
265 .. option:: amend [--object OBJECTDEF] [--image-opts] [-p] [-q] [-f FMT] [-t CACHE] [--force] -o OP…
267 Amends the image format specific *OPTIONS* for the image file
270 The set of options that can be amended are dependent on the image
279 Run a simple sequential I/O benchmark on the specified image. If ``-w`` is
304 …[-b SOURCE_FILE [-F SOURCE_FMT]] [-g GRANULARITY] [--object OBJECTDEF] [--image-opts | -f FMT] FIL…
307 in the disk image *FILENAME*. The various modifications are:
326 To see what bitmaps are present in an image, use ``qemu-img info``.
328 .. option:: check [--object OBJECTDEF] [--image-opts] [-q] [-f FMT] [--output=OFMT] [-r [leaks | al…
330 Perform a consistency check on the disk image *FILENAME*. The command can
342 In case the image does not have any inconsistencies, check exits with ``0``.
347 Check completed, the image is (now) consistent
351 Check completed, image is corrupted
353 Check completed, image has leaked clusters, but is not corrupted
355 Checks are not supported by the image format
357 If ``-r`` is specified, exit codes representing the image state refer to the
359 will yield the exit code 0, independently of the image state before.
361 .. option:: commit [--object OBJECTDEF] [--image-opts] [-q] [-f FMT] [-t CACHE] [-b BASE] [-r RATE_…
363 Commit the changes recorded in *FILENAME* in its base image or backing file.
370 The image *FILENAME* is emptied after the operation has succeeded. If you do
374 If the backing chain of the given image file *FILENAME* has more than one
378 image (which is *FILENAME*) will be used. Note that after a commit operation
379 all images between *BASE* and the top image will be invalid and may return
381 the top image stays valid).
385 .. option:: compare [--object OBJECTDEF] [--image-opts] [-f FMT] [-F FMT] [-T SRC_CACHE] [-p] [-q] …
394 image contains only unallocated and/or zeroed sectors in the area after the end
395 of the other image. In addition, if any sector is not allocated in one image
398 Strict mode, it fails in case image size differs or a sector is allocated in
399 one image and is not allocated in the second one.
403 byte. In addition, result message can report different image size in case
416 Error on opening an image
422 .. option:: convert [--object OBJECTDEF] [--image-opts] [--target-image-opts] [--target-is-zero] [-…
424 Convert the disk image *FILENAME* or a snapshot *SNAPSHOT_PARAM*
425 to disk image *OUTPUT_FILENAME* using format *OUTPUT_FMT*. It can
433 Image conversion is also useful to get smaller image when using a
435 suppressed from the destination image.
438 that must contain only zeros for ``qemu-img`` to create a sparse image during
440 unallocated or zero sectors, and the destination image will always be
443 You can use the *BACKING_FILE* option to force the output image to be
444 created as a copy on write image of the specified base image; the
445 *BACKING_FILE* should have the same content as the input's base image,
446 however the path, image format (as given by *BACKING_FMT*), etc may differ.
472 Create the new disk image *FILENAME* of size *SIZE* and format
476 If the option *BACKING_FILE* is specified, then the image will record
486 image will be created even if the associated backing file cannot be opened. A
488 backing file specification valid when you want to use an image created this
495 .. option:: dd [--image-opts] [-U] [-f FMT] [-O OUTPUT_FMT] [bs=BLOCK_SIZE] [count=BLOCKS] [skip=BL…
506 .. option:: info [--object OBJECTDEF] [--image-opts] [-f FMT] [--output=OFMT] [--backing-chain] [-U…
508 Give information about the disk image *FILENAME*. Use it in
510 from the displayed size. If VM snapshots are stored in the disk image,
513 If a disk image has a backing file chain, information about each disk image in
516 For instance, if you have an image chain like:
522 To enumerate information about each disk image in the above chain, starting from top to base, do:
532 ``--output=human`` reports the following information (for every image in the
535 *image*
536 The image file name
539 The image format
545 How much space the image file occupies on the host file system (may be
550 Cluster size of the image format, if applicable
553 Whether the image is encrypted (only present if so)
556 This is shown as ``no`` if the image is dirty and will have to be
563 The format of the backing file, if the image enforces it
569 Further information whose structure depends on the image format. This
574 .. option:: map [--object OBJECTDEF] [--image-opts] [-f FMT] [--start-offset=OFFSET] [--max-length=…
576 Dump the metadata of image *FILENAME* and its backing file chain.
595 means that 0x20000 (131072) bytes starting at offset 0 in the image are
627 …ut=OFMT] [-O OUTPUT_FMT] [-o OPTIONS] [--size N | [--object OBJECTDEF] [--image-opts] [-f FMT] [-l…
629 Calculate the file size required for a new image. This information
631 the image that will be placed in them. The values reported are
632 guaranteed to be large enough to fit the image. The command can
636 If the size *N* is given then act as if creating a new empty image file
638 converting an existing image file using ``qemu-img convert``. The format
642 A snapshot in an existing image can be specified using *SNAPSHOT_PARAM*.
652 The ``required size`` is the file size of the new image. It may be smaller
653 than the virtual disk size if the image format supports compact representation.
655 The ``fully allocated size`` is the file size of the new image once data has
656 been written to all sectors. This is the maximum size that the image file can
658 and other advanced image format features.
661 copy bitmaps from a source image in addition to the guest-visible
666 .. option:: snapshot [--object OBJECTDEF] [--image-opts] [-U] [-q] [-l | -a SNAPSHOT | -c SNAPSHOT …
668 List, apply, create or delete snapshots in image *FILENAME*.
670 .. option:: rebase [--object OBJECTDEF] [--image-opts] [-U] [-q] [-f FMT] [-t CACHE] [-T SRC_CACHE]…
672 Changes the backing file of an image. Only the formats ``qcow2`` and
675 The backing file is changed to *BACKING_FILE* and (if the image format of
678 string), then the image is rebased onto no backing file (i.e. it will exist
699 the entire *FILENAME* image) are compressed when written.
702 converting an image. It only works if the old backing file still
710 content of the image will be corrupted.
714 file, i.e. you can use it to fix an image whose backing file has
719 a guest, and you want to get back to a thin image on top of a
720 template or base image.
725 image called ``diff.qcow2`` that contains just the differences, do:
735 .. option:: resize [--object OBJECTDEF] [--image-opts] [-f FMT] [--preallocation=PREALLOC] [-q] [--…
737 Change the disk image as if it had been created with *SIZE*.
739 Before using this command to shrink a disk image, you MUST use file system and
745 image's end.
747 After using this command to grow a disk image, you must use file system and
751 When growing an image, the ``--preallocation`` option may be used to specify
752 how the additional image area should be allocated on the host. See the format
761 Supported image file formats:
765 Raw disk image format (default). This format has the advantage of
770 image or ``ls -ls`` on Unix/Linux.
776 ``full``). ``falloc`` mode preallocates space for image by
778 for image by writing data to underlying storage. This data may or
783 QEMU image format, the most versatile format. Use it to have smaller
792 traditional image format that can be read by any QEMU since 0.10.
793 ``compat=1.1`` enables image format extensions that only QEMU 1.1 and
798 File name of a base image (see ``create`` subcommand)
801 Image format of the base image
805 compressed clusters on the image. Note that setting this option doesn't yet
806 cause the image to actually receive compressed writes. It is most commonly
815 If this option is set to ``on``, the image is encrypted with
840 sector. When a disk image has multiple internal snapshots this
855 2M). Smaller cluster sizes can improve the image file size whereas
860 ``falloc``, ``full``). An image with preallocated metadata is
861 initially larger but can improve performance when the image needs
880 Btrfs has low performance when hosting a VM image file, even more
898 the qcow2 file will only contain the image's metadata.
908 file consistent as a standalone read-only raw image.
913 offset in the raw data file. This results in a read-only raw image. Writes
916 raw image.
929 QEMU also supports various other image file formats for
936 The main purpose of the block drivers for these formats is image