Qemu-img info

qemu-img info IMAGE_NAME

 $ qemu-img info test.vmdk 
 (VMDK) image open: flags=0x2 filename=test.vmdk
 image: test.vmdk
 file format: vmdk
 virtual size: 20M (20971520 bytes)
 disk size: 17M

 $ qemu-img info image-qcow.qcow2
 image: image-qcow.qcow2
 file format: qcow2
 virtual size: 10G (10737418240 bytes)
 disk size: 136K
 cluster_size: 65536

 $ qemu-img info MY_image-qcow.qcow2
 image: MY_image-qcow.qcow2
 file format: qcow2
 virtual size: 20G (21474836480 bytes)
 disk size: 7.5G
 cluster_size: 65536
 Format specific information:
    compat: 1.1
    lazy refcounts: true
    refcount bits: 16
    corrupt: false

 $ qemu-img info --backing-chain MY_image-qcow.qcow2
 image: MY_image-qcow.qcow2
 file format: qcow2
 virtual size: 20G (21474836480 bytes)
 disk size: 7.5G
 cluster_size: 65536
 Format specific information:
    compat: 1.1
    lazy refcounts: true
    refcount bits: 16
    corrupt: false

qemu-img info IMAGE.qcow2
qemu-img: Could not open 'IMAGE.qcow2': Failed to get shared "write" lock
Is another process using the image?

Notes:

• Encrypted information will be available only if the image is encrypted (The use of encryption in qcow and qcow2 images is considered to be flawed by modern cryptography standards)
• Snapshot list: A list of all internal snapshots

Related commands

• qemu-img resize
• qemu-img convert

See also

• QEMU: qemu-img, qemu-ga, qemu.conf, virsh qemu, QEMU guest agent (qemu-ga), qcow2, qemu-nbd, qemu-img map, qemu-io, /etc/libvirt/qemu.conf, QEMU releases, VENOM, qemu-nbd --help, qemu-system
• libguestfs-tools: virt-sysprep, virt-clone, virt-builder, virt-customize, virt-resize, virt-rescue, virt-sparsify, guestmount, guestfish, virt-inspector, virt-cat, virt-log, virt-df, virt-ls, virt-filesystems, virt-list-filesystems, virt-edit
• Filesystems: lazy allocation, speculative preallocation (XFS)

https://manpages.debian.org/testing/qemu-utils/qemu-img.1.en.html#OPTIONS