Ensure that the following capabilities exist on the KVM hypervisor and the unit on which it is hosted before you attempt to automatically deploy LoadMasters to KVM:

  1. The host server on which KVM is running must have login through the SSH protocol enabled so that the KVM user specified as part of the credentials for a Target Environment on Kemp 360 Central can securely communicate with the KVM host server. See the documentation for your host operating system for instructions on enabling SSH.
  2. Public key authentication is used to authenticate Kemp 360 Central to the KVM host over SSH, so Kemp 360 Central's public key must be added to the list of Authorized Keys in the KVM user profile for the user login specified as part of the credentials for a Target Environment on Kemp 360 Central. When you deploy a LoadMaster to KVM, or when you create a KVM Target Environment, Kemp 360 Central's public key is displayed as part of the user interface (as shown in the procedure below). See the KVM documentation for information on adding the Kemp 360 Central public key as an authorized key to a KVM user profile.
  3. The KVM user that is specified in the login credentials for a Target Environment on Kemp 360 Central must have the proper permission to communicate with the libvirtd daemon running on the KVM hypervisor. Generally, on a Linux system, you would add this user to the libvirtd group. See the KVM documentation and the documentation for your host operating system for instructions on how to give this user permission to communicate with the libvirtd daemon.
  4. The netcat software must be installed on the KVM host server. See the documentation for your host operating system for instructions on installing software packages.