Configure remote access to virtual machines

How Abiquo supports remote access to VMs

To connect to a VM, click the console button on the VM control panel.

The platform opens a connection to the VM using the appropriate protocol, for example, VNC, RDP, SSH, or WebMKS.

Open

The platform's default remote access server is Apache Guacamole https://guacamole.incubator.apache.org/ , which runs on the Remote Services server. Guacamole supports VNC, RDP, and SSH connections using a single solution for all protocols. When you configure a datacenter or public cloud region, the platform automatically adds the remote service, and you can share the remote service with other datacenters or providers. 

When a user requests remote access to a VM where the environment uses VNC, SSH, or RDP:

1. The platform registers an event with the action name "VIRTUAL_MACHINE_REQUEST_ACCESS". 

2. The Abiquo Server supplies a link to the VM connection via the Guacamole server. 

3. The Abiquo UI loads the Guacamole client, which opens the remote access link. 

4. The platform requests the remote access password and/or SSH key

For VMware, Abiquo supports WebMKS.

• vCloud Director uses WebMKS only

• vCenter uses WebMKS with WebMKS proxy, as an alternative to VNC via Guacamole

• vSphere 7.0+ uses WebMKS only

Brand the Guacamole client

To brand the Guacamole client:

1. Copy the stylesheet from theme/default/css/theme_guacamole.css to your theme

2. Modify it as required

For more details, see Abiquo branding guide

Configure remote access in private cloud

The following configuration applies to private cloud and non-WebMKS access:

1. For vCenter clusters added as physical machines, optionally set properties to define how the platform should detect host IPs used for management traffic to assign host IPs for remote access. See Abiquo configuration properties#esxi. See Add VMware vCenter clusters as servers

   • com.abiquo.esxi.discovery.networkinterface.networks

   • com.abiquo.esxi.discovery.networkinterface.onlymanagementip

2. Optionally configure the port range for VNC if you would like to modify the platform default of 5900 to 65534. In general, VNC connections should use ports 5900 to 6000. VMware only recommends ports 5900 to 5964. See VMware Documentation

   • abiquo.vncport.min

   • abiquo.vncport.max

3. Optionally configure keymaps for ESXi. To set a default keymap value for the platform, Abiquo configuration properties#vnc

   • To set default ESXi keymap and pulldown values for VMs in the UI, see Configure Abiquo UI. 

   • Note that on ESXi for certain locales, when using remote access from a web client, some keystrokes do not translate. See https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2071245

Disable or enable remote access for the platform

By default, remote access is enabled for the whole platform.

To change the remote access configuration for the platform:

1. Log in to the Abiquo UI and go to Configuration → Infrastructure. 

2. Set the property to Allow remote access to virtual machines as required.

The state of remote access will change for VMs that are NOT deployed. Deployed VMs will keep their original state.

• After you disable remote access for VMs on hypervisors, users cannot access deployed VMs through the console button but the port is still enabled, so users can connect with another client.

Configure VM templates for remote access

For VM templates:

• Administrators can set a default VM user and password for SSH connections. 

• With a compatible template, users can request an initial VM password using guest setup, which will be sent to them by email or SMS. See Guest setup

Configure user accounts for remote access

To enable remote access, user accounts should have the following:

• SSH public key

• Email address

• Telephone number (cell phone)

For public cloud, users must assign the following to their VMs:

• A public IP

• A firewall that allows the appropriate type of connection for the VM (for example, SSH connections to Linux VMs and RDP connections to Windows VMs)

VM settings for remote access

• For native VM settings, see VM general information, which includes enable/disable the console button, Keymap for ESXi, and Remote access password.

• For settings for VMs captured from hypervisors, see Import and capture virtual machines.

WebMKS for vCenter

Remote access for vCenter 7 is through WebMKS only and Abiquo supports WebMKS. For earlier versions, VMs may be running VNC.

For an environment without VMs running VNC, see Install WebMKS proxy and configure WebMKS

If remote access to VMs is enabled to use VNC, you can change to use WebMKS. See Enable WebMKS for vCenter