Linux系统下如何安装VMware_tools

·  主  机：VMWare--Fedora 9

·  编译器：arm-linux-gcc-4.3.2

==================================================================================

#mount -t iso9660 /dev/cdrom /mnt/

会看到有Vmwaretools的.rpm和.tar.gz的包

#cp /mnt/vmware*.tar.gz /tmp/

#umount /dev/cdrom

#cd /tmp

/#tar zxf Vmware*.tar.gz

/#cd vmware-tools-distrib

/#./vmware-install.pl

 

In which directory do you want to install the binary files?

[/usr/bin]

 

What is the directory that contains the init directories (rc0.d/ to rc6.d/)?

[/etc]

 

What is the directory that contains the init scripts?

[/etc/init.d]

 

In which directory do you want to install the daemon files?

[/usr/sbin]

 

In which directory do you want to install the library files?

[/usr/lib/vmware-tools]

 

The path "/usr/lib/vmware-tools" does not exist currently. This program isgoing to create it, including needed parent directories. Is this what you want?

[yes]

 

In which directory do you want to install the documentation files?

[/usr/share/doc/vmware-tools]

 

The path "/usr/share/doc/vmware-tools" does not exist currently. This programis going to create it, including needed parent directories. Is this what youwant?

[yes]

 

The installation of VMware Tools 6.0.0 build-45731 for Linux completedsuccessfully. You can decide to remove this software from your system at anytime by invoking the following command: "/usr/bin/vmware-uninstall-tools.pl".

 

Before running VMware Tools for the first time, you need to configure it byinvoking the following command: "/usr/bin/vmware-config-tools.pl". Do you wantthis program to invoke the command for you now?

[yes] no

 

Enjoy,

 

--the VMware team

 

debian:/tmp/vmware-tools-distrib# /usr/bin/vmware-config-tools.pl

 

Stopping VMware Tools services in the virtual machine:

   Guest operating system daemon:                                      done

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?

[/usr/src/linux/include]

 

The path "/usr/src/linux/include" is not an existing directory.

 

What is the location of the directory of C header files that match your running

kernel? [/usr/src/linux/include]

/usr/src/linux-headers-2.6.17-2-686/include        

(如果此处没有内核目录，先安装kernel-devel)

 

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 /usr/src/linux-headers-2.6.17-2-686/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/linux-headers-2.6.17-2-686'

  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

  CC      /tmp/vmware-config0/vmmemctl-only/vmmemctl.mod.o

  LD [M]  /tmp/vmware-config0/vmmemctl-only/vmmemctl.ko

make[1]: Leaving directory `/usr/src/linux-headers-2.6.17-2-686'

cp -f vmmemctl.ko ./../vmmemctl.o

make: Leaving directory `/tmp/vmware-config0/vmmemctl-only'

The module loads perfectly in the running kernel.

 

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 /usr/src/linux-headers-2.6.17-2-686/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/linux-headers-2.6.17-2-686'

  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

  CC      /tmp/vmware-config0/vmhgfs-only/vmhgfs.mod.o

  LD [M]  /tmp/vmware-config0/vmhgfs-only/vmhgfs.ko

make[1]: Leaving directory `/usr/src/linux-headers-2.6.17-2-686'

cp -f vmhgfs.ko ./../vmhgfs.o

make: Leaving directory `/tmp/vmware-config0/vmhgfs-only'

The module loads perfectly in the running kernel.

 

pcnet32                28420  0

Unloading pcnet32 module

 

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 /usr/src/linux-headers-2.6.17-2-686/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/linux-headers-2.6.17-2-686'

  CC [M]  /tmp/vmware-config0/vmxnet-only/vmxnet.o

  Building modules, stage 2.

  MODPOST

  CC      /tmp/vmware-config0/vmxnet-only/vmxnet.mod.o

  LD [M]  /tmp/vmware-config0/vmxnet-only/vmxnet.ko

make[1]: Leaving directory `/usr/src/linux-headers-2.6.17-2-686'

cp -f vmxnet.ko ./../vmxnet.o

make: Leaving directory `/tmp/vmware-config0/vmxnet-only'

The module loads perfectly in the running kernel.

 

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 /usr/src/linux-headers-2.6.17-2-686/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/linux-headers-2.6.17-2-686'

  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

  CC      /tmp/vmware-config0/vmblock-only/vmblock.mod.o

  LD [M]  /tmp/vmware-config0/vmblock-only/vmblock.ko

make[1]: Leaving directory `/usr/src/linux-headers-2.6.17-2-686'

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]

yes

 

 

Extracting the sources of the vmci module.

 

Building the vmci module.

 

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config0/vmci-only'

make -C /usr/src/linux-headers-2.6.17-2-686/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/linux-headers-2.6.17-2-686'

  CC [M]  /tmp/vmware-config0/vmci-only/dbllnklst.o

  CC [M]  /tmp/vmware-config0/vmci-only/kernelStubsLinux.o

  CC [M]  /tmp/vmware-config0/vmci-only/vmciDatagram.o

  CC [M]  /tmp/vmware-config0/vmci-only/vmci_drv.o

  CC [M]  /tmp/vmware-config0/vmci-only/vmciProcess.o

  CC [M]  /tmp/vmware-config0/vmci-only/vmciResource.o

  CC [M]  /tmp/vmware-config0/vmci-only/vmciSharedMemory.o

  CC [M]  /tmp/vmware-config0/vmci-only/vmciTest.o

  CC [M]  /tmp/vmware-config0/vmci-only/vmciUtil.o

  LD [M]  /tmp/vmware-config0/vmci-only/vmci.o

  Building modules, stage 2.

  MODPOST

  CC      /tmp/vmware-config0/vmci-only/vmci.mod.o

  LD [M]  /tmp/vmware-config0/vmci-only/vmci.ko

make[1]: Leaving directory `/usr/src/linux-headers-2.6.17-2-686'

cp -f vmci.ko ./../vmci.o

make: Leaving directory `/tmp/vmware-config0/vmci-only'

The module loads perfectly in the running kernel.

 

Detected X.org version 7.1.

 

 

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

 

X Window System Version 7.1.1

Release Date: 12 May 2006

X Protocol Version 11, Revision 0, Release 7.1.1

Build Operating System: UNKNOWN

Current Operating System: Linux debian 2.6.17-2-686 #1 SMP Wed Sep 13 16:34:10 UTC 2006 i686

Build Date: 04 September 2007

        Before reporting problems, check http://wiki.x.org

        to make sure that you have the latest version.

Module Loader present

Markers: (--) probed, (**) from config file, (==) default setting,

        (++) from command line, (!!) notice, (II) informational,

        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.

(++) Log file: "/tmp/vmware-config0/XF86ConfigLog.4879", Time: Mon Oct  1 09:32:46 2007

(++) Using config file: "/tmp/vmware-config0/XF86Config.4879"

(EE) Failed to load module "void" (module does not exist, 0)

 

X is running fine with the new config file.

 

(EE) AIGLX: Screen 0 is not DRI capable

(EE) No Input driver matching `void'

    xkb_keycodes             { include "xfree86+aliases(qwerty)" };

    xkb_types                { include "complete" };

    xkb_compatibility        { include "complete" };

    xkb_symbols              { include "pc(pc105)+us" };

    xkb_geometry             { include "pc(pc104)" };

FreeFontPath: FPE "/usr/share/fonts/X11/misc" refcount is 2, should be 1; fixing.

Starting VMware Tools services in the virtual machine:

   Switching to guest configuration:                                   done

   Guest filesystem driver:                                            done

   Mounting HGFS shares:                                              failed

   Guest memory manager:                                               done

   Guest vmxnet fast network device:                                   done

   New Host-Guest communications path:                                 done

   Blocking file system:                                               done

   DMA setup:                                                          done

   Guest operating system daemon:                                      done

 

The configuration of VMware Tools 6.0.0 build-45731 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:

"/usr/bin/vmware-toolbox" during an X server session.

 

To use the vmxnet driver, restart networking using the following commands:

/etc/init.d/networking stop

rmmod pcnet32

rmmod vmxnet

modprobe vmxnet

/etc/init.d/networking start

 

If you wish to configure any experimental features, please run the following

command: "vmware-config-tools.pl --experimental".

 

Enjoy,

 

--the VMware team         

------------------------------------

到这里需要做下面三件工作

1.设置显示器的分辨率（display）

2.修正鼠标飘逸问题：

在vm（fedora 9）中安装vm-tool后鼠标位置错误，由于在装载xorg-x11-drv-vmmouse驱动时的一个bug，
在客户虚拟机的显示中，鼠标位置可能不正确。直到被更新前，在客户机中添加Option NoAutoAddDevices到
/etc/X11/xorg.conf文件的ServerFlags节中。
如果需要，创建这个节：
Section "ServerFlags"
Option "NoAutoAddDevices"
EndSection
这三句话要放在xorg.conf的最后，要不然重新启动后就不会有图形界面...

3.reboot  ok

--------------------------------------------