When working with VM templates, you will usually need to know the capacity of the VM disk files, which is the correct deployed size of the disks.
Most hypervisors require this value to launch a VM and the platform uses this value in V2V conversion to other disk formats and to export VM templates to public cloud.
To easily obtain the size that the disk will have when it is deployed, you can use qemu-img or VBoxManage as described here.
QEMU (from www.qemu.org) is available for Linux, Macintosh, and Windows.
You can use the qemu-img info command to get the details of a disk.
The capacity is the virtual size.
VirtualBox is available from https://www.virtualbox.org/wiki/Downloads.
You can use the VBoxManage showhdinfo command to obtain data about the disk image.
The capacity is the Logical Size.
Remember that not all image formats are supported using this method.
You can upload an OVA to the Abiquo platform and it will automatically enter the capacity in the VM template.
But if you upload a single disk file via the UI, then you must manually enter the capacity.
The capacity will depend on the type of disk you are using:
If you are have an OVF file to manually upload a template, it must have a correct ovf:capacity attribute. For example, here is an extract of an OVF file.
If you are uploading a single disk manually, you must enter the capacity but if you don't know the correct size at that time, you can always enter a best-guess value. Then before you create a VM, edit the VM template and enter the correct value.