Abiquo 5.0

Skip to end of metadata
Go to start of metadata

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.

Use qemu-img

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.

user@userpc:~/Downloads $ qemu-img info ./yVM-disk1.vmdk
image: ./yVM-disk1.vmdk
file format: vmdk
virtual size: 64M (67108864 bytes)
disk size: 14M
Format specific information:
    cid: 2107273510
    parent cid: 4294967295
    create type: streamOptimized
            compressed: true
            virtual size: 67108864
            filename: ./yVM-disk1.vmdk
            cluster size: 65536

Use VBoxManage

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.

[root@localhost]# VBoxManage showhdinfo /root/VMs/CentOS-5-5-w-LAMP.vmdk 

UUID:                 0147718f-d8b4-4c53-8c82-877ce76f1d93
Accessible:           yes
Logical size:         51200 MBytes
Current size on disk: 2881 MBytes
Type:                 normal (base)
Storage format:       VMDK
Location:             /root/VMs/CentOS-5-5-w-LAMP.vmdk 

Remember that not all image formats are supported using this method.

Enter the capacity of the VM template in the multi-cloud platform

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:

  • For fixed disk formats, the size of the deployed VM disk is the same as the physical size of the disk image.
  • For sparse and compressed formats, such as stream-optimized, it is the provisioned size.

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.

    <Info>List of the virtual disks used in the package</Info>
    <Disk ovf:capacity="734003200" ovf:diskId="vmdisk1" ovf:fileRef="file1" ...

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.

  • No labels