This section describes how to install and configure hypervisors in Abiquo as cloud nodes.
Abiquo only supports hypervisors installed and configured as described in the corresponding documentation.
If you are integrating existing hypervisors, check this section to ensure they are compatible and properly configured.
Remember to consider the configuration limits of your hypervisors. Documentation is available for most hypervisors, for example, VMware Maximum Configurations.
A cloud node is a server configured in Abiquo where the virtual resources assigned to each user are deployed.
Depending on the underlying virtualization technology, the Cloud node will require additional components to interoperate with Abiquo:
Docker requires the Abiquo Pilot agent in each Docker host.
VMWare, Hyper-V and XenServer do not require additional software to be installed.
The following table summarizes the hypervisor features available in the Abiquo platform.
Customers should always check the specific hypervisor features tables for further information.
|Hyper-V R2||KVM||Oracle VM||XenServer||Docker|
|Operating System or Profile||n/a|
|CentOS 7||x86 only||n/a||Ubuntu|
|Virtualization||VLAN Support for|
|Sub Hypervisor||Name||ESXi||-||-||Oracle VM/Xen||Xen||-|
|Manager Hypervisor||Name||vCenter||Hyper-V Manager||-||OVM Manager||XenServer||-|
|IDE, SCSI||IDE, SCSI, VIRTIO||IDE, SCSI||IDE, SCSI||-|
LVM, EXT3, NFS,
|External Storage||iSCSI storage|
with iSCSI adapter or NFS
|LUN Limit||iSCSI 256 LUNs per cluster||-||-||1000 LUNs |
per Oracle VM
|Storage Resize||Primary disk resize|
|Secondary disk resize|
|Apps Library||Persistent virtual machines|
|Move||VM Migration|| set more frequent|
|Storage Migration|| with vMotion|
|HA (choose one)||Hypervisor||With vCenter||Failover Clustering||-||-|
Abiquo supports the following hypervisor VM movement functionality. Note that target datastore must always be enabled in Abiquo for detection to work as expected.
See How to make VMware vMotion work with Abiquo. Abiquo does not support vMotion between machines with different network service types
|Hyper-V||VM Move||Abiquo uses Msvm_MigrationJob to detect moved VMs. These jobs only exist for 5 minutes, so ensure the abiquo.vsm.pollingfrequency.hyperv_301 is configured to a low value. The default value of 5000 milliseconds is appropriate.|
Not supported on virtualized hypervisors (QEMU). See How to configure KVM for live migration under Abiquo
Abiquo supports the following High Availability functionality. If both Abiquo and hypervisor HA are supported, you should choose only ONE of these. Note that the shared datastore must always be enabled in Abiquo.
Abiquo enables remote access to VMs through the eye icon. Abiquo includes the default noVNC program for VNC connections. The noVNC client interface can be branded. The Abiquo noVNC installation requires the websockify proxy. See Configure Remote Access to Virtual Machines