vmware-tools安装说明

1、启动并进入Linux系统。
2、然后选择虚拟机菜单中的“虚拟机/安装VMware-Tools”,此时就会有把VMware-tools文件映像到CD－ROM中。
3、把“VMwareTools-6.0.2-59824.i386.rpm，VMwareTools-6.0.2-59824.tar.gz”文件复制到自己的需要的位置中，然后选择一种安装方式。在此我选VMwareTools-6.0.2-59824.tar.gz。
4、解压
# tar -zxvf VmwareTools-6.0.2-59824.tar.gz
5、进入/home/tsm/Tools/vmware-tools-distrib目录中，
cd /home/tsm/Tools/vmware-tools-distrib
6、输入 ./vmware-install.pl进行安装，在安装过程中根据提示进行选择，在此我一路选择回车即可，周详安装过程如下：
[root@tsmpc vmware-tools-distrib]# ./vmware-install.pl，
Creating a new VMware Tools installer database using the tar4 format.
Installing VMware Tools.
In which directory do you want to install the binary files? 
[/home/tsm/software] 
What is the directory that contains the init directories (rc0.d/ to rc6.d/)? 
[/etc/rc.d] 
What is the directory that contains the init scripts? 
[/etc/rc.d/init.d] 
In which directory do you want to install the daemon files? 
[/home/tsm/sbin] 
The path "/home/tsm/sbin" does not exist currently. This program is going to 
create it, including needed parent directories. Is this what you want? 
[yes]    
In which directory do you want to install the library files? 
[/home/tsm/lib/vmware-tools] 
The path "/home/tsm/lib/vmware-tools" does not exist currently. This program is
going to create it, including needed parent directories. Is this what you want?
[yes] 
In which directory do you want to install the documentation files? 
[/home/tsm/doc/vmware-tools] 
The path "/home/tsm/doc/vmware-tools" does not exist currently. This program is
going to create it, including needed parent directories. Is this what you want?
[yes] 
The installation of VMware Tools 6.0.2 build-59824 for Linux completed 
successfully. You can decide to remove this software from your system at any 
time by invoking the following command: 
"/home/tsm/software/vmware-uninstall-tools.pl".
Before running VMware Tools for the first time, you need to configure it by 
invoking the following command: "/home/tsm/software/vmware-config-tools.pl". Do
you want this program to invoke the command for you now? [yes] 
Stopping VMware Tools services in the virtual machine:
   Guest operating system daemon:                          [确定]
Trying to find a suitable vmmemctl module for your running kernel.
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.23.1-42.fc8/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.23.1-42.fc8/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.23.1-42.fc8-i686’
  CC [M]  /tmp/vmware-config0/vmmemctl-only/os.o
  SHIPPED /tmp/vmware-config0/vmmemctl-only/vmmemctl1.o
  LD [M]  /tmp/vmware-config0/vmmemctl-only/vmmemctl.o
  Building modules, stage 2.
  MODPOST 1 modules
  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.23.1-42.fc8-i686’
cp -f vmmemctl.ko ./../vmmemctl.o
make: Leaving directory `/tmp/vmware-config0/vmmemctl-only’
The module loads perfectly in the running kernel.
Trying to find a suitable vmhgfs module for your 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.23.1-42.fc8/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.23.1-42.fc8-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/dbllnklst.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/eventManager.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/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/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/rpcin.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 1 modules
  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.23.1-42.fc8-i686’
cp -f vmhgfs.ko ./../vmhgfs.o
make: Leaving directory `/tmp/vmware-config0/vmhgfs-only’
The module loads perfectly in the running kernel.
pcnet32                31429  0 
Unloading pcnet32 module
Trying to find a suitable vmxnet module for your 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.23.1-42.fc8/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.23.1-42.fc8-i686’
  CC [M]  /tmp/vmware-config0/vmxnet-only/vmxnet.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-config0/vmxnet-only/vmxnet.mod.o
  LD [M]  /tmp/vmware-config0/vmxnet-only/vmxnet.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.23.1-42.fc8-i686’
cp -f vmxnet.ko ./../vmxnet.o
make: Leaving directory `/tmp/vmware-config0/vmxnet-only’
The module loads perfectly in the running kernel.
Trying to find a suitable vmblock module for your running kernel.
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-config0/vmblock-only’
make -C /lib/modules/2.6.23.1-42.fc8/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.23.1-42.fc8-i686’
  CC [M]  /tmp/vmware-config0/vmblock-only/linux/block.o
  CC [M]  /tmp/vmware-config0/vmblock-only/linux/control.o
  CC [M]  /tmp/vmware-config0/vmblock-only/linux/dbllnklst.o
  CC [M]  /tmp/vmware-config0/vmblock-only/linux/dentry.o
  CC [M]  /tmp/vmware-config0/vmblock-only/linux/file.o
  CC [M]  /tmp/vmware-config0/vmblock-only/linux/filesystem.o
  CC [M]  /tmp/vmware-config0/vmblock-only/linux/inode.o
  CC [M]  /tmp/vmware-config0/vmblock-only/linux/module.o
  CC [M]  /tmp/vmware-config0/vmblock-only/linux/stubs.o
  CC [M]  /tmp/vmware-config0/vmblock-only/linux/super.o
  LD [M]  /tmp/vmware-config0/vmblock-only/vmblock.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-config0/vmblock-only/vmblock.mod.o
  LD [M]  /tmp/vmware-config0/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.23.1-42.fc8-i686’
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/vmware-config0/vmblock-only’
The module loads perfectly in the running kernel.
[EXPERIMENTAL] The Virtual Machine Communication Interface (VMCI) service 
provides a new communication capability with the Host, primarily for 
development at the moment.  Would you like to enable this feature? [no] 
Detected X.org version 1.3.
No drivers for X.org version: 1.3.
Please choose one of the following display sizes that X will start with (1 - 
15):
[1]  "640x480"
[2]< "800x600"
[3]  "1024x768"
[4]  "1152x864"
[5]  "1280x800"
[6]  "1152x900"
[7]  "1280x1024"
[8]  "1376x1032"
[9]  "1400x900"
[10]  "1400x1050"
[11]  "1440x900"
[12]  "1680x1050"
[13]  "1600x1200"
[14]  "1920x1200"
[15]  "2364x1773"
Please enter a number between 1 and 15:
[2] 3
Starting VMware Tools services in the virtual machine:
   Switching to guest configuration:                       [确定]
   Guest filesystem driver:                                [确定]
   Mounting HGFS shares:                                   [失败]
   Guest memory manager:                                   [确定]
   Guest vmxnet fast network device:                       [确定]
   Blocking file system:                                   [确定]
   DMA setup:                                              [确定]
   Guest operating system daemon:                          [确定]
/etc/rc.d/init.d/vmware-tools: line 822: vmware-guestd: command not found
The configuration of VMware Tools 6.0.2 build-59824 for Linux for this running 
kernel completed successfully.
You must restart your X session before any mouse or graphics changes take 
effect.
You can now run VMware Tools by invoking the following command: 
"/home/tsm/software/vmware-toolbox" during an X server session.
To use the vmxnet driver, restart networking using the following commands: 
/etc/init.d/network stop
rmmod pcnet32
rmmod vmxnet
modprobe vmxnet
/etc/init.d/network start
To make use of the virtual printer, you will need to restart the CUPS service
Enjoy,
--the VMware team

[root@tsmpc vmware-tools-distrib]#