2.2. Oracle VDI System Requirements

2.2.1. Oracle VDI Hardware Requirements
2.2.2. Supported Installation Platforms for Oracle VDI
2.2.3. Requirements for Oracle Linux Platforms
2.2.4. Requirements for Oracle Solaris 11 Platforms
2.2.5. Requirements for Oracle Solaris 10 Platforms
2.2.6. User Requirements
2.2.7. Network Requirements
2.2.8. Time Synchronization
2.2.9. Requirements for Using a Remote MySQL Database
2.2.10. Oracle VDI Centers in Virtualized Environments
2.2.11. Sun Ray Software
2.2.12. Sun Ray Operating Software
2.2.13. Oracle Virtual Desktop Client

2.2.1. Oracle VDI Hardware Requirements

The basic hardware requirements for Oracle VDI are:

  • At least 4 gigabytes (GB) of random-access memory (RAM)

  • Quad core x86-64 (64-bit) central processing unit (CPU), with virtualization support (Intel VT-x or AMD-V)

  • At least 32 gigabytes (GB) of free disk space

  • 1 gigabit (Gbit) network interface card (NIC)

These requirements assume the host is used only for Oracle VDI.

Hardware sizing is a very important part of planning an Oracle VDI deployment. For some basic sizing guidelines, see Chapter 7, Performance and Tuning. For more detailed assistance with sizing, contact an Oracle Sales or Support representative.

2.2.2. Supported Installation Platforms for Oracle VDI

The following are the supported installation platforms for Oracle VDI:

Table 2.1. Supported Oracle VDI Installation Platforms

Operating System

Supported Releases

Oracle Linux (64-bit) on x86 platforms

5.8 and 6.3

Oracle Solaris (64-bit) on x86 platforms

Oracle Solaris 10 release 8/11 (update 10) or later

Oracle Solaris 11.1 or later


Oracle products certified on Oracle Linux are also certified and supported on Red Hat Enterprise Linux due to implicit compatibility between both distributions. Oracle does not run any additional testing on Red Hat Enterprise Linux products.

For the best performance on Oracle Linux platforms, use Oracle's Unbreakable Enterprise Kernel.

For Sun Ray Software, there are some feature differences between Oracle Linux and Oracle Solaris platforms, see Feature Differences Between Oracle Solaris and Oracle Linux Platforms in the Sun Ray Software Administration Guide for details.

All hosts in an Oracle VDI Center must use the same operating system, either Oracle Linux or Oracle Solaris. You cannot use a mixture of Oracle Linux 5 and Oracle Linux 6 hosts, or Oracle Solaris 10 and Oracle Solaris 11 hosts, in an Oracle VDI Center.

If you intend to use the single Oracle VDI host configuration model, you must also take the Oracle VM VirtualBox requirements into account, see Section 2.1.1, “Single Oracle VDI Host Configuration” and Section 4.1.2, “System Requirements for Oracle VM VirtualBox” for details.

The supported installation platforms for Oracle VDI can be virtualized, see Section 2.2.10, “Oracle VDI Centers in Virtualized Environments”.

If you use technologies for automating the installation of the operating system or for replicating hosts, such as Kickstart on Oracle Linux platforms, or Jumpstart or Flash Archives on Oracle Solaris platforms, you must ensure that each host has a unique iSCSI initiator name. See your system documentation for details on how to configure the iSCSI initiator.

2.2.3. Requirements for Oracle Linux Platforms

Oracle VDI requires that an Oracle Linux system is running in runlevel 5 (full multi-user mode with a graphical user interface).

For Oracle Linux 5 platforms, the default package set is required and must be installed on the host.

For Oracle Linux 6 platforms, the Desktop package set is required and must be installed on the host.

Oracle VDI requires specific packages to be installed. The Oracle VDI installation script checks for these packages before installing the software. If any required packages are missing, the installation script uses the yum command to check whether the packages are available. If the missing required packages are available, you are prompted to continue and the packages are downloaded and installed. If the required packages are not available, the installation fails and a list of required packages that must be installed is displayed.

Automatic software update tools can be configured to update a host to a new release of Oracle Linux when it becomes available. Updates performed in this way can result in the host being updated to a release of Oracle Linux that is not supported. You must ensure that your Oracle VDI hosts are configured to receive updates only for the supported releases of Oracle Linux.

Before you install Oracle VDI on a host:

  1. Ensure that yum is configured correctly.

    To resolve package dependencies and to receive updates only for the supported releases of Oracle Linux, see the following:

    Oracle Linux patches that fix bugs affecting Oracle VDI are only available on ULN.

  2. Update the host with the latest package versions by using the yum update command.

If the host does not have Internet access, you can configure yum to resolve package dependencies using a local source, see Section 2.2.3.3, “Resolving Package Dependencies Without Internet Access”.

SELinux must be disabled on the host. For details of how to check the SELinux status and how to disable SELinux, see Section 2.2.3.4, “Disabling SELinux”.

The firewall must be disabled on the host during installation and configuration. See Section 2.2.7, “Network Requirements” for more details.

For Oracle Linux 6 platforms, optimize the shared memory used by PulseAudio. Add the following line to the /etc/pulse/client.conf file on the host:

shm-size-bytes = 131072

See Audio Output Troubleshooting (Oracle Solaris 11 and Oracle Linux 6) in the Sun Ray Software Administration Guide for details about PulseAudio.

2.2.3.1. Required Channel Subscriptions for Oracle Unbreakable Linux Network (ULN)

Before you install Oracle VDI, ensure the host is subscribed to the required Oracle Unbreakable Linux Network (ULN) channels. For information about ULN, see Oracle Linux Unbreakable Linux Network User's Guide.

If you change your channel subscriptions, use the yum clean all command to clear the yum cache, and then use the yum repolist command to check that you have subscribed to the correct channels.

ULN Channel Subscriptions for Oracle Linux 6 Platforms

  • Unsubscribe from the following channels:

    Channel Label

    Channel Name

    ol6_x86_64_latest

    Oracle Linux 6 Latest (x86_64)

    ol6_x86_64_UEK_latest

    Latest Unbreakable Enterprise Kernel for Oracle Linux 6 (x86_64)

  • Subscribe to the following channels:

    Channel Label

    Channel Name

    ol6_u3_x86_64_patch

    Oracle Linux 6 Update 3 Patch (x86_64)

    ol6_u3_x86_64_base

    Oracle Linux 6 Update 3 installation media copy (x86_64)

    ol6_x86_64_UEK_base

    Unbreakable Enterprise Kernel for Oracle Linux 6 (x86_64)

    ol6_x86_64_gdm_multiseat

    Oracle Linux 6 GDM Multiseat

ULN Channel Subscriptions for Oracle Linux 5 Platforms

  • Unsubscribe from the following channels:

    Channel Label

    Channel Name

    el5_x86_64_latest

    Enterprise Linux 5 Latest (x86_64)

    ol5_x86_64_latest

    Oracle Linux 5 Latest (x86_64)

    ol5_x86_64_UEK_latest

    Latest Unbreakable Enterprise Kernel for Oracle Linux 5 (x86_64)

  • Subscribe to the following channels:

    Channel Label

    Channel Name

    ol5_u8_x86_64_patch

    Oracle Linux 5 Update 8 Patch (x86_64)

    ol5_u8_x86_64_base

    Oracle Linux 5 Update 8 installation media copy (x86_64)

    ol5_x86_64_UEK_base

    Unbreakable Enterprise Kernel for Oracle Linux 5 (x86_64)

2.2.3.2. Required Repository Configuration for the Oracle Public Yum Server

Before you install Oracle VDI, ensure the required repositories are configured for the Public Yum Server. For details of how to enable access to the repositories on the Public Yum Server, see http://public-yum.oracle.com. For Oracle Linux 6 platforms, see also Yum in the Oracle Linux Administrator's Solutions Guide for Release 6.

For Oracle Linux 6 platforms, you must download the latest yum configuration file (http://public-yum.oracle.com/public-yum-ol6.repo) and copy it to the /etc/yum.repos.d directory on the host. The latest yum configuration file contains entries for the required Oracle Linux 6 GDM Multiseat repository.

If you change your repository configuration, use the yum clean all command to clear the yum cache, and then use the yum repolist command to check that you have the correct repository configuration.

Repository Configuration for Oracle Linux 6 Platforms

  • Disable the following repositories:

    Repository

    Name

    [ol6_latest]

    Oracle Linux 6 Latest (x86_64)

    [ol6_UEK_latest]

    Latest Unbreakable Enterprise Kernel for Oracle Linux 6 (x86_64)

  • Enable the following repositories:

    Repository

    Name

    [ol6_u3_base]

    Oracle Linux 6 Update 3 installation media copy (x86_64)

    [ol6_UEK_base]

    Unbreakable Enterprise Kernel for Oracle Linux 6 (x86_64)

    [ol6_gdm_multiseat]

    Oracle Linux 6 GDM Multiseat (x86_64)

Repository Configuration for Oracle Linux 5 Platforms

  • Disable the following repositories:

    Repository

    Name

    [ol5_latest]

    Oracle Linux 5 Latest (x86_64)

    [ol5_UEK_latest]

    Latest Unbreakable Enterprise Kernel for Oracle Linux 5 (x86_64)

  • Enable the following repositories:

    Repository

    Name

    [ol5_u8_base]

    Oracle Linux 5 Update 8 installation media copy (x86_64)

    [ol5_UEK_base]

    Unbreakable Enterprise Kernel for Oracle Linux 5 (x86_64)

2.2.3.3. Resolving Package Dependencies Without Internet Access

If the host does not have Internet access, you can configure yum to resolve package dependencies locally using the following:

  • A local yum server.

  • A local yum repository created from an ISO image.

  • A local yum server created from an ISO image.

For details of how to configure a local yum server or repository, see Yum in the Oracle Linux Administrator's Solutions Guide for Release 6.

For Oracle Linux 6 platforms, you currently cannot use an ISO image to resolve the package dependencies because it does not contain gdm-multiseat packages.

Hosts configured to use a local yum server or repository created from an ISO image are only suitable for evaluation installments because they are not configured to receive the latest packages and security fixes.

2.2.3.4. Disabling SELinux

Use either the sestatus or the getenforce command to check the current SELinux status. If the SELinux status is Enforcing or Permissive , Oracle VDI installs correctly but configuration fails. To disable SELinux:

  1. Edit the /etc/selinux/config file and change the SELINUX setting to SELINUX=disabled.

    The setenforce command only enables you to change between Enforcing or Permissive .

  2. Reboot the host to apply the configuration change.

2.2.3.5. Checking the Status of the iSCSI daemon

The iSCSI daemon must be running on the Oracle VDI host. Use the following command to check:

# service iscsid status

If the daemon is not running, start it with the following command:

# service iscsid start

On Oracle Linux 6 platforms, if daemon fails to start, try the following command:

# service iscsid force-start

2.2.4. Requirements for Oracle Solaris 11 Platforms

Oracle VDI requires that an Oracle Solaris system is running in runlevel 3 (multi-user level with NFS resources shared).

The default Oracle Solaris 11 packages, which are provided through the solaris package publisher, are required and must be installed on the host.

Oracle VDI requires specific packages to be installed. The Oracle VDI installation script checks for these packages before installing the software. If any required packages are missing, the installation script uses the pkg command to check whether the packages are available. If the missing required packages are available, you are prompted to continue and the packages are downloaded and installed. If the required packages are not available, the installation fails and a list of required packages that must be installed is displayed. You must resolve these dependencies before you can install Oracle VDI.

Before you install Oracle VDI on a host:

  1. Ensure that the Oracle Solaris Image Packaging System (IPS) is configured to receive updates from the Oracle Solaris 11 Support Repository.

    For more details, see the Oracle Technology Network article How to Update Oracle Solaris 11 Systems From Oracle Support Repositories.

  2. Install the latest Oracle Solaris 11 Support Repository Update (SRU), using the pkg update command.

    For more details, see the Oracle Technology Network article More Tips for Updating Your Oracle Solaris 11 System from the Oracle Support Repository.

The firewall must be disabled on the host. See Section 2.2.7, “Network Requirements” for more details.

If you use Solaris zones, Oracle VDI must be installed in the global zone. Installation in a non-global zone is not supported.

To increase the performance of Sun Ray Clients, make the following configuration updates:

  1. Add the following line to the host's /etc/system file.

    set hires_tick=1

    For more information about this setting, see How to Improve Sun Ray Client Performance by Decreasing Buffering on the Network Switch (Oracle Solaris) in the Sun Ray Software Administration Guide.

  2. Add the following line to the host's /etc/system file.

    set mac:mac_cpu_binding_on=0

    For more information about this setting, see How to Improve Network Performance by Disabling CPU Binding (Oracle Solaris 11) in the Sun Ray Software Administration Guide.

  3. Reboot the host.

2.2.5. Requirements for Oracle Solaris 10 Platforms

Oracle VDI requires that an Oracle Solaris system is running in runlevel 3 (multi-user level with NFS resources shared).

The Entire Distribution software cluster is required and must be installed on the host.

Before you install Oracle VDI, the latest Recommended Patchset must be installed on the host. You can download the patchset from My Oracle Support.

The firewall must be disabled on the host. See Section 2.2.7, “Network Requirements” for more details.

If you use Solaris zones, Oracle VDI must be installed in the global zone. Installation in a non-global zone is not supported.

To increase the performance of Sun Ray Clients, make the following configuration update:

  1. Add the following line to the host's /etc/system file.

    set hires_tick=1

    For more information about this setting, see How to Improve Sun Ray Client Performance by Decreasing Buffering on the Network Switch (Oracle Solaris) in the Sun Ray Software Administration Guide.

  2. Reboot the host.

2.2.6. User Requirements

In order to install and configure Oracle VDI, you must be able to run commands as root on the host.

Typically, you use the su - root command to become superuser or to assume the root role. Alternatively, you can use the sudo command to run commands. To use the sudo command, your sudo configuration must grant running the required Oracle VDI commands as root.

2.2.7. Network Requirements

Before you install and configure Oracle VDI, disable the firewall on the host. This ensures that the required configuration can take place. After installation and configuration, you can re-enable the firewall. See Section 2.5, “Firewall Ports and Protocols” for details of the ports that might need to be opened.

You must have Domain Name System (DNS) entries for your Oracle VDI hosts. The DNS forward lookup and reverse lookup for a host must always succeed. There must be a one-to-one mapping between the forward and reverse lookup.

Always use fully-qualified DNS names for your Oracle VDI hosts. For example, vdi.example.com.

A host must have a fixed host name and a static IP address. The host cannot be a DHCP client.

Currently, Oracle VDI does not support IPv6 or IP MultiPathing (IPMP).

There are additional network requirements for Sun Ray Software, see Using a Shared Network Configuration in the Sun Ray Software Administration Guide.

2.2.8. Time Synchronization

It is important to synchronize the time on your Oracle VDI hosts. Use Network Time Protocol (NTP) software to ensure the time on all hosts is synchronized. The time difference between your hosts should be less than 30 seconds.

When you configure Oracle VDI, a check is made as to whether NTP is configured on the host. If NTP is not configured, the first host (the primary) added to the Oracle VDI Center is automatically configured as an NTP server, and the secondary hosts in the Oracle VDI Center automatically synchronize their times with the primary. If NTP is configured but the time on a host is not synchronized, a warning displays when you configure Oracle VDI.

2.2.9. Requirements for Using a Remote MySQL Database

You specify that you want to use a remote MySQL database when you configure the primary host in an Oracle VDI Center. The remote MySQL database must already be installed and configured.

The following are the supported remote databases:

  • MySQL Server, at least release 5.0, with the InnoDB storage engine.

  • MySQL Cluster, at least release 6.2.15, with the NDB storage engine.

To use the remote database, you must provide the following information when you configure Oracle VDI on a primary host:

  • The DNS name of the MySQL host.

  • The user name and password of a privileged administrator in the MySQL database.

  • The port number to use for connections to the database and whether you want to use Socket Secure Layer (SSL) to secure the connections.

The privileged database administrator is used only to create and configure an Oracle VDI database on the remote MySQL database. When the Oracle VDI database is created, a database user is also created. All access to the remote Oracle VDI database is performed through this user. By default, the name of the remote Oracle VDI database is vda and the name of the database user is vdadb. When you configure the Oracle VDI primary, you can choose different names, and choose a password to use for the database user.

To use SSL connections to the remote database, you must copy the certificate and key files needed for the SSL connection to the primary host so that they can be specified when you configure Oracle VDI. The certificates and key must be in Privacy Enhanced Mail (PEM) format. Depending on the SSL configuration of the remote database, you might need the following:

  • The Certificate Authority (CA) certificate

  • The client certificate

  • The client certificate private key

For more information about MySQL SSL configuration, refer to the chapter "MySQL Server Administration" in the MySQL Reference Manual.

2.2.10. Oracle VDI Centers in Virtualized Environments

Oracle VDI is supported, and can be installed in, an Oracle virtualized environment. If you encounter a problem when using an unsupported virtualization environment, you may be asked to demonstrate the issue on a non-virtualized operating system to ensure the problem is not related to the virtualization product.

If you plan to create an Oracle VDI Center by cloning an Oracle VDI host template, note the following:

  • Only clone an unconfigured host.

    A fully-configured Oracle VDI host template cannot be cloned. You can install the Oracle VDI software in the template, but you can only configure the host and add it to an Oracle VDI Center after it has been cloned.

    Use the -i option with the vda-install command to install the software without configuring it.

  • iSCSI initiator node names must be unique for each host.

    After cloning the template, you might have to reconfigure the iSCSI initiator name on the host, so that it is a unique name. See your system documentation for details on how to configure the iSCSI initiator.

  • High availability requires two separate hosts.

    The primary Oracle VDI host (with the master database) and the first secondary Oracle VDI host (with the replication database) can be installed in a virtualized environment. However, to provide for high availability, they must be hosted on separate physical machines.

For information on multiple Oracle VDI Centers, see Section 3.12, “About Global Oracle VDI Centers”.

2.2.11. Sun Ray Software

When you install and configure Oracle VDI, Oracle Sun Ray Software is also automatically installed and configured. You do not need to configure Sun Ray Software separately.

See also Feature Differences Between Oracle Solaris and Oracle Linux Platforms in the Sun Ray Software Administration Guide.

For the latest list of peripherals tested to work with Sun Ray Clients, see the Sun Ray Clients and Oracle Virtual Desktop Client Peripherals List at:

http://www.oracle.com/technetwork/server-storage/sunrayproducts/docs/index.html

2.2.12. Sun Ray Operating Software

Every Sun Ray Client contains a firmware module known as Sun Ray Operating Software. Updates to Sun Ray Operating Software are released periodically. The updates include support for the latest Sun Ray Software features, performance enhancements, and bug fixes.

In order to update Sun Ray Clients with the latest firmware, Sun Ray Operating Software must be downloaded separately from My Oracle Support and installed on Sun Ray servers. Both new and existing Sun Ray Clients might not contain the latest Sun Ray Operating Software and might need to be updated.

The latest Sun Ray Operating Software can be downloaded from the Sun Ray Products Download page at:

http://www.oracle.com/technetwork/server-storage/sunrayproducts/downloads/index.html

See Sun Ray Client Firmware in the Sun Ray Software Administration Guide for details of how to update the Sun Ray Operating Software on Sun Ray Clients.

For support-related questions about Sun Ray Operating Software, see knowledge document ID 1448410.1 on My Oracle Support.

2.2.13. Oracle Virtual Desktop Client

An Oracle Virtual Desktop Client is a software version of a Sun Ray Client. The Oracle Virtual Desktop Client application runs on an ordinary PC or tablet and provides a Sun Ray session in a desktop window. It is supported and can be installed on Windows, Linux, Mac OS X, iPad, and Android. An Oracle Virtual Desktop Client supports most of the standard Sun Ray Client functionality.

The Oracle Virtual Desktop Client product is not included with the Oracle VDI software. It must be downloaded separately from the Sun Ray Products Download page at:

http://www.oracle.com/technetwork/server-storage/sunrayproducts/downloads/index.html

You should ensure that you use the latest release of Oracle Virtual Desktop Client as this includes support for the latest Sun Ray Software features, performance enhancements, and bug fixes.

For detailed information about using the Oracle Virtual Desktop Client application, see: