Abiquo Documentation Cookies Policy

Our Documentation website uses cookies to improve your experience. Please visit our Cookie Policy page for more information about cookies and how we use them.


Abiquo 4.6

Skip to end of metadata
Go to start of metadata

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.

API Feature

To retrieve the information about Supported Disk Format Types from the Abiquo API, use the requests of the DiskFormatTypes Resource

Supported Disk Format Types

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 formatURITechnical ReferenceDescription

RAW

http://raw/

 Device disk format

VMDK_STREAM_OPTIMIZED

http://www.vmware.com/technical-resources/interfaces/vmdk_access.html#streamOptimized

vmdk_50_technote.pdf
see Stream-Optimized p11
VMware stream optimized format

VMDK_FLAT

http://www.vmware.com/technical-resources/interfaces/vmdk_access.html#monolithic_flat

vmdk_50_technote.pdf
see Simple Extents p5
VMware fixed disk

VMDK_SPARSE

http://www.vmware.com/technical-resources/interfaces/vmdk_access.html#monolithic_sparse

vmdk_50_technote.pdf 
see Hosted Sparse Extents p6
/ ESXi Host Sparse Extents on p9
VMware sparse disk

VHD_FLAT

http://technet.microsoft.com/en-us/virtualserver/bb676673.aspx#monolithic_flat

VHD specification Word file
see Fixed Hard Disk Image p3
VHD fixed disk

VHD_SPARSE

http://technet.microsoft.com/en-us/virtualserver/bb676673.aspx#monolithic_sparse

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_FLAT

http://forums.virtualbox.org/viewtopic.php?t=8046#monolithic_flat

 VDI fixed disk

VDI_SPARSE

http://forums.virtualbox.org/viewtopic.php?t=8046#monolithic_sparse

 VDI sparse disk

QCOW2_FLAT

http://people.gnome.org/~markmc/qcow-image-format.html#monolithic_flat

 QCOW2 fixed disk

QCOW2_SPARSE

http://people.gnome.org/~markmc/qcow-image-format.html#monolithic_sparse

 QCOW2 sparse disk
AMI http://amiprotocol.sourceforge.net/ami-specif.html#1.9.2.user.xml  AMI
DOCKER_IMAGE https://docs.docker.com/terms/image/  Docker image
ISOhttp://iso ISO format

Abiquo will record UNKNOWN as the format for disks that are not in one of the above formats.


Hypervisor Compatibility Table

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  (star)

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

FormatAWSESX/ESXiHyper-VKVMOracle VMXenServerDocker

RAW

(error)  

(tick)

(tick)

(tick)(tick)

(error)

 

VMDK_FLAT

 

(tick) (star)

 

(tick) (star) 

 

 

VMDK_SPARSE

 

(tick)

 

  

 

 
VMDK_STREAM_OPTIMIZED (tick)     

VHD_FLAT

 

 

(tick)


 

(tick)

 

VHD_SPARSE

 

 

(tick) (star)


 

(tick) (star)

 
VHDX_FLAT  

(tick) Deploy VHDX templates
(error) No conversions TO or
FROM VHDX
(error) No persistent VHDX templates

    
VHDX _SPARSE  

(tick) Deploy VHDX templates
(error)   No conversions TO or
FROM VHDX
(error) No persistent VHDX templates

    

VDI_FLAT

 

 

 

  

 

 

VDI_SPARSE

 

 

 

  

 

 

QCOW2_FLAT

 

 

 

(tick) 

 

 

QCOW2_SPARSE

 

 

 

(tick) 

 

 
AMI

(tick)
(error) no conversions

     

 

DOCKER_IMAGE      (tick)
(error) no conversions
ISO (tick)(tick)(tick) (tick) 


Hypervisor default format and conversions

In the above table, the hypervisor default format (also called the base format) for each hypervisor is marked with a  (star). 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 

See also Appliance library concepts#Virtual-to-Virtual Conversion .

Raw format for persistent VMs

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.


Note about ISO

Abiquo supports ISO disks, which may be bootable installation disks (added to templates) or data disks (added to VMs). See: