Abiquo 5.2

Skip to end of metadata
Go to start of metadata

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.



Cloud Nodes

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 may require additional components to interoperate with Abiquo, for example, KVM requires the Abiquo AIM agent in each KVM host.

VMWare and Hyper-V do not require additional software to be installed.




Features Summary Table

The following table summarizes the hypervisor features of the most popular hypervisors available in the Abiquo platform.

Customers should always check the specific hypervisor features tables for further information.


 Virtualization technology
FeaturesvCenter/vSphere ESXiHyper-VKVM
 General InformationVersion

6.x, 7.x

R2+

KVM 0.12+

 Operating System or Profilen/a

Server 2012
Core 2012

CentOS 7
 VirtualizationVLAN Support for
virtualizing DHCP
(tick)-(tick)
Sub HypervisorNameESXi, vCenter Cluster--
Manager HypervisorNamevCenterHyper-V Manager-
 Direct Integration(tick)--
 Compatibility(tick)--
StorageDisk controllers

IDE, SCSI, SATA

IDE, SCSIIDE, SCSI, VIRTIO
 DatastoresAlllocal disk,
SMB
All 
External StorageiSCSI storage

(tick) with iSCSI adapter or NFS

(tick)(tick)
 LUN LimitiSCSI 256 LUNs per cluster--
 

Secondary disks
on Datastore

(tick)(tick)(tick)
Storage ResizePrimary disk resize

(tick) thin-provisioned
on
SCSI or SATA controller only,
with no VM snapshots

(tick)

(tick)
(error) VMDK sparse
(error) VHD

 Secondary disk resize

(tick) thin-provisioned
on
SCSI or SATA controller only,
with no VM snapshots

(tick)(tick)
 Volume resize(tick)(tick)(tick)
Apps LibraryPersistent virtual machines(tick)

(tick) VHD
(error) VHDX

(tick)
 Instance(tick)(tick)(tick)
MoveVM Migration(tick)(tick) set more frequent
VSM polling
(tick)
 Storage Migration(tick)(warning) with vMotion
of VM
(tick)

(tick)
(error) QEMU
HAHypervisor(tick) With vCenter(tick) Failover Clustering-
Monitoring
and Metrics
Hypervisor(tick) With vCenter(tick) 




Hypervisor integration pages



VM movement support

Abiquo supports the following hypervisor VM movement functionality. Note that target datastore must always be enabled in Abiquo for detection to work as expected.

Hypervisor

Move Technology

Notes

ESX/ESXi

vMotion

See How to make VMware vMotion work with Abiquo. Abiquo does not support vMotion between machines with different network service types

Hyper-VVM MoveAbiquo 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.

KVM

Live Migration

Not supported on virtualized hypervisors (QEMU). See How to configure KVM for live migration under Abiquo



Virtual machine templates

See Template Compatibility TableAdd VM Templates to the Apps Library and Importing Templates into the Appliance Library




Remote Access Support

Abiquo enables remote access to VMs through the eye icon. Abiquo includes the default Guacamole server for VNC, RDP, and SSH connections and it also supports WebMKS for vCloud and vCenter. The Guacamole client interface and WebMKS can be branded. Abiquo can use WebMKS with a websocket proxy. See Configure Remote Access to Virtual Machines