Hello, The size of my qcow2 images is always reported as 1M:
IMAGE 114 INFORMATION
ID : 114
NAME : debian-wheezy
USER : nebula
GROUP : nebula
DATASTORE : default
TYPE : OS
REGISTER TIME : 04/10 10:18:26
PERSISTENT : No
SOURCE :
/var/lib/one/datastores/1/5d2be6f9746fc3447be11c6621da87df
FSTYPE : save_as
SIZE : 1M
STATE : rdy
RUNNING_VMS : 0
PERMISSIONS
OWNER : um-
GROUP : u--
OTHER : u--
IMAGE TEMPLATE
DEV_PREFIX="vd"
DRIVER="qcow2"
SAVED_DISK_ID="0"
SAVED_IMAGE_ID="17"
SAVED_VM_ID="347"
SAVE_AS="YES"
As far as I understand, the size is calculated only at creation time and
never updated.
I think we could differentiate the real size from the virtual size in
case of thin provisioning like qcow2, qemu-img actually reports:
qemu-img info /var/lib/one/datastores/1/5d2be6f9746fc3447be11c6621da87df
image: /var/lib/one/datastores/1/5d2be6f9746fc3447be11c6621da87df
file format: qcow2
virtual size: 40G (42949672960 bytes)
disk size: 629M
cluster_size: 65536
Format specific information:
compat: 1.1
lazy refcounts: false
Regards.
--
Daniel Dehennin
Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF
Fingerprint: 3E69 014E 5C23 50E8 9ED6 2AAD CC1E 9E5B 7A6F E2DF
signature.asc
Description: PGP signature
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
