How to check if AIM is running

No hypervisor responding

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:

Check your network connectivity and firewalls. See KVM troubleshooting guide#ConfigureFirewallandServices and #Default Ports

Also check that you have configured the basic AIM parameters as described below.

NFS repository file not found

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.

How to mount the Abiquo NFS repository on the KVM host

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.

1. Edit the FSTAB (# vi /etc/fstab) on the KVM hosts. Add this line with your IP address:

2. Then mount the volume using:

3. Check that it is mounted:

4. Check for a line like the following:

5. Then restart the abiquo-aim service:

6. Now try adding the KVM host in Abiquo again.

Default ports

By default the KVM host:

• Has Abiquo AIM listening at TCP port 8889 for Abiquo Remote Services communications.

• Has the Libvirt Daemon listening at TCP port 16509 for Abiquo Remote Services communications.

• Communicates with the Redis server on TCP port 6379.

See Ports and communications for detailed information

Loading AIM configuration file

By default the KVM host:

• loads the abiquo-aim.ini configuration file (/etc/abiquo-aim.ini).

Basic AIM configuration

Do the following steps:

1. Log in to the KVM server as root

2. Edit the file /etc/abiquo-aim.ini

3. Change any required parameters as described in the AIM agent page.

4. Restart the AIM service

5. You can now try adding the KVM host in Abiquo again.

Logs

Abiquo AIM writes log messages in

• stderr

• /var/log/messages

Restart Abiquo AIM

To restart the Abiquo AIM service: