Lines Matching +full:- +full:- +full:disable +full:- +full:linux +full:- +full:aio
5 any of the tools (like ``qemu-img``). This includes the preferred formats
10 ``qemu-img create`` and ``qemu-img convert`` using the ``-o`` option.
13 .. program:: image-formats
19 Linux or NTFS on Windows), then only the written sectors will reserve
20 space. Use ``qemu-img info`` to know the real size used by the
21 image or ``ls -ls`` on Unix/Linux.
34 .. program:: image-formats
51 zero clusters, which allow efficient copy-on-read for sparse images.
69 use to unlock the LUKS key slot is given by the ``encrypt.key-secret``
73 If this is set to ``aes``, the image is encrypted with 128-bit AES-CBC.
74 The encryption key is given by the ``encrypt.key-secret`` parameter.
78 - The AES-CBC cipher is used with predictable initialization vectors based
81 - The user passphrase is directly used as the encryption key. A poorly
83 - In the event of the passphrase being compromised there is no way to
94 .. option:: encrypt.key-secret
99 .. option:: encrypt.cipher-alg
102 to ``aes-256``. Only used when ``encrypt.format=luks``.
104 .. option:: encrypt.cipher-mode
109 .. option:: encrypt.ivgen-alg
114 .. option:: encrypt.ivgen-hash-alg
119 .. option:: encrypt.hash-alg
124 .. option:: encrypt.iter-time
149 tables must be rebuilt, i.e. on the next open an (automatic) ``qemu-img
150 check -r all`` is required, which may take some time.
164 - Disable it by mounting with nodatacow, then all newly created files
166 - For an empty file, add the NOCOW file attribute. That's what this
175 .. program:: image-formats
182 ``lazy_refcounts=on`` option to get a more QED-like behaviour.
198 Changes the cluster size (must be power-of-2 between 4K and 64K). Smaller
205 power-of-2 between 1 and 16). There is normally no need to
209 .. program:: image-formats
228 If this is set to ``aes``, the image is encrypted with 128-bit AES-CBC.
229 The encryption key is given by the ``encrypt.key-secret`` parameter.
241 .. option:: encrypt.key-secret
246 .. program:: image-formats
249 LUKS v1 encryption format, compatible with Linux dm-crypt/cryptsetup
254 .. option:: key-secret
258 .. option:: cipher-alg
261 to ``aes-256``.
263 .. option:: cipher-mode
267 .. option:: ivgen-alg
272 .. option:: ivgen-hash-alg
277 .. option:: hash-alg
282 .. option:: iter-time
287 .. program:: image-formats
300 .. program:: image-formats
330 .. program:: image-formats
343 .. program:: image-formats
346 Hyper-V compatible image format (VHDX).
362 ``qemu-img convert`` with ``subformat=dynamic``.
366 Block size; min 1 MB, max 256 MB. 0 means auto-calculate based on
373 Read-only formats
376 More disk image file formats are supported in a read-only mode.
378 .. program:: image-formats
383 .. program:: image-formats
386 Linux Compressed Loop image, useful only to reuse directly compressed
387 CD-ROM images present for example in the Knoppix CD-ROMs.
389 .. program:: image-formats
394 .. program:: image-formats
405 Linux
408 On Linux, you can directly use the host device filename instead of a
429 is better to only make READ-ONLY accesses to the hard disk otherwise
430 you may corrupt your host data (use the ``-snapshot`` command
435 controller supports zoned storage. Use ``--blockdev host_device,
436 node-name=drive0,filename=/dev/nullb0,cache.direct=on`` to pass through
456 READ-ONLY accesses to the hard disk otherwise you may corrupt your
457 host data (use the ``-snapshot`` command line so that the
475 .. parsed-literal::
477 |qemu_system| linux.img -hdb fat:/my_directory
481 them via SAMBA or NFS. The default access is *read-only*.
485 .. parsed-literal::
487 |qemu_system| linux.img -fda fat:floppy:/my_directory
492 .. parsed-literal::
494 |qemu_system| linux.img -fda fat:floppy:rw:/my_directory
498 - use non-ASCII filenames
499 - use "-snapshot" together with ":rw:"
500 - expect it to work when loadvm'ing
501 - write to the FAT directory on the host system while accessing it with the guest system
509 .. parsed-literal::
511 |qemu_system| linux.img -hdb nbd://my_nbd_server.mydomain.org:1024/
516 .. parsed-literal::
518 |qemu_system| linux.img -hdb nbd+unix://?socket=/tmp/my_socket
520 In this case, the block device must be exported using ``qemu-nbd``:
522 .. parsed-literal::
524 qemu-nbd --socket=/tmp/my_socket my_disk.qcow2
526 The use of ``qemu-nbd`` allows sharing of a disk between several guests:
528 .. parsed-literal::
530 qemu-nbd --socket=/tmp/my_socket --share=2 my_disk.qcow2
534 .. parsed-literal::
536 |qemu_system| linux1.img -hdb nbd+unix://?socket=/tmp/my_socket
537 |qemu_system| linux2.img -hdb nbd+unix://?socket=/tmp/my_socket
539 If the ``nbd-server`` uses named exports (supported since NBD 2.9.18, or with QEMU's
542 .. parsed-literal::
544 |qemu_system| -cdrom nbd://localhost/debian-500-ppc-netinst
545 |qemu_system| -cdrom nbd://localhost/openSUSE-11.1-ppc-netinst
550 .. parsed-literal::
552 |qemu_system| linux.img -hdb nbd:my_nbd_server.mydomain.org:1024
553 |qemu_system| linux2.img -hdb nbd:unix:/tmp/my_socket
554 |qemu_system| -cdrom nbd:localhost:10809:exportname=debian-500-ppc-netinst
577 iscsi://[<username>[%<password>]@]<host>[:<port>]/<target-iqn-name>/<lun>
588 iscsi://<host>/<target-iqn-name>/<lun>
591 in a configuration file provided via '-readconfig' or directly on the
594 If the initiator-name is not specified qemu will use a default name
595 of 'iqn.2008-11.org.linux-kvm[:<uuid>'] where <uuid> is the UUID of the
597 'iqn.2008-11.org.linux-kvm[:<name>'] where <name> is the name of the
604 -iscsi initiator-name=iqn.qemu.test:my-initiator
610 -iscsi header-digest=CRC32C|CRC32C-NONE|NONE-CRC32C|NONE
619 initiator-name = "iqn.qemu.test:my-initiator"
620 # header digest is one of CRC32C|CRC32C-NONE|NONE-CRC32C|NONE
621 header-digest = "CRC32C"
630 initiator-name = "iqn.qemu.test:my-initiator"
631 # header digest is one of CRC32C|CRC32C-NONE|NONE-CRC32C|NONE
632 header-digest = "CRC32C"
636 .. parsed-literal::
642 initiator-name = "iqn.qemu.test:my-initiator"
643 header-digest = "CRC32C"
646 |qemu_system| -drive file=iscsi://127.0.0.1/iqn.qemu.test/1 \\
647 -readconfig iscsi.conf
651 using the Linux STGT software target. This target is available on Red Hat based
652 systems as the package 'scsi-target-utils'.
654 .. parsed-literal::
656 tgtd --iscsi portal=127.0.0.1:3260
657 tgtadm --lld iscsi --op new --mode target --tid 1 -T iqn.qemu.test
658 tgtadm --lld iscsi --mode logicalunit --op new --tid 1 --lun 1 \\
659 -b /IMAGES/disk.img --device-type=disk
660 tgtadm --lld iscsi --mode logicalunit --op new --tid 1 --lun 2 \\
661 -b /IMAGES/cd.iso --device-type=cd
662 tgtadm --lld iscsi --op bind --mode target --tid 1 -I ALL
664 |qemu_system| -iscsi initiator-name=iqn.qemu.test:my-initiator \\
665 -boot d -drive file=iscsi://127.0.0.1/iqn.qemu.test/1 \\
666 -cdrom iscsi://127.0.0.1/iqn.qemu.test/2
677 .. parsed-literal::
679 |qemu_system| -drive file=gluster[+TYPE]://[HOST}[:PORT]]/VOLUME/PATH
684 .. parsed-literal::
714 are 0-9, with 9 being the most verbose, and 0 representing no debugging output.
716 are 0 - None, 1 - Emergency, 2 - Alert, 3 - Critical, 4 - Error, 5 - Warning,
717 6 - Notice, 7 - Info, 8 - Debug, 9 - Trace
725 .. parsed-literal::
727 qemu-img create gluster://HOST/VOLUME/PATH SIZE
731 .. parsed-literal::
733 |qemu_system| -drive file=gluster://1.2.3.4/testvol/a.img
734 |qemu_system| -drive file=gluster+tcp://1.2.3.4/testvol/a.img
735 |qemu_system| -drive file=gluster+tcp://1.2.3.4:24007/testvol/dir/a.img
736 |qemu_system| -drive file=gluster+tcp://[1:2:3:4:5:6:7:8]/testvol/dir/a.img
737 |qemu_system| -drive file=gluster+tcp://[1:2:3:4:5:6:7:8]:24007/testvol/dir/a.img
738 |qemu_system| -drive file=gluster+tcp://server.domain.com:24007/testvol/dir/a.img
739 |qemu_system| -drive file=gluster+unix:///testvol/dir/a.img?socket=/tmp/glusterd.socket
740 …|qemu_system| -drive file=gluster://1.2.3.4/testvol/a.img,file.debug=9,file.logfile=/var/log/qemu-…
744 "debug":9,"logfile":"/var/log/qemu-gluster.log",
747 |qemu_system| -drive driver=qcow2,file.driver=gluster,file.volume=testvol,file.path=/path/a.img,
748 file.debug=9,file.logfile=/var/log/qemu-gluster.log,
758 .. parsed-literal::
760 |qemu_system| -drive file=ssh://[USER@]SERVER[:PORT]/PATH[?host_key_check=HOST_KEY_CHECK]
764 .. parsed-literal::
766 …|qemu_system| -drive file.driver=ssh[,file.user=USER],file.host=SERVER[,file.port=PORT],file.path=…
774 used, but it must implement the sftp-server protocol. Most Unix/Linux
785 turns off known-hosts checking. Or you can check that the host key
803 echo $key | base64 -d | sha256sum
805 6c3aa525beda9dc83eadfbd7e5ba7d976ecb59575d1633c87cd06ed2ed6e366f -
806 12214fd9ea5b408086f98ecccd9958609bd9ac7c0ea316734006bc7818b45dc8 -
807 d36420137bcbd101209ef70c3b15dc07362fbe0fa53c5b135eba6e6afa82f0ce -
813 Currently authentication must be done using ssh-agent. Other
816 Note: Many ssh servers do not support an ``fsync``-style operation.
836 with ``-drive file=/dev/sda`` using either thread pool or linux-aio.
842 Before starting QEMU, bind the host NVMe controller to the host vfio-pci
845 .. parsed-literal::
847 # modprobe vfio-pci
848 # lspci -n -s 0000:06:0d.0
851 # echo 1102 0002 > /sys/bus/pci/drivers/vfio-pci/new_id
853 # |qemu_system| -drive file=nvme://HOST:BUS:SLOT.FUNC/NAMESPACE
857 .. parsed-literal::
859 |qemu_system| -drive file.driver=nvme,file.device=HOST:BUS:SLOT.FUNC,file.namespace=NAMESPACE
875 This feature is currently supported by the file protocol on Linux with the Open
877 locking if the POSIX host doesn't support Linux OFD locking.
886 shared virtual disk images between multiple VMs, the "share-rw" device option
891 ``-device ...,share-rw=on`` parameter can be used. This is only safe if
895 Note that share-rw=on only declares the guest's ability to share the disk.
897 to the disk image and this is unaffected by the share-rw=on option.
906 -blockdev driver=qcow2,file.filename=/path/to/image,file.locking=off,file.driver=file
920 .. program:: filter-drivers
926 useful for file-systems with slow allocation.
931 .. option:: prealloc-align
936 .. option:: prealloc-size