Private cloud providers

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.

Features		vCenter/vSphere ESXi	Hyper-V	KVM
		Virtualization technology
General Information	Version	6.x, 7.x	R2+	KVM 0.12+
	Operating System or Profile	n/a	Server 2012 Core 2012	CentOS 7
Virtualization	VLAN Support for virtualizing DHCP		-
Sub Hypervisor	Name	ESXi, vCenter Cluster	-	-
Manager Hypervisor	Name	vCenter	Hyper-V Manager	-
	Direct Integration		-	-
	Compatibility		-	-
Storage	Disk controllers	IDE, SCSI, SATA	IDE, SCSI	IDE, SCSI, VIRTIO
	Datastores	All	local disk, SMB	All
External Storage	iSCSI storage	with iSCSI adapter or NFS
	LUN Limit	iSCSI 256 LUNs per cluster	-	-
	Secondary disks on Datastore
Storage Resize	Primary disk resize	thin-provisioned on SCSI or SATA controller only, with no VM snapshots		VMDK sparse VHD
	Secondary disk resize	thin-provisioned on SCSI or SATA controller only, with no VM snapshots
	Volume resize
Apps Library	Persistent virtual machines		VHD VHDX
	Instance
Move	VM Migration		set more frequent VSM polling
	Storage Migration	with vMotion of VM		QEMU
HA	Hypervisor	With vCenter	Failover Clustering	-
Monitoring and Metrics	Hypervisor	With vCenter	-

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-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.
KVM	Live Migration	Not supported on virtualized hypervisors (QEMU). See /wiki/spaces/ABI54/pages/310740129

Virtual machine templates

See Template Compatibility Table, Add 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