The Virtualization feature allows Virtual Machines to be run on select Exinda appliances, allowing 3rd party operating systems and products to be installed. Once enabled, you can install any standard 32- or 64-bit x86 (Intel based) operating system onto an Exinda Virtualization Partition (EVP). Most of the virtualization configuration is performed using the "virt" CLI command. In the UI, you can see which virtual machines are configured and can power them on, off, or restart (cycle) them. You can also view the VGA console for each virtual machine.
![]() |
Note Virtualization requires an additional license before this feature can be configured and used. Please contact Exinda TAC or your local Exinda representative if you do not have this license and you wish to use this feature. The Virtualization menu will not appear if the Exinda Virtualization license has not been installed. |
---|
Figure - List of Virtual Machines providing ability to power on/off, power cycle, and launch the VGA console
The VGA console uses a Java-based applet to launch a secure SSH-based protocol to encrypt the session. You need to have Java installed and enabled as well as direct SSH access to the Exinda appliance in order to use this feature. You also need to authenticate with your username and password.
![]() |
Note This menu does not appear unless you have purchased this feature. |
---|
Only selected Exinda 60 series hardware is supported. Currently, the following hardware is available for Virtualization:
Exinda 4061
![]() |
Note Virtualization requires 8 GB of RAM or higher. You may need to purchase a RAM kit. |
---|
Configure virtualization through the CLI with the virt vm command.
These commands can be used to create virtual machines, configure CPU, storage, memory, install an operating system, etc. See CLI: Virtualization.
Click the Launch VGA Console button beside the desired virtual machine in the Virtual Machines list.
This feature creates a secure SSH connection to the Exinda appliance so that the VGA console can be viewed securely. Therefore, direct SSH access to the Exinda appliance must be available.
If the console does not appear, you may need to add the web address for the Exinda appliance to the Java Exception Site List. This is required since the Exinda appliance has a self-signed certificate for https access, which newer versions of Java are blocking.
If you are unable to log in, it may be due to an enhancement in JDK 7: "The JDK 7 release supports the Server Name Indication (SNI) extension in the JSSE client. The SNI, described in RFC 4366, enables TLS clients to connect to virtual servers." (from the Oracle support page)
If this is the case, the system pops up a java console window with an exception including:
Javax.net.ssl.SSLProtocolExceptio: handshake alert: unrecognized_name
Options for working around the JDK issue:
Set your hostname on the Exinda to the Fully Qualified Domain Name (FQDN) that will be used to access the UI and launch the VGA console.
|
|