Vmware Tools Guide Linux Osp - Install - Guide
Vmware Tools Guide Linux Osp - Install - Guide
EN-000329-02
VMware Tools Installation Guide Operating System Specific Packages
You can find the most up-to-date technical documentation on the VMware Web site at:
http://www.vmware.com/support/
The VMware Web site also provides the latest product updates.
If you have comments about this documentation, submit your feedback to:
[email protected]
Copyright © 2008, 2009, 2010 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright
and intellectual property laws. VMware products are covered by one or more patents listed at
http://www.vmware.com/go/patents.
VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks
and names mentioned herein may be trademarks of their respective companies.
VMware, Inc.
3401 Hillview Ave.
Palo Alto, CA 94304
www.vmware.com
2 VMware, Inc.
Contents
VMware, Inc. 3
VMware Tools Installation Guide Operating System Specific Packages
4 VMware, Inc.
About This Book
The VMware Tools Installation Guide Operating System Specific Packages provides information about how to use
the operating system specific packages (OSP) to install VMware Tools in virtual machines. OSPs are separate
downloadable VMware Tools packages. These packages are specific to each operating system. OSPs enable
individual, and operating system (OS) specific, download, installation, and upgrade of VMware Tools.
NOTE Use either the VMware Tools automatic installation and update through the VI Client, vSphere Client
or use the OSPs for individual manual installation and update. You cannot mix the two methods.
The OSPs support a specific list of Linux guest operating systems. For a current list of the guests supported by
VMware Tools OSPs, go to the online VMware Compatibility Guide:
http://www.vmware.com/resources/compatibility/search.php?action=base&deviceCategory=software
From the VMware Web site select Support and Downloads > Compatibility Guides, and click the View the
Guest/Host OS tab on the VMware Compatibility Guide Web site link
Intended Audience
This book is intended for administrators who wants to install, upgrade, or use Operating System Specific
Packages for VMware Tools. This book is for experienced Linux system administrators who are familiar with
virtual machine technology. The administrator should also be familiar with datacenter operations and
proficient with packaging and updating systems of their specific guest OS Linux distribution.
Document Feedback
VMware welcomes your suggestions for improving our documentation. If you have comments, send your
feedback to [email protected].
Customers with appropriate support contracts should use telephone support for the fastest response on
priority 1 issues. Go to http://www.vmware.com/support/phone_support.
Support Offerings
To find out how VMware support offerings can help meet your business needs, go to
http://www.vmware.com/support/services.
VMware, Inc. 5
VMware Tools Installation Guide Operating System Specific Packages
6 VMware, Inc.
1
OSPs are an alternative to the existing mechanism used to install VMware Tools through the VI Client or
vSphere™ Client. With VMware Tools OSPs you can use the native update mechanisms of your operating
system to download, install, and manage VMware Tools. OSPs enable you to manage VMware Tools from
within the guest as you would other standard software.
Decoupling: VMware Tools OSP updates are decoupled from the VMware platform. This allows you to
update to the latest version of VMware Tools without having to update to the latest version of the VMware
product. Keeping OSPs as separate downloadable packages allows for more flexibility in managing your
VMware products updates and installations. OSPs provide the option to configure the update managers
on your Linux distributions to check for updates to VMware Tools and upgrades as needed.
Standards‐compliant: VMware Tools OSPs are packaged in the native package format and follow the best
practices and standards of the supported operating systems. For example, Red Hat Enterprise Linux uses
the rpm package manager and Debian‐based distributions use the deb package standard. OSPs use the
standard mechanisms for expressing dependencies among packages, and the tools are broken in to
separate components for kernel and user space.
Availability: Because the OSPs are standards‐compliant, you can use the standard guest operating system
packaging tools to examine the OSPs. Standards‐compliant also allows you to more easily understand
how the OSPs behave while installing, upgrading, or uninstalling VMware Tools. This allows you to
determine which components you want to install and the validity of the packaging.
Go to the OSP Web site for general information and for links to downloads and support information:
http://www.vmware.com/download/packages.html
For a current list of the guests supported by VMware Tools OSPs, go to the online VMware Compatibility
Guide: http://www.vmware.com/resources/compatibility/search.php?action=base&deviceCategory=software
VMware, Inc. 7
VMware Tools Installation Guide Operating System Specific Packages
8 VMware, Inc.
2
“Prepare the Guest Operating System to Install VMware Tools OSPs” on page 11
The following system environment conditions determine which VMware Tools OSPs you install:
The packages in Table 2‐1 are listed in the order in which you must install the packages. The sequence of
package installation remains the same irrespective of the environment on which the virtual machine is
running.
NOTE The VMware open-vm-tools packages are not built based on source code from the open VMware
Tools project on sourceforge.net.
VMware, Inc. 9
VMware Tools Installation Guide Operating System Specific Packages
To use VMware Tools Operating System Specific Packages, uninstall the existing VMware Tools through the
vSphere Client. You must uninstall the existing VMware Tools to prevent package conflicts and incorrect
operation of VMware Tools.
10 VMware, Inc.
Chapter 2 Prepare for Installation
1 Log on as root.
Using a package manager – A tool provided with the operating system that performs global tasks.
zypper – SUSE Linux Enterprise Server 11 and SUSE Linux Enterprise Desktop 11
CentOS 4
OEL 4
VMware, Inc. 11
VMware Tools Installation Guide Operating System Specific Packages
Some of the packages are dependent on other packages either provided in the normal package repositories by
Red Hat, SUSE or by packages provided in the VMware repository. If dependencies are not met, you must
identify the missing packages and install them.
When installing the VMware Tools, the packages must be installed in the appropriate order for each
installation type. This order applies for all guest operating systems.
If you are using a package management tool, such as yum, apt, rug, or zypper select the configuration
appropriate for the environment and install the top level package as listed.
12 VMware, Inc.
3
“Installing VMware Tools Using OSPs on a RHEL 4 or RHEL 3 Virtual Machine” on page 15
“Installing VMware Tools Using OSPs on a SLES 11 or SLED 11 Virtual Machine” on page 18
“Installing VMware Tools Using OSPs on a CentOS 5 and OEL 5 Virtual Machine” on page 26
“Installing VMware Tools Using OSPs on a CentOS 4 or OEL 4 Virtual Machine” on page 28
Operating system supplied packages that provide mouse and display drivers for ESX and ESXi take
precedence over the same drivers supplied by the OSP packages. This assumes that the packages provided by
the operating system function as expected, and that the drivers were configured properly to manage the
display and mouse.
Sometimes the mouse and display drivers provided by the operating system do not function properly or are
not fully configured. Should this occur, download the vmware-open-vm-tools-xorg-drv-display and
vmware-open-vm-tools-xorg-drv-mouse driver packages and install them directly. You might must use a ‐
‐force option if they conflict with the packages provided by the operating system.
VMware, Inc. 13
VMware Tools Installation Guide Operating System Specific Packages
NOTE If you previously installed the most recent VMware public key, and upgraded to RHEL 5.3, this error
does not occur.
If you are experiencing this error, disable the signature check during OSP installation.
Follow the instructions for installing OSPs as outlined in the section, “Install VMware Tools for the RHEL 5
Guest Operating System” on page 15, with the following exceptions:
Add the --nogpgcheck option to every invocation of the yum install command.
For the complete list of packages to install, see “Identify the Packages to Install” on page 9.
If you have not already registered RHEL 5 on the virtual machine where you plan to install VMware Tools,
configure and register RHN (Red Hat Network).
a If it does not exist, create the directory on the virtual machine to store the key:
/<key-path>/
14 VMware, Inc.
Chapter 3 VMware Tools Installation
If it does not exist, create the directory and repository file on the virtual machine. You can choose any
name for this file, but it must use the .repo file extension. For example:
/etc/yum.repos.d/vmware-tools.repo
b Add the following contents to the file and save the file.
[vmware-tools]
name=VMware Tools for Red Hat Enterprise Linux $releasever - $basearch
baseurl=http://packages.vmware.com/tools/esx/<esx-version>/rhel5/<arch>
enabled=1
gpgcheck=1
gpgkey=file:///<key-path>/VMWARE-PACKAGING-GPG-KEY.pub
<arch> is the architecture option. For 32‐bit, this is i686. For 64‐bit, this is x86_64.
<esx-version> is replaced with either 3.5u2, 3.5u3, 3.5u4, 3.5u5, 4.0, or 4.0u1 depending upon the
ESX/ESXi version.
<key-path> is the path and directory you created when you obtained and imported the VMware
Packaging Public GPG Key in Step 5.
IMPORTANT ESX 3.5 Update 5 OSPs fail to install on a RHEL 5.4 guest with PAE.
Before you install VMware Tools, complete “Prepare the Guest Operating System to Install VMware Tools
OSPs” on page 11.
1 Run the yum command from the command line of the guest operating system:
# yum install vmware-tools
When you run this command, all the other packages are installed in the correct order.
2 (Optional) Install the VMware provided SVGA and, if needed, the mouse driver replacing the Red Hat
provided versions. The installation skips these packages if they are older than the versions included with
the Red Hat installation.
# yum install vmware-open-vm-tools-xorg-drv-display
# yum install vmware-open-vm-tools-xorg-drv-mouse
If you later uninstall VMware OSPs and want to use the Red Hat provided drivers, you must reinstall
them.
VMware, Inc. 15
VMware Tools Installation Guide Operating System Specific Packages
For the complete list of packages to install, see “Identify the Packages to Install” on page 9.
2 Obtain and import the VMware Packaging Public GPG Key from the guest operating system installed on
the virtual machine where you plan to install the OSP Tools
3 Download the OSP packages to the virtual machine where you plan to install them.
To obtain and import the VMware Packaging Public GPG Key for RHEL 4 or RHEL 3
1 If a directory does not exist, create a directory on the virtual machine to store the key:
/<key-path>/
<key-path> is the path you created to the directory on the virtual machine to store the key.
<esx-version> is replaced with either 3.5u2, 3.5u3, 3.5u4, 3.5u5, 4.0, or 4.0u1 depending upon the
ESX/ESXi version.
Go to /rhel4 or /rhel3
3 Identify the rpms required for VMware Tools installation. For example:
vmware-open-vm-tools-kmod-7.4.6-110268.130320.el4.i686.rpm
<tools-build>.<package-build> is the release build for the tools and the package. Multiple versions
might exist in the repository. Select the most recent (higher numbered)
<tools-build>.<package-build>.
16 VMware, Inc.
Chapter 3 VMware Tools Installation
<package-build> is the release build for the package. Multiple versions might exist in the repository.
Select the most recent (higher numbered) <package-build>.
<arch> is the architecture option. For 32‐bit, this is i686. For 64‐bit, this is x86_64.
4 Create a directory for the RPMS on the virtual machine where you plan to install VMware Tools.
/<vmware-tools-path>/
Install VMware Tools for the RHEL 4 or RHEL 3 Guest Operating Systems
Installing VMware Tools on a RHEL 4 or RHEL 3 virtual machine requires manually running rpm commands.
Specify the package and rug installs the required additional VMware Tools packages. For a list of packages to
install, see “Identify the Packages to Install” on page 9.
Before completing these steps, complete all steps in “Prepare the Guest Operating System to Install VMware
Tools OSPs” on page 11.
1 (Optional) Back up Red Hat provided SVGA driver from the command line of the guest operating system
virtual machine:
When this command runs, all the other packages are installed in the correct order.
CAUTION When you install the VMware Tools packages for RHEL 4 or RHEL 3, the following message
appears: Warning vmware-open-vm-tools-8.3.0-206098.el4.i686.rpm: V3 RSA/MD5 signature:
NOKEY, key ID 66fd4949.The message will vary depending upon which version of VMware Tools you have
installed. You can safely ignore this message. It has no bearing on the success of the installation.
3 (Optional) Install VMware provided SVGA and, if needed, mouse drivers replacing the Red Hat provided
versions. The installation skips these packages if they are older than the versions included with the Red
Hat installation.
If you uninstall VMware OSPs and want to use the Red Hat provided drivers, you must reinstall them.
For RHEL 4
# rpm -ivh --force
vmware-open-vm-tools-xorg-drv-display-<version>-<tools-build>.<package-build>.
<dist>.<arch>.rpm
For RHEL 3
# rpm -ivh --force
vmware-open-vm-tools-xfree86-drv-display-<version>-<tools-build>.<package-buil
d>.<dist>.<arch>.rpm
VMware, Inc. 17
VMware Tools Installation Guide Operating System Specific Packages
<tools-build>.<package-build> is the release build for the tools and the package.
<arch> is the architecture option. For 32‐bit, this is i686. For 64‐bit, this is x86_64.
For the complete list of packages to install, see “Identify the Packages to Install” on page 9.
1 Obtain and import the VMware Packaging Public GPG Key from the guest operating system of the virtual
machine where you plan to install VMware Tools.
a If it does not exist, create the directory on the virtual machine to store the key. At the command line
type:
/<key-path>/
d Import the key. Run the command appropriate for the guest operating system. For example:
# rpm --import /<key-path>/VMWARE-PACKAGING-GPG-KEY.pub
<key-path> is the path you created to the directory on the virtual machine to store the key.
All three of the preceding lines constitute the entire command needed.
<dist> is Linux distribution version. Use sles11 for both SLES11 and SLED11.
<arch> is the architecture option. For 32‐bit, this is i586. For 64‐bit, this is x86_64.
<esx-version> is replaced with either 3.5u2, 3.5u3, 3.5u4, 3.5u5, 4.0, or 4.0u1 depending upon the
ESX/ESXi version.
18 VMware, Inc.
Chapter 3 VMware Tools Installation
Before you install VMware Tools, complete the task “Prepare the Guest Operating System to Install VMware
Tools OSPs” on page 11.
Install the top level VMware Tools package, from the command line of the guest operating system virtual
machine type:
# zypper install -c vmware-tools-collection vmware-tools
When you run this command, all the other packages are automatically installed in the correct order.
CAUTION When you install the VMware Tools packages for SLES 11, the following message appears: The
following packages are not supported by their vendor: vmware-open-vm-tools
vmware-open-vm-tools-common vmware-open-vm-tools-kmod vmware-open-vm-tools-nox
vmware-open-vm-tools-xorg-utilities vmware-tools vmware-tools-common vmware-tools-nox.
The message will vary depending upon which version of VMware Tools you have installed. You can safely
ignore this message. It has not bearing on the success of the installation.
For the complete list of packages to install, see “Identify the Packages to Install” on page 9.
1 Obtain and import the VMware Packaging Public GPG Key, from the guest operating system of the virtual
machine where you plan to install VMware Tools, at the command line type.
a If it does not exist, create the directory on the virtual machine to store the key:
/<key-path>/
VMware, Inc. 19
VMware Tools Installation Guide Operating System Specific Packages
<key-path> is the path you created to the directory on the virtual machine to store the key.
<arch> is the architecture option. For 32‐bit, this is i586. For 64‐bit, this is x86_64.
<esx-version> is replaced with either 3.5u2, 3.5u3, 3.5u4, 3.5u5, 4.0, or 4.0u1 depending upon the
ESX/ESXi version.
Before you install VMware Tools, complete the task “Prepare the Guest Operating System to Install VMware
Tools OSPs” on page 11.
Install the top level VMware Tools package, from the command line of the guest operating system virtual
machine type:
# rug install -c -u vmware-tools-collection vmware-tools
# rug install -c -u vmware-tools-collection vmware-open-vm-tools-xorg-drv-display
vmware-open-vm-tools-xorg-drv-mouse
When you run this command, all the other packages are automatically installed in the correct order.
For the complete list of packages to install, see “Identify the Packages to Install” on page 9.
20 VMware, Inc.
Chapter 3 VMware Tools Installation
2 Obtain and import the VMware Packaging Public GPG Key from the guest operating system installed on
the virtual machine where you plan to install the OSP Tools.
3 Download the packages to the virtual machine where you plan to install them.
To obtain and import the VMware Packaging Public GPG Key for SLES 9
1 If a directory does not exist, create a directory on the virtual machine to store the key:
/<key-path>/
<key-path> is the path you created to the directory on the virtual machine to store the key.
2 Find the subdirectory on the guest operating system of the virtual machine where you plan to install
VMware Tools. At the command line, type:
Go to /sles9
3 Identify the rpms required for VMware Tools installation. For example:
open-vmtools-7.7.2-11588.el4.i586.rpm
<tools-build>.<package-build> is the release build for the tools and the package. Multiple versions
might exist in the repository. Select the most recent (higher numbered)
<tools-build>.<package-build>.
<package-build> is the release build for the package. Multiple versions might exist in the repository.
Select the most recent (higher numbered) <package-build>.
4 Create a directory for the RPMS on the virtual machine where you plan to install VMware Tools.
VMware, Inc. 21
VMware Tools Installation Guide Operating System Specific Packages
/<vmware-tools-path>/
IMPORTANT After installing the ESX 3.5 Update 5 OSP tools, the vmware mouse driver does not load on SLES
9 through SLES 9 SP4. The mouse can leave the window, but you need to click on the guest before you can start
using the mouse in the virtual machine.
Before you install VMware Tools, complete the task “Prepare the Guest Operating System to Install VMware
Tools OSPs” on page 11.
2 (Optional) Install VMware provided SVGA and, if needed, mouse driver replacing the SUSE provided
versions. The installation skips these packages if they are older than the versions included with the Red
Hat installation.
If you uninstall VMware OSPs and want to use the SUSE provided drivers, you must reinstall them.
<tools-build>.<package-build> is the release build for the tools and the package.
<arch> is the architecture option. For 32‐bit, this is i586. For 64‐bit, this is x86_64.
When you run this command, all the other packages are installed in the correct order.
22 VMware, Inc.
Chapter 3 VMware Tools Installation
CAUTION When you install the VMware Tools packages for SLES 9, the following message appears: Warning
“vmware-open-vm-tools-8.3.0-206098.el4.i686.rpm: V3 RSA/MD5 signature: NOKEY, key ID
66fd4949.” You can safely ignore this message. It has not bearing on the success of the installation.
For the complete list of packages to install, see “Identify the Packages to Install” on page 9.
d Import the key. Run the command appropriate for the guest operating system. For example:
$ sudo apt-key add /<key-path>/VMWARE-PACKAGING-GPG-KEY.pub
<key-path> is the path you created to the directory on the virtual machine to store the key.
2 Configure the proxy, as needed from the guest operating system on the virtual machine where you plan
to install VMware Tools.
Add the following contents to /etc/apt/apt-get conf. Create the file if needed.
ACQUIRE {http::proxy "http://[[user][:pass]@]host[:port]/"
}
For example
ACQUIRE {http::proxy "http://proxyuser:[email protected]:3128"
}
a If it does not exist, create the directory and repository file on the virtual machine. You can choose any
name for this file, but it must use the .list file extension. For example:
/etc/apt/sources.list.d/vmware-tools.list
c Add the following contents to the file and save the file.
VMware, Inc. 23
VMware Tools Installation Guide Operating System Specific Packages
The configuration syntax is specific to each operating system version. For example, replace hardy
with karmic for Ubuntu 9.10, jaunty for Ubuntu 9.04, and intrepid for Ubuntu 8.10.
<esx-version> is replaced with either 3.5u2, 3.5u3, 3.5u4, 3.5u5, 4.0, or 4.0u1 depending upon the
ESX/ESXi version.
This command lists the packages available for downloading and updates that are listed on this Web
site: http://packages.vmware.com.
If you install unsupported tools kernel modules in a virtual machine that already contains an official VMware
Tools release, the unsupported tools kernel modules overwrite the VMware modules. The Ubuntu packages
have the same name as one of the VMware Tools OSPs, and this results in a package‐name collision. The name
collision might cause issues with the Ubuntu packaging system when it attempts to install the supported
VMware Tools OSP. The Ubuntu packaging system installs the incompatible Ubuntu‐provided package
instead of the appropriate VMware Tools OSP.
Because of this collision you might be unable to install the OSPs on Ubuntu 8.10 from the repositories if the
multiverse repository is enabled. You must also avoid installing these packages if they were originally
installed using the tar installation method.
You have the open-vm-tools package from the Ubuntu multiverse repository installed on the system.
If you suspect you might have this conflict, do the following tasks as needed, to replace the conflicting
open-vm-tool package with supported versions of VMware Tools.
1 Determine whether you have the Ubuntu open-vm-tools package installed, by running the following
command.
# dpkg -s open-vm-tools | grep ^Maint
If the result states that the open-vm-tools package is not installed, or if the maintainer field, in the results
output, lists the VMware Build Team, you do not have the Ubuntu open-vm-tools package installed. You
can safely install or upgrade the OSPs.
24 VMware, Inc.
Chapter 3 VMware Tools Installation
If the maintainer field, in the results output, lists Ubuntu MOTU Develop, you have the Ubuntu package
installed and must remove it before you update the OSPs.
3 Verify that you do not have open-vm-tools installed on the system, by running the following command:
$ sudo dpkg-query -s open-vm-tools
The confirming response indicates that the package open-vm-tools is not installed and no information
is available.
NOTE This procedure is not necessary for Ubuntu 8.10 on ESX 4.0 Update 1.
2 In the Ubuntu Software tab, deselect the box Software restricted by copyright or legal issues
(multiverse).
3 Click Close.
If you enable the multiverse repository in the future, you run the risk of the original problem where
open-vm-tools packages are available from two different sources. Using the multiverse repository prevents
you from updating the OSPs when newer versions are available and causes Update Manager to warn that not
all packages could be installed, each time you open Update Manager.
This command instructs the package manager to never upgrade the open-vm-tools package.
To upgrade the open-vm-tools package when newer versions of the OSPs are available, perform the
following:
2 Disable the multiverse repository. For more information, see the section, “Disable Ubuntu Package
Management System” on page 25.
VMware, Inc. 25
VMware Tools Installation Guide Operating System Specific Packages
The advantage of using the regular VMware Tools installer is that it avoids the Ubuntu package management
system entirely. This avoids the problem introduced by an unsupported Ubuntu package and a
VMware‐supported OSP that have the same package name.
The disadvantage is that the package management system does not see the installed files. It cannot prevent
unsupported packages from being installed. This might cause an overwrite of important files by the VMware
Tools installation.
1 Make sure that the Ubuntu open-vm-tools package does not install. For more information, see the
section, “Uninstall Existing Ubuntu open‐vm‐tools Packages” on page 24.
2 Follow the VMware Tools installation instructions from your product manual.
3 Manually ensure that you do not later install the Ubuntu open-vm-tools package.
The package manager cannot prevent overwriting VMware Tools files with additional installations. A method
does not exist to prevent accidental installation of the unsupported Ubuntu packages. Disabling the multiverse
repository helps.
Before you install VMware Tools, complete “Prepare the Guest Operating System to Install VMware Tools
OSPs” on page 11.
1 Identify the kernel module for the Ubuntu operating system. For example, from the command line, type:
$ uname -r
The command returns kernel type and version. Following are the type options:
generic
server
virtual
2 Install the kernel modules for the kernel type and version. For example:
For ESX/ESXi 3.5
$ sudo apt-get install open-vm-tools-kmod-<type> vmware-tools-kmod-<type>
<type> = the value returned in Step 1.
When you run this command, all the other packages are automatically installed in the correct order.
26 VMware, Inc.
Chapter 3 VMware Tools Installation
Download OSPs for the CentOS 5 and OEL 5 Guest Operating Systems
Download all the packages for a given distribution and architecture. Download the OSPs locally to the virtual
machine where you plan to install VMware Tools. The OSPs are located on the VMware Web site at
:http://packages.vmware.com/tools. Locate the directory that corresponds to your ESX installation and the
operating system where you want to install the OSPs.
For the complete list of packages to install, see “Identify the Packages to Install” on page 9.
a If it does not exist, create the directory on the virtual machine to store the key:
/<key-path>/
a If it does not exist, create the directory and repository file on the virtual machine. You can choose any
name for this file, but it must use the .repo file extension. For example:
/etc/yum.repos.d/vmware-tools.repo
c Add the following contents to the file and save the file.
[vmware-tools]
name=VMware Tools for CentOS (or OEL) $releasever - $basearch
baseurl=http://packages.vmware.com/tools/esx/<esx-version>/<dist>/<arch>
enabled=1
gpgcheck=1
gpgkey=file:///<key-path>/VMWARE-PACKAGING-GPG-KEY.pub
<dist> is Linux distribution version. Use rhel5.CentOS 5 and OEL 5 use the RHEL 5 base.
<arch> is the architecture option. For 32‐bit, this is i686. For 64‐bit, this is x86_64.
<esx-version> is replaced with either 3.5u2, 3.5u3, 3.5u4, 3.5u5, 4.0, or 4.0u1 depending upon the
ESX/ESXi version.
<key-path> is the path and directory you created when you obtained and imported the VMware
Packaging Public GPG Key in Step 5.
VMware, Inc. 27
VMware Tools Installation Guide Operating System Specific Packages
Install VMware Tools for the CentOS 5 or OEL 5 Guest Operating System
Installing VMware Tools on a CentOS 5 or OEL 5 virtual machine uses the package management tool, yum.
Specify the package and yum installs the required additional VMware Tools packages. For a list of packages
to install, see “Identify the Packages to Install” on page 9.
Before you install VMware Tools, complete “Prepare the Guest Operating System to Install VMware Tools
OSPs” on page 11.
1 Install the top level VMware Tools package, from the command line of the guest operating system virtual
machine, type:
# yum install vmware-tools
When you run this command, all the other packages are installed in the correct order.
2 (Optional) Install VMware provided SVGA and , if needed, mouse driver replacing the CentOS provided
versions. The installation skips these packages if they are older than the versions included with the
CentOS installation.
# yum install vmware-open-vm-tools-xorg-drv-display
# yum install vmware-open-vm-tools-xorg-drv-mouse
If you later uninstall VMware OSPs and want to use the CentOS or OEL 5 provided drivers, you must
reinstall them.
For the complete list of packages to install, see “Identify the Packages to Install” on page 9.
2 Download the packages to the virtual machine where you plan to install them.
<esx-version> is replaced with either 3.5u2, 3.5u3, 3.5u4, 3.5u5, 4.0, or 4.0u1 depending upon the
ESX/ESXi version.
Go to /rhel4
CentOS 4 and OEL 4 uses the RHEL 4 base, and are in the rhel4 directory.
3 Identify the rpms required for VMware Tools installation. For example:
vmware-open-vm-tools-kmod-7.4.6-110268.130320.el4.i686.rpm
28 VMware, Inc.
Chapter 3 VMware Tools Installation
<tools-build>.<package-build> is the release build for the tools and the package. Multiple versions
might exist in the repository. Select the most recent (higher numbered)
<tools-build><package-build>.
<arch> architecture option. For 32‐bit, this is i686. For 64‐bit, this is x86_64.
4 Create a directory for the RPMS on the virtual machine where you plan to install VMware Tools.
/<vmware-tools-path>/
Install VMware Tools for the CentOS 4 or OEL 4 Guest Operating System
Installing VMware Tools on a CentOS 4 or OEL 4 virtual machine requires that you manually run the rpm
commands. Specify the package, and rug installs the required additional VMware Tools packages. For a list of
packages to install, see “Identify the Packages to Install” on page 9.
Before completing these steps, finish all steps in “Prepare the Guest Operating System to Install VMware Tools
OSPs” on page 11.
1 (Optional) Back up the CentOS or OEL provided SVGA driver from the command line of the guest
operating system virtual machine:
When you run this command, all the other packages are installed in the correct order.
3 (Optional) Install VMware provided SVGA and , if needed, mouse driver replacing the CentOS or OEL
provided versions. The automatic installation skips these packages if they are older than the versions
included with the CentOS or OEL installation.
If you uninstall OSPs and want to use the CentOS or OEL provided drivers, you must reinstall them.
# rpm -ivh --force
vmware-open-vm-tools-xorg-drv-display-<version>-<tools-build>.<package-build>.
<dist>.<arch>.rpm
<arch> architecture option. For 32‐bit, this is i686. For 64‐bit, this is x86_64.
VMware, Inc. 29
VMware Tools Installation Guide Operating System Specific Packages
Verify Installation
After installation is complete, verify that VMware Tools is installed and functioning properly.
1 Reboot the virtual machine and run the following command in the guest operating system
vmmemctl, vmci, vmmemctl, and vmxnet kernel modules are loaded in the system.
For ESX 4.0 hardware version 7 RHEL 5, SLES 10, Ubuntu 8.x, Ubuntu 9.x virtual machines
The pvscsi is mounted under /pvscsi. The marker file is under /pvscsi .
5 If you installed VMware Tools on a GUI system, restart the virtual machine GUI.
This action verifies that the new SVGA and mouse drivers or configurations are functioning.
b Click outside the virtual machine in the Windows screen and perform a task.
If the mouse driver is working correctly, you should be able to complete these tasks without using
Ctrl‐Alt to shift the mouse from one window to the next.
7 To verify the SVGA drivers, verify that you can change resolutions using one of the following methods:
System > Preferences > Screen Resolution. (Depending upon the guest.)
30 VMware, Inc.
4
Using your guest operating system package manager, search this repository for updates to each distribution.
Most package managers search for and apply the updates.
2 Review the packages for RHEL 4 and SLES 9 and check for
<version>-<tools-build>.<package-build> updates.
<tools-build>.<package-build> is the release build for the tools and the package.
3 If you identify updates, see Chapter 3, “VMware Tools Installation,” on page 13.
Check for updated packages. For the appropriate guest operating system, run the command listed:
VMware, Inc. 31
VMware Tools Installation Guide Operating System Specific Packages
To uninstall OSPs
1 Remove the OSP installations in the order listed for each package type:
# rpm -e <packagename>
If a package is not installed, the command skips the action and returns the prompt.
vmware‐tools
vmware‐tools‐nox
vmware‐tools‐common
vmware‐open‐vm‐tools
vmware‐open‐vm‐tools‐xorg‐utilities
vmware‐open‐vm‐tools‐nox
vmware‐open‐vm‐tools‐common
vmware‐open‐vm‐tools‐kmod
32 VMware, Inc.
Chapter 4 Post Installation OSP Tasks
vmware‐tools
vmware‐tools‐nox
vmware‐tools‐common
vmware‐tools‐kmod
open‐vm‐tools
open‐vm‐tools‐xorg‐utilities
open‐vm‐tools‐nox
open‐vm‐tools‐common
open‐vm‐tools‐kmod
As a part of the deinsallation, the default display and mouse drivers are reset to VESA and the system
mouse. To use a different display and mouse driver, edit your xorg configuration file.
1 Ensure that your environment meets the build dependencies, such as gcc and
kernel-source/headers/devel packages.
2 Unpack and recompile the source packages (rpm or deb) with your own kernel in to usable binary
packages.
If you do not want to install these dependencies on the target guest, use a staging host for compilation.
Customized Kernels for RHEL 3, RHEL 4, RHEL 5, SLES 9, SLES 10, SLES 11,
and SLED 11
The rpm based distributions include RHEL 4, RHEL 5, SLES 9, and SLES 10. This section describes how to
build a customized binary kernel module packages and how to install VMware Tools OSPs. This process
includes the following tasks:
ESX and ESXi 3.5 have kmod source packages. ESX/ESXi 4.0 does not require these kmod source packages.
open-vm-tools-kmod-<version>-<release>.src.rpm
vmware-tools-kmod-<version>-<release>.src.rpm
VMware, Inc. 33
VMware Tools Installation Guide Operating System Specific Packages
<esx-version> is replaced with either 3.5u2, 3.5u3, 3.5u4, 3.5u5, 4.0, or 4.0u1 depending upon your
ESX/ESXi version.
<key-path> is the path and directory you created for the key.
<tools-build>.<package-build> is the release build for the tools and the package.
<key-path> is the path and directory you created for the key.
<tools-build>.<package-build> is the release build for the tools and the package.
This step builds a binary kmod package suitable for use with the running kernel.
5 To build a binary kmod package from another kernel, pass the additional parameter to rpmbuild:
'--define "kversion 2.6.myversion"'
<arch> is the architecture option. For 32‐bit, this is i686. For 64‐bit, this is x86_64.
As with all other packages, the accompanying -debuginfo package containing debugging symbols can
be useful. The -debuginfo package is not typically installed, but it is available for installation.
34 VMware, Inc.
Chapter 4 Post Installation OSP Tasks
To build the binary kernel module packages for RHEL 4, CentOS 4, and OEL 4
For ESX/ESXi 3.5 download the two kmod source packages. ESX/ESXi 4.0 does not require the kmod source
packages.
open-vm-tools-kmod-<version>-<release>.src.rpm
vmware-tools-kmod-<version>-<release>.src.rpm
<esx-version> is replaced with either 3.5u2, 3.5u3, 3.5u4, 3.5u5, 4.0, or 4.0u1 depending upon your
ESX/ESXi version.
2 Install the kernel headers for the kernel for which you building the kernel module packages.
<key-path> is the path and directory you created for the key.
<tools-build>.<package-build> is the release build for the tools and the package.
This step builds a binary kmod package suitable for use with the running kernel.
5 To build a binary kmod package from another kernel, pass the additional parameter to rpmbuild:
'--define "kversion 2.6.myversion"'
<arch> is the architecture option. For 32‐bit, this is i686. For 64‐bit, this is x86_64.
As with all other packages, the accompanying -debuginfo package containing debugging symbols can be
useful. The -debuginfo package is not typically installed, but it is available for installation.
To build the binary kernel module packages for SLES 10, SLES 11, and SLED 11
For ESX/ESXi 3.5 download the two kmod source packages. ESX/ESXi 4.0 does not require the kmod source
packages.
open-vm-tools-kmod-<version>-<release>.src.rpm
vmware-tools-kmod-<version>-<release>.src.rpm
<esx-version> is replaced with either 3.5u2, 3.5u3, 3.5u4, 3.5u5, 4.0, or 4.0u1 depending upon your
ESX/ESXi version.
2 Install the kernel headers for the kernel module packages you plan to build.
<key-path> is the path and directory you created for the key.
VMware, Inc. 35
VMware Tools Installation Guide Operating System Specific Packages
<tools-build>.<package-build> is the release build for the tools and the package.
This step builds a binary kmod package suitable for use with the running kernel.
5 To build a binary kmod package from another kernel, pass the additional parameter to rpmbuild:
'--define "kversion 2.6.myversion"'
<arch> is the architecture option. For 32‐bit, this is i686. For 64‐bit, this is x86_64.
As with all other packages, the accompanying -debuginfo package containing debugging symbols can
be useful. The -debuginfo package is not typically installed, but it is available for installation.
For ESX/ESXi 3.5 download the two kmod source packages. ESX/ESXi 4.0 does not require the kmod source
packages.
open-vm-tools-kmod-<version>-<release>.src.rpm
vmware-tools-kmod-<version>-<release>.src.rpm
<esx-version> is replaced with either 3.5u2, 3.5u3, 3.5u4, 3.5u5, 4.0, or 4.0u1 depending upon your
ESX/ESXi version.
2 Install the kernel headers for the kernel for which you building the kernel module packages.
<key-path> is the path and directory you created for the key.
<tools-build>.<package-build> is the release build for the tools and the package.
This step builds a binary kmod package suitable for use with the running kernel.
5 To build a binary kmod package from another kernel, pass the additional parameter to rpmbuild:
'--define "kversion 2.6.myversion"'
<arch> is the architecture option. For 32‐bit, this is i686. For 64‐bit, this is x86_64.
As with all other packages, the accompanying -debuginfo package contains useful debugging symbols.
The -debuginfo package is not typically installed, but it is available for installation.
<arch> is the architecture option. For 32‐bit, this is i686. For 64‐bit, this is x86_64.
36 VMware, Inc.
Chapter 4 Post Installation OSP Tasks
VMware, Inc. 37
VMware Tools Installation Guide Operating System Specific Packages
38 VMware, Inc.