5.1. Oracle VDI Hypervisor

5.1.1. About the Oracle VDI Hypervisor
5.1.2. System Requirements for the Oracle VDI Hypervisor
5.1.3. Updating the Oracle VDI Hypervisor
5.1.4. How to Install the Oracle VDI Hypervisor
5.1.5. How to Configure the VRDP Port Range

5.1.1. About the Oracle VDI Hypervisor

Oracle VDI bundles and supports a specific Oracle VM VirtualBox release, which is referred to as the Oracle VDI Hypervisor. See Section 5.1.2, “System Requirements for the Oracle VDI Hypervisor”.

The Oracle VDI Hypervisor provides the following Oracle VDI desktop provider features.

Shared Memory

Shared Memory (also known as memory ballooning) is a feature that enables more desktops to run on Oracle VDI Hypervisor hosts. By specifying an amount of memory to be shared between desktops, the Oracle VDI hypervisor host's memory can be automatically redistributed between desktops as required. The Shared Memory feature can be activated on a per-pool basis on the Pool category, Settings tab by specifying a value greater than 0% (up to 75%).

The memory sharing percentage is the amount of memory that can be used for other desktops if a desktop does not require the full amount of memory for itself. For instance, if the desktop memory size is 1 GB and memory sharing is set to 40%, the desktop will initially have around 600 MB of real memory. The other 400 MB will be made available to the desktop on demand.

Oracle VDI constantly monitors desktops with memory sharing enabled to ensure they don't run out of memory. If a desktop's free memory drops below 64 MB more usable memory will be provided. If a desktop has excessive amounts of free memory, some memory will be gradually taken away until the memory sharing percentage is reached. The changes to desktop memory will not be apparent to the guest OS.

Memory Paging

Memory Paging (also known as de-duplication of memory) is a feature that enables more desktops to run on Oracle VDI Hypervisor hosts. If several desktops have identical content in memory, pages will be used to consume real memory on the hypervisor only once. The desktops will reference the page and do not need physical memory for identical pages any more.

The Memory Paging feature can be activated on a per-pool basis on the Pool category, Settings tab.

5.1.2. System Requirements for the Oracle VDI Hypervisor

Oracle VDI includes release 4.0.10 of Oracle VM VirtualBox. For reasons of backward compatibility, you can continue to use some releases Oracle VM VirtualBox that were included in previous releases of Oracle VDI. In this release, the following are the only supported releases of Oracle VM VirtualBox:

  • Oracle VM VirtualBox 4.0.10

  • Oracle VM VirtualBox 3.2.12

To obtain the best performance, it is best to install and use the Oracle VDI Hypervisor that is bundled with this release.

The following are the supported installation platforms for the bundled Oracle VDI Hypervisor:

Operating System

Supported Releases

Oracle Linux (64-bit) on x86 platforms

5.6

Oracle Solaris (64-bit) on x86 platforms

Solaris 10 release 10/09 (update 8) or later

Note: Solaris 11 is not supported.

All Oracle VDI Hypervisor hosts must have the virtualization extensions from AMD (AMD-V) and Intel (VT-x) enabled.

Customers can use new or existing hardware as long as the CPU it meets the x86 CPU requirements.

If the firewall is enabled on the Oracle VDI Hypervisor hosts, the following ports must be opened:

  • Port 22 for SSH connections

  • Port 443 for HTTPS connections

  • Ports 49152 to 65534 for VRDP connections

The HTTPS ports is configurable when you install the Oracle VDI Hypervisor. The VRDP ports are only required if the VRDP protocol is used to connect to desktops. See Section 6.1.7, “Choosing Between VRDP and MS-RDP” for details. The range of ports used is configurable, see Section 5.1.5, “How to Configure the VRDP Port Range” for details.

5.1.2.1. System Requirements for the Oracle VDI Hypervisor on Oracle Solaris Platforms

On Solaris platforms, you must install the Entire distribution to get the libraries required by Oracle VDI. The Oracle VDI Hypervisor installation script warns you if zfs_arc_min is not set. The recommended setting for a dedicated Oracle VDI Hypervisor host is 512 MB.

To set 512 MB as the zfs_arc_min, log in as root and add the following in /etc/system:

set zfs:zfs_arc_min = 536870912

On Oracle Solaris platforms, the Oracle VDI Hypervisor requires specific packages to be installed in order to function correctly. The following are the required packages:

  • SUNWapch2r

  • SUNWapch2u

  • SUNWapch2d

To check if a package is installed on the host, run the following command as root:

# pkginfo -x <package-name>

5.1.2.2. System Requirements for the Oracle VDI Hypervisor on Linux Platforms

On Oracle Linux platforms, the Oracle VDI Hypervisor requires specific packages to be installed in order to function correctly. The following are the required packages:

  • distcache.i386 (32-bit version)

  • distcache.x86_64 (64-bit version)

  • gcc

  • glibc-devel

  • glibc-headers

  • httpd

  • kernel-devel or kernel-uek-devel (depending on the Linux kernel)

  • kernel-headers or kernel-uek-headers (depending on the Linux kernel)

  • libgomp

  • mod_ssl

  • SDL

To check if a package is installed on the host, run the following command as root:

# rpm -q <package-name>

To install a required package, run the following command as root:

# yum install <package-name>

5.1.2.3. Storage Requirements for the Oracle VDI Hypervisor

The Oracle VDI Hypervisor requires a storage server to store the virtual machines used by Oracle VDI. This server is in addition to the Oracle VDI Hypervisor host itself.

See Section 5.6.1, “Supported Storage Server Platforms” for details of what is supported.

For detailed instructions on storage preparation, see:

5.1.3. Updating the Oracle VDI Hypervisor

You update the Oracle VDI Hypervisor by installing the new release bundled with an Oracle VDI release. When you update, the existing Oracle VDI Hypervisor must first be uninstalled. When you install the new release, the installation script prompts you to uninstall existing release. Alternatively, you can uninstall the existing release manually with the vb-install -u command.

When you uninstall the Oracle VDI Hypervisor, you are prompted to shut down any virtual machines that are running. You must shut down all running virtual machines before uninstalling. You are also prompted to unregister and delete the virtual machines. If you choose to unregister and delete, you cannot register the virtual machines again after the update.

After updating the Oracle VDI Hypervisor, you must update the guest additions in all templates and desktops.

5.1.4. How to Install the Oracle VDI Hypervisor

This section describes how to install the release of Oracle VM VirtualBox that is bundled with Oracle VDI.

Before you begin, check that the host meets the installation requirements, see Section 5.1.2, “System Requirements for the Oracle VDI Hypervisor”.

If you are updating an Oracle VDI Hypervisor, see Section 5.1.3, “Updating the Oracle VDI Hypervisor”.

About the Oracle VDI Hypervisor Installation Script

The Oracle VDI Hypervisor is installed and uninstalled with the vb-install script. In Oracle VDI release 3.3, the installation process has changed for legal reasons. The Oracle VDI Hypervisor is delivered as two packages, an open source package (the Base Pack) and an Oracle proprietary package (the Extension Pack).

The Oracle VDI software archive only includes the Extension Pack. When you run the vb-install script, the script automatically downloads the Base Pack using the wget program. If this fails, for example due to network connectivity problems, the script exits and you must manually download the Base Pack. It might take as long as ten minutes for the script to exit. You can download the Base Pack and the Extension Pack from the Oracle VDI download page.

When you install the Oracle VDI Hypervisor, you are prompted for a user name, a password, and a port number to use for SSL connections. The user name and password are for the user that runs the hypervisor on the host. By default, the root user is used. The Oracle VDI Hypervisor has the facility for suspending and resuming virtual machines and running the hypervisor as root is the easiest way to guarantee that the suspend and resume functionality works. If you use a different user, the user must have a home directory and the home directory must not be shared between several systems that run Oracle VM VirtualBox. By default, port 443 is used, but you can choose a different port.

The following table lists the parameters that can be used with vb-install script to automate the installation on several servers with a script.

Parameter

Description

-f

Forces existing virtual machines to be deleted.

-n <user>

Specifies the user name of the Oracle VM VirtualBox user.

-o <port>

Specifies the SSL port to use to connect to Oracle VM VirtualBox. The default is port 443.

-p

Requires input from standard input (stdin) to enter the password in a secure way.

-u

Uninstalls the currently installed release of Oracle VM VirtualBox.

Steps

  1. Log in as root on the virtualization host.

  2. Download the main Oracle VDI software archive.

  3. Unzip the main Oracle VDI software archive and change working directory to the extracted directory.

    • On Oracle Solaris hosts:

      # unzip vda_3.3_solaris_amd64.zip
      # cd vda_3.3_solaris_amd64
    • On Oracle Linux hosts:

      # unzip vda_3.3_linux.zip
      # cd vda_3.3_linux
  4. Unzip the Oracle VM VirtualBox archive and change working directory to the extracted directory.

    # unzip vbox_4.0.zip
    # cd vbox_4.0
  5. Install Oracle VM VirtualBox.

    # ./vb-install

    The installation script downloads the Oracle VM VirtualBox Base Pack, and then installs both the Base Pack and the Extension Pack. After you accept the software license agreement, you complete the installation by providing a user name, a password, and a port number to use for SSL connections.

    If the Base Pack download fails, you must manually download it from the Oracle VDI download page. Make sure you download the release that is bundled and supported with this release of Oracle VDI. Copy the Base Pack to the same folder as the vb-install script, and then run the script again.

5.1.5. How to Configure the VRDP Port Range

If the VRDP protocol is selected as the desktop protocol, Oracle VDI makes connections to Oracle VDI Hypervisor hosts on a range of ports between 49152 to 65534. Use the vda settings-setprops command to configure the VRDP port range.

  • Run the following command as root.

    #  /opt/SUNWvda/sbin/vda settings-setprops -p \
    vbox.rdp.port.range="<StartPort>-<EndPort>"
    

    For example:

    #  /opt/SUNWvda/sbin/vda settings-setprops -p \
    vbox.rdp.port.range="50000-60000"