Admin Guide 2. Cloud Node. KVM
Changes to KVM Support in Abiquo 3.6:
The Abiquo KVM Cloud Node requires Abiquo packages. Abiquo does not support other installations of KVM.
This section will guide you through the required steps to install Abiquo KVM Cloud Node and all its dependencies using the Abiquo packages.
Abiquo recommends that you complete the following table with platform information for installing and configuring KVM. This information will help you to avoid problems with the installation or configuration of KVM in Abiquo.
IP address of AEE Server
IP address of Remote Services. Monolithic install = Abiquo Server IP, Distributed install = Remote Services IP
IP address of NFS/CIFS Server. In Distributed install, often shared with V2V Server
By default /opt/vm_repository
Host IP address
IP address of this KVM cloud node, e.g. 10.10.1.5 or DHCP
IP address of the Gateway that this cloud node will use, e.g. 10.10.1.1 or DHCP
IP address of the Primary DNS server that this cloud node use, e.g. 10.65.2.13 or DHCP
IP address of the Secondary DNS server that this cloud node use, e.g. 10.65.2.13 or DHCP
By default /
Host datastore directory
By default /var/lib/virt
Download and install the latest version of the CentOS-6.6-x86_64-minimal.iso from here: http://mirror.centos.org/centos/6/isos/x86_64/
Disable guest suspend
Abiquo recommends that you consult your organization's security expert for an appropriate firewall configuration
The Abiquo ISO disabled SELinux by default and this is the equivalent manual configuration.
The file would then look as follows.
This is the default configuration previously performed in the Abiquo ISO install.
Check if SElinux is enabled. Run the following command
If the result is "Enabled" then reboot
libvirt and qemu packages are excluded from system upgrades to maintain compatibility. Check /etc/yum.conf for details.
If you are using DHCP networking, follow the steps below to use static network addressing.
Edit interface configuration in /etc/sysconfig/network-scripts for your NIC(s). For example: /etc/sysconfig/network-scripts/ifcfg-eth1:
Then restart network service for the settings to take effect
KVM can be installed on 64-bit x86 systems including virtual machines and physical machines without virtualization extensions. To configure KVM on a machine without virtualization extensions:
Add this line in the Remote Services properties:
Restart the Abiquo Tomcat server
Create this link on the KVM node:
Restart AIM service:
If KVM is virtualized on a ESXi 5.x host, remove UUID lines from interface config files, and restart network:
This means that virtual machines will be created in KVM using PC emulation, which is performed in software and is therefore slower. PC emulation only works when KVM is installed on x86 64-bit machines, including VMs. See Abiquo Configuration Properties.
Do not use the NFS Repository as a hypervisor datastore
Do not choose the Abiquo Appliance Library directory (/opt/vm_repository by default) as the Hypervisor datastore location because this will cause performance problems
A datastore hosts the VMs and associated virtual disk files on your hypervisor. A datastore can be:
If you are using a directory on the system disk, you should not use the root directory.
When you add the hypervisor to Abiquo as a physical machine:
If you enable the datastore, Abiquo will use it in the datastore allocation process when users deploy VMs, if it is in an available Datastore tier
|Name||Local or remote absolute path. This is automatically detected by Abiquo|
Mount point for the hypervisor. This is automatically detected by Abiquo
Relative directory path added to the root path to form the datastore path. If empty, the datastore path will be only the root path. The Directory and Root Path must be consistent
|Datastore tier||Select the datastore tier to assign. Users must have access to the tiers that you assign to the datastores or they will not be able to deploy on this machine|
Size of the datastore as detected by Abiquo. Units can be MB, GB or TB
Used size of the datastore as detected by Abiquo. Units can be MB, GB or TB
If the datastore is enabled, it can be used by the datastore allocation process when you deploy VMs
The Abiquo platform uses AIM (Abiquo Infrastructure Management) to communicate with the KVM hypervisor. If Abiquo cannot communicate with AIM, Abiquo will give the following error message:
Also check that you have configured the basic AIM parameters as described below.
If you receive the following message when adding the KVM to Abiquo, it may mean that the NFS Repository Server is not mounted.
Mount the repository from the NFS Server as described below.
The NFS repository should be automatically mounted by the install script, but if there are any problems during the install, you can mount it manually.
Edit the FSTAB (# vi /etc/fstab) on the KVM hosts. Add this line with your IP address:
Then mount the volume using:
Check that it is mounted:
Check for a line like the following:
Then restart the abiquo-aim service:
By default the KVM host:
See Ports and Communications for detailed information
By default the KVM host:
Do the following steps:
Restart the AIM service
Abiquo AIM writes log messages in
To restart the Abiquo AIM service: