Lines Matching refs:or
17 machine or any other process; this may destroy the image. Also, be aware that
51 *SIZE* is the disk image size in bytes. Optional suffixes ``k`` or
61 by the used format or see the format descriptions below for details.
64 'snapshot.id=[ID],snapshot.name=[NAME]' or '[ID_OR_NAME]'.
76 object type is a ``secret``, which is used to supply passwords and/or
117 With or without a command, shows help and lists the supported formats.
123 progress is reported when the process receives a ``SIGUSR1`` or
164 Strict mode - fail on different image size or sector allocation
185 but is only recommended for preallocated devices like host devices or other
191 improve performance if the data is remote, such as with NFS or iSCSI backends,
243 Is the name of the snapshot to create, apply or delete
295 AIO backends: ``threads``, ``native`` or ``io_uring``.
298 Linux, this option only works if ``-t none`` or ``-t directsync`` is
306 Perform one or more modifications of the persistent bitmap *BITMAP*
331 output in the format *OFMT* which is either ``human`` or ``json``.
337 wrong fix or hiding corruption that has already occurred.
343 Other exit codes indicate the kind of inconsistency found or if another error
363 Commit the changes recorded in *FILENAME* in its base image or backing file.
388 different format or settings.
391 *FILENAME1*) and/or ``-F`` (used for *FILENAME2*) option.
394 image contains only unallocated and/or zeroed sectors in the area after the end
398 Strict mode, it fails in case image size differs or a sector is allocated in
402 information that both images are same or the position of the first different
412 Images are identical (or requested help was printed)
424 Convert the disk image *FILENAME* or a snapshot *SNAPSHOT_PARAM*
426 be optionally compressed (``-c`` option) or use any format specific
440 unallocated or zero sectors, and the destination image will always be
457 This is only recommended for preallocated devices like host devices or other
473 *FMT*. Depending on the file format, you can add one or more *OPTIONS*
479 ``commit`` monitor command (or ``qemu-img commit``).
487 matching backing file must be created or additional options be used to make the
528 The command can output in the format *OFMT* which is either ``human`` or
597 at offset 0x50000 (327680). Data that is compressed, encrypted, or
608 false if the sectors are either unallocated or stored as optimized
619 cases where ``human`` format would omit the entry or exit with an error.
630 can be used to size logical volumes or SAN LUNs appropriately for
633 output in the format *OFMT* which is either ``human`` or ``json``.
662 data; the line is omitted if either source or destination lacks
663 bitmap support, or 0 if bitmaps are supported but there is nothing
668 List, apply, create or delete snapshots in image *FILENAME*.
709 specifying the correct new backing file, or the guest-visible
712 This mode is useful for renaming or moving the backing file to
718 disk images. This can be useful when you have copied or cloned
720 template or base image.
767 file system supports *holes* (for example in ext2 or ext3 on
768 Linux or NTFS on Windows), then only the written sectors will reserve
770 image or ``ls -ls`` on Unix/Linux.
778 for image by writing data to underlying storage. This data may or
785 on Windows), optional AES encryption, zlib or zstd based compression and
808 with the ``compress`` filter driver or backup block jobs with compression
828 poorly chosen or short passphrase will compromise the security
890 Note: this option is only valid to new or empty files. If there is
893 issue ``lsattr filename`` to check if the NOCOW flag is set or not
930 compatibility with older QEMU versions or other hypervisors,
938 images to either raw or qcow2 in order to achieve good performance.