Abiquo is a hypervisor-independent cloud solution that can manage multiple virtualization technologies. It is able to deploy virtual appliances to many different hypervisors, and manage them from a rich web interface. The following sections describe the template disk formats supported by the Abiquo platform, and the formats supported by the hypervisors Abiquo manages.
To retrieve the information about Supported Disk Format Types from the Abiquo API, use the requests of the DiskFormatTypes Resource
Abiquo supports the disk format types given in this table for OVF import.
Abiquo identifies the disk formats by their URIs as given in the following table. These URIs were found in OVF files exported in these formats. However, over time vendors may change their reference information and URIs. Therefore customers who wish to import OVF files should check that their file formats will be correctly identified by Abiquo.
|Disk format||URI||Technical Reference||Description|
|Device disk format|
see Stream-Optimized p11
|VMware stream optimized format|
see Simple Extents p5
|VMware fixed disk|
see Hosted Sparse Extents p6
/ ESXi Host Sparse Extents on p9
|VMware sparse disk|
|VHD specification Word file |
see Fixed Hard Disk Image p3
|VHD fixed disk|
see Dynamic Hard Disk Image p3
|VHD sparse disk|
|VHDX_FLAT||http://technet.microsoft.com/en-us/library/hh831446.aspx#monolithic_flat||VHDX fixed disk|
|VHDX_SPARSE||http://technet.microsoft.com/en-us/library/hh831446.aspx#monolithic_sparse||VHDX sparse disk|
|VDI fixed disk|
|VDI sparse disk|
|QCOW2 fixed disk|
|QCOW2 sparse disk|
Abiquo will record UNKNOWN as the format for disks that are not in one of the above formats.
The following table shows the different formats supported by the hypervisors. If you upload a template in a format not supported by your hypervisor to the Appliance Library view, Abiquo will convert it to the most suitable format.
The hypervisor default format (also called the base format) for each hypervisor is marked with a .
Change base format and formats offered
You can configure the list of formats offered and the base format using Abiquo Configuration Properties. See Abiquo Configuration Properties#pluginmetadata
Deploy VHDX templates
Deploy VHDX templates
In the above table, the hypervisor default format (also called the base format) for each hypervisor is marked with a . This is the preferred deployment format for this hypervisor, and if there is a disk in the base format, Abiquo will deploy this disk.
Abiquo converts disks from other hypervisor formats into the base format. For example, if you upload a VHD template and you have ESXi hypervisors, Abiquo will convert it into VMDK fixed format
Abiquo will not convert templates that are in other compatible formats for the same hypervisor. For example, if you upload a VMDK Sparse template for ESXi, then Abiquo will deploy the template as a VM with a sparse disk. However, if you somehow have both a sparse and a fixed format for the same disk, Abiquo will deploy the fixed format disk with thin provisioning enabled.
Abiquo will convert an Abiquo instance disk to hypervisor base format, but the administrator can control this conversion with properties. See Abiquo Configuration Properties#instance
For each hypervisor, the administrator can override the available formats and the default format using properties. See Abiquo Configuration Properties#pluginmetadata
Raw format for persistent virtual machine templates
The Disk from device or raw format is used for persistent VM templates. Before creating a persistent VM template, Abiquo converts the template's disks to raw format and then dumps them to a volume on the selected storage.
Abiquo supports ISO disks, which may be bootable installation disks (added to templates) or data disks (added to VMs). See: