Difference between revisions of "Qcow2"
Jump to navigation
Jump to search
↑ https://git.qemu.org/?p=qemu.git;a=blob_plain;f=docs/interop/qcow2.txt;hb=HEAD
↑ https://git.qemu.org/?p=qemu.git;a=blob_plain;f=docs/interop/qcow2.txt;hb=HEAD
↑ https://www.berrange.com/posts/2017/02/10/the-surprisingly-complicated-world-of-disk-image-sizes/
| (16 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | [[wikipedia:qcow2]]<ref>https://git.qemu.org/?p=qemu.git;a=blob_plain;f=docs/interop/qcow2.txt;hb=HEAD</ref> is a [[file format]] for [[disk image]] files used by [[QEMU]]. qcow2 support [[AES]] and multiple [[snapshots]]. | |
| + | A qcow2 image file is organized in units of constant size, which are called (host) clusters. A cluster is the unit in which all allocations are done, both for actual guest data and for image metadata.<ref>https://git.qemu.org/?p=qemu.git;a=blob_plain;f=docs/interop/qcow2.txt;hb=HEAD</ref> | ||
| − | [[qcow2]] internal [[snapshots]] are best avoided in favour of extenal snapshots. <ref>https://www.berrange.com/posts/2017/02/10/the-surprisingly-complicated-world-of-disk-image-sizes/</ref> | + | |
| + | [[qcow2]] internal [[snapshots]] are best avoided in favour of [[extenal snapshots]]. <ref>https://www.berrange.com/posts/2017/02/10/the-surprisingly-complicated-world-of-disk-image-sizes/</ref> | ||
| Line 10: | Line 12: | ||
| − | ==Related | + | ==Related terms == |
| − | * <code>[[qemu-img create]]</code> | + | * <code>[[qemu-img info]]</code>, <code>[[qemu-img create]]</code>, <code>[[qemu-img convert]]</code> |
| − | + | * [[qemu-system-x86_64]] | |
| + | * <code>[[guestmount]]</code> command to mount <code>[[qcow2]]</code> images | ||
| + | * <code>[[.raw]]</code> | ||
| + | * <code>[[.vdi]]</code> | ||
| + | * [[zlib]] | ||
| + | * <code>[[/var/lib/libvirt/images/]]</code> | ||
== See also == | == See also == | ||
| + | * {{qcow2}} | ||
* {{qemu-img}} | * {{qemu-img}} | ||
* {{KVM}} | * {{KVM}} | ||
Latest revision as of 19:14, 11 December 2023
wikipedia:qcow2[1] is a file format for disk image files used by QEMU. qcow2 support AES and multiple snapshots.
A qcow2 image file is organized in units of constant size, which are called (host) clusters. A cluster is the unit in which all allocations are done, both for actual guest data and for image metadata.[2]
qcow2 internal snapshots are best avoided in favour of extenal snapshots. [3]
Activities[edit]
- Extend LVM on qcow2 images
- Read about
rawfiles andqcow2differences: https://www.berrange.com/posts/2017/02/10/the-surprisingly-complicated-world-of-disk-image-sizes/
Related terms[edit]
qemu-img info,qemu-img create,qemu-img convert- qemu-system-x86_64
guestmountcommand to mountqcow2images.raw.vdi- zlib
/var/lib/libvirt/images/
See also[edit]
- qcow2,
qemu-img convert qemu-img:qemu-img info,qemu-img check,qemu-img resize,qemu-img create, qcow2,qemu-img rebase,qemu-img convert,qemu-img commit,qemu-img ammend- KVM, Installation, QEMU,
virsh,virtinst,libguestfs-tools, libvirt, qemu, Red Hat Virtualization (RHV), MacVTap, Virtio, oVirt, KVM services, KVM networking, KVM graphics, CPU, KVM on ARM
Advertising:
