Oracle Technologies Blog

By ASKM

Installing VMware tools

Posted by Srikrishna Murthy Annam on September 14, 2010

When you are working with VMware linux machine, you may feel some difficulty with the cursor movement. When you move your cursor to the vmware linux machine, it takes the control of the cursor and you cant move your cursor outside the vmware linux machive. To release the cursor , you have to press CTRL+ALT. Then Vmware linux machine releases the cursor to Host operating system.

It also enhances the graphical appearance of the vmware virtual linux machine.

There are two ways , we can install VMware tools. One way is to use VMwaretools.tar.gz file and another way is to install VMwaretools.rpm and then running mware-config-tools.pl  file to install VMware tools.

Pls follow the demo to install VMware tools using xxx.tar.gz file.

The following session log shows how to install rpm and then run the mware-config-tools.pl file to install VMware tools.

[root@localhost rpms]# rpm -ivh VMwareTools-7.7.6-203138.i386.rpm
Preparing…                ########################################### [100%]
1:VMwareTools            ########################################### [100%]

The installation of VMware Tools 7.7.6 for Linux completed successfully.
You can decide to remove this software from your system at any time by
invoking the following command: “rpm -e VMwareTools”.

Before running VMware Tools for the first time, you need to
configure it for your running kernel by invoking the
following command: “/usr/bin/vmware-config-tools.pl”.

Enjoy,

–the VMware team

[root@localhost rpms]#

[root@localhost rpms]# /usr/bin/vmware-config-tools.pl

Stopping VMware Tools services in the virtual machine:
Guest operating system daemon:[  OK  ]

None of the pre-built vmmemctl modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmmemctl module
for your system (you need to have a C compiler installed on your system)?
[yes]

Using compiler “/usr/bin/gcc”. Use environment variable CC to override.

What is the location of the directory of C header files that match your running
kernel? [/lib/modules/2.6.18-164.el5xen/build/include]

Extracting the sources of the vmmemctl module.

Building the vmmemctl module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmmemctl-only’
make -C /lib/modules/2.6.18-164.el5xen/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.18-164.el5-xen-i686′
CC [M]  /tmp/vmware-config0/vmmemctl-only/backdoorGcc32.o
CC [M]  /tmp/vmware-config0/vmmemctl-only/os.o
CC [M]  /tmp/vmware-config0/vmmemctl-only/vmballoon.o
LD [M]  /tmp/vmware-config0/vmmemctl-only/vmmemctl.o
Building modules, stage 2.
MODPOST
CC      /tmp/vmware-config0/vmmemctl-only/vmmemctl.mod.o
LD [M]  /tmp/vmware-config0/vmmemctl-only/vmmemctl.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.18-164.el5-xen-i686′
cp -f vmmemctl.ko ./../vmmemctl.o
make: Leaving directory `/tmp/vmware-config0/vmmemctl-only’
The vmmemctl module loads perfectly into the running kernel.

None of the pre-built vmhgfs modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmhgfs module for
your system (you need to have a C compiler installed on your system)? [yes]

Extracting the sources of the vmhgfs module.

Building the vmhgfs module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmhgfs-only’
make -C /lib/modules/2.6.18-164.el5xen/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.18-164.el5-xen-i686′
CC [M]  /tmp/vmware-config0/vmhgfs-only/backdoor.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/backdoorGcc32.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/bdhandler.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/cpName.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/cpNameLinux.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/cpNameLite.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/dentry.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/dir.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/file.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/filesystem.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/fsutil.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/hgfsBd.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/hgfsEscapeLinux.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/hgfsUtil.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/inode.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/kernelStubsLinux.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/link.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/messageBackdoor.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/message.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/module.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/page.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/request.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/rpcout.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/staticEscape.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/stubs.o
CC [M]  /tmp/vmware-config0/vmhgfs-only/super.o
LD [M]  /tmp/vmware-config0/vmhgfs-only/vmhgfs.o
Building modules, stage 2.
MODPOST
CC      /tmp/vmware-config0/vmhgfs-only/vmhgfs.mod.o
LD [M]  /tmp/vmware-config0/vmhgfs-only/vmhgfs.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.18-164.el5-xen-i686′
cp -f vmhgfs.ko ./../vmhgfs.o
make: Leaving directory `/tmp/vmware-config0/vmhgfs-only’
The vmhgfs module loads perfectly into the running kernel.

None of the pre-built vmxnet modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmxnet module for
your system (you need to have a C compiler installed on your system)? [yes]

Extracting the sources of the vmxnet module.

Building the vmxnet module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config0/vmxnet-only’
make -C /lib/modules/2.6.18-164.el5xen/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.18-164.el5-xen-i686′
CC [M]  /tmp/vmware-config0/vmxnet-only/vmxnet.o
In file included from /tmp/vmware-config0/vmxnet-only/vmxnet.c:39:
/tmp/vmware-config0/vmxnet-only/compat_netdevice.h:273: error: redefinition of ‘struct napi_struct’
/tmp/vmware-config0/vmxnet-only/vmxnet.c: In function ‘vmxnet_probe_device’:
/tmp/vmware-config0/vmxnet-only/vmxnet.c:993: warning: cast to pointer from integer of different size
make[2]: *** [/tmp/vmware-config0/vmxnet-only/vmxnet.o] Error 1
make[1]: *** [_module_/tmp/vmware-config0/vmxnet-only] Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.18-164.el5-xen-i686′
make: *** [vmxnet.ko] Error 2
make: Leaving directory `/tmp/vmware-config0/vmxnet-only’
Unable to build the vmxnet module.

The fast network device driver (vmxnet module) is used only for our fast
networking interface. The rest of the software provided by VMware Tools is
designed to work independently of this feature.
If you wish to have the fast network driver enabled, you can install the driver
by running vmware-config-tools.pl again after making sure that gcc, binutils,
make and the kernel sources for your running kernel are installed on your
machine. These packages are available on your distribution’s installation CD.
[ Press Enter key to continue ]

None of the pre-built vmblock modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmblock module
for your system (you need to have a C compiler installed on your system)?
[yes]

Extracting the sources of the vmblock module.

Building the vmblock module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmblock-only’
make -C /lib/modules/2.6.18-164.el5xen/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.18-164.el5-xen-i686′
CC [M]  /tmp/vmware-config1/vmblock-only/linux/block.o
CC [M]  /tmp/vmware-config1/vmblock-only/linux/control.o
CC [M]  /tmp/vmware-config1/vmblock-only/linux/dbllnklst.o
CC [M]  /tmp/vmware-config1/vmblock-only/linux/dentry.o
CC [M]  /tmp/vmware-config1/vmblock-only/linux/file.o
CC [M]  /tmp/vmware-config1/vmblock-only/linux/filesystem.o
CC [M]  /tmp/vmware-config1/vmblock-only/linux/inode.o
CC [M]  /tmp/vmware-config1/vmblock-only/linux/module.o
CC [M]  /tmp/vmware-config1/vmblock-only/linux/stubs.o
CC [M]  /tmp/vmware-config1/vmblock-only/linux/super.o
LD [M]  /tmp/vmware-config1/vmblock-only/vmblock.o
Building modules, stage 2.
MODPOST
CC      /tmp/vmware-config1/vmblock-only/vmblock.mod.o
LD [M]  /tmp/vmware-config1/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.18-164.el5-xen-i686′
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/vmware-config1/vmblock-only’
The vmblock module loads perfectly into the running kernel.

[EXPERIMENTAL] The VMware FileSystem Sync Driver (vmsync) is a new feature that
creates backups of virtual machines. Please refer to the VMware Knowledge Base
for more details on this capability. Do you wish to enable this feature?
[no]

None of the pre-built vmci modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vmci module for
your system (you need to have a C compiler installed on your system)? [yes]

Extracting the sources of the vmci module.

Building the vmci module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmci-only’
make -C /lib/modules/2.6.18-164.el5xen/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.18-164.el5-xen-i686′
CC [M]  /tmp/vmware-config1/vmci-only/kernelStubsLinux.o
CC [M]  /tmp/vmware-config1/vmci-only/vmciDatagram.o
CC [M]  /tmp/vmware-config1/vmci-only/vmci_drv.o
CC [M]  /tmp/vmware-config1/vmci-only/vmciEvent.o
CC [M]  /tmp/vmware-config1/vmci-only/vmciGuestDs.o
CC [M]  /tmp/vmware-config1/vmci-only/vmciGuestKernelIf.o
CC [M]  /tmp/vmware-config1/vmci-only/vmciKernelIf.o
CC [M]  /tmp/vmware-config1/vmci-only/vmciProcess.o
CC [M]  /tmp/vmware-config1/vmci-only/vmciQueuePair.o
CC [M]  /tmp/vmware-config1/vmci-only/vmciUtil.o
LD [M]  /tmp/vmware-config1/vmci-only/vmci.o
Building modules, stage 2.
MODPOST
CC      /tmp/vmware-config1/vmci-only/vmci.mod.o
LD [M]  /tmp/vmware-config1/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.18-164.el5-xen-i686′
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/vmware-config1/vmci-only’
The vmci module loads perfectly into the running kernel.

None of the pre-built vsock modules for VMware Tools is suitable for your
running kernel.  Do you want this program to try to build the vsock module for
your system (you need to have a C compiler installed on your system)? [yes]

Extracting the sources of the vsock module.

Building the vsock module.

Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vsock-only’
make -C /lib/modules/2.6.18-164.el5xen/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.18-164.el5-xen-i686′
CC [M]  /tmp/vmware-config1/vsock-only/linux/af_vsock.o
CC [M]  /tmp/vmware-config1/vsock-only/linux/driverLog.o
CC [M]  /tmp/vmware-config1/vsock-only/linux/util.o
CC [M]  /tmp/vmware-config1/vsock-only/linux/vsockAddr.o
LD [M]  /tmp/vmware-config1/vsock-only/vsock.o
Building modules, stage 2.
MODPOST
WARNING: “VMCIDatagram_CreateHnd” [/tmp/vmware-config1/vsock-only/vsock.ko] undefined!
WARNING: “VMCIDatagram_DestroyHnd” [/tmp/vmware-config1/vsock-only/vsock.ko] undefined!
WARNING: “VMCIEvent_Subscribe” [/tmp/vmware-config1/vsock-only/vsock.ko] undefined!
WARNING: “VMCI_DeviceGet” [/tmp/vmware-config1/vsock-only/vsock.ko] undefined!
WARNING: “VMCIMemcpyFromQueueV” [/tmp/vmware-config1/vsock-only/vsock.ko] undefined!
WARNING: “VMCIQueuePair_Detach” [/tmp/vmware-config1/vsock-only/vsock.ko] undefined!
WARNING: “VMCI_GetContextID” [/tmp/vmware-config1/vsock-only/vsock.ko] undefined!
WARNING: “VMCIDatagram_Send” [/tmp/vmware-config1/vsock-only/vsock.ko] undefined!
WARNING: “VMCIQueuePair_Alloc” [/tmp/vmware-config1/vsock-only/vsock.ko] undefined!
WARNING: “VMCIEvent_Unsubscribe” [/tmp/vmware-config1/vsock-only/vsock.ko] undefined!
WARNING: “VMCIMemcpyToQueueV” [/tmp/vmware-config1/vsock-only/vsock.ko] undefined!
CC      /tmp/vmware-config1/vsock-only/vsock.mod.o
LD [M]  /tmp/vmware-config1/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.18-164.el5-xen-i686′
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/vmware-config1/vsock-only’
The vsock module loads perfectly into the running kernel.

Detected X.org version 7.1.

Please choose one of the following display sizes that X will start with (1 –
29):

[1]  “320×200”
[2]  “320×240”
[3]  “400×300”
[4]  “512×384”
[5]  “640×400”
[6]  “640×480”
[7]  “720×480”
[8]  “800×480”
[9]  “854×480”
[10]  “720×576”
[11]  “800×600”
[12]  “1024×768”
[13]  “1280×720”
[14]  “1280×768”
[15]  “1152×864”
[16]  “1280×800”
[17]  “1366×768”
[18]  “1280×960”
[19]  “1440×900”
[20]  “1280×1024”
[21]  “1400×1050”
[22]  “1680×1050”
[23]  “1600×1200”
[24]  “1920×1080”
[25]  “1920×1200”
[26]  “1920×1440”
[27]  “2048×1536”
[28]  “2560×1600”
[29]  “2560×1920”
Please enter a number between 1 and 29:

[3]

X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.

Then reboot the machine once.

Hope it helps

SRI

Advertisements

One Response to “Installing VMware tools”

  1. Thanks a million for this, I appreciate the info

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: