Oracle Linux 5.7安装VMware Tools的问题

案例环境介绍：

    虚拟机的版本：VMware? Workstation 8.0.3 build-703057
    操作系统版本：Oracle Linux Server release 5.7

在安装虚拟机工具时，执行./vmware-install.pl 命令后一步一步操作，最后出现如下错误信息,安装程序aborted：

Creating a new initrd boot image for the kernel. No module ehci-hcd found for kernel 2.6.32-200.13.1.el5uek, aborting. ERROR: "/sbin/mkinitrd -f  --with=vmxnet3   --with=vmw_pvscsi   --with=vmxnet  /boot/initrd-2.6.32-200.13.1.el5uek.img 2.6.32-200.13.1.el5uek" exited with non-zero status.

Your system currently may not have a functioning init image and may not boot properly.  DO NOT REBOOT!  Please ensure that you have enough free space available in your /boot directory and run this configuration script again.

Execution aborted.

Found VMware Tools CDROM mounted at /media/VMware Tools. Ejecting device /dev/sr0 ...
    Found VMware Tools CDROM mounted at /mnt/cdrom. Ejecting device /dev/cdrom ...

解决方法介绍：

Google了一些资料后，终于找到了一个解决方法：拷贝一些文件到对应目录即可解决这个错误。如下所示：将这些文件拷贝到/lib/modules/2.6.32-200.13.1.el5uek/kernel/drivers/usb/host目录下

[[email protected] host]# ls /lib/modules/2.6.18-274.el5/kernel/drivers/usb/host/?hci-hcd.ko 
/lib/modules/2.6.18-274.el5/kernel/drivers/usb/host/ehci-hcd.ko

/lib/modules/2.6.18-274.el5/kernel/drivers/usb/host/ohci-hcd.ko

/lib/modules/2.6.18-274.el5/kernel/drivers/usb/host/uhci-hcd.ko

[[email protected] host]# cp /lib/modules/2.6.18-274.el5/kernel/drivers/usb/host/?hci-hcd.ko /lib/modules/2.6.32-200.13.1.el5uek/kernel/drivers/usb/host

拷贝完这些文件后，执行perl安装脚本vmware-install.pl重新安装VMware Tools即可安装成功。安装过程如下所示：

[[email protected] vmware-tools-distrib]# ./vmware-install.pl 
A previous installation of VMware Tools has been detected.

 

The previous installation was made by the tar installer (version 4).

 

Keeping the tar4 installer database format.

 

You have a version of VMware Tools installed.  Continuing this install will 

first uninstall the currently installed version.  Do you wish to continue? 

(yes/no) [yes] 

 

Uninstalling the tar installation of VMware Tools.

 

Stopping services for VMware Tools

 

Stopping VMware Tools services in the virtual machine:

   Guest operating system daemon:[  OK  ]

   Virtual Printing daemon:[  OK  ]

   VMware User Agent (vmware-user):[  OK  ]

   Blocking file system:[  OK  ]

   Unmounting HGFS shares:[  OK  ]

   Guest filesystem driver:[  OK  ]

   VM communication interface socket family:[  OK  ]

   VM communication interface:[  OK  ]

 

This program previously created the file 

/usr/lib/vmware-tools/lib64/libconf/etc/pango/pango.modules, and was about to 

remove it.  Somebody else apparently did it already.

 

File /etc/vmware-tools/vmware-user.desktop is backed up to 

/etc/vmware-tools/vmware-user.desktop.old.2.

 

File /usr/lib/vmware-tools/lib64/libconf/etc/gtk-2.0/gtk.immodules is backed up

to /usr/lib/vmware-tools/lib64/libconf/etc/gtk-2.0/gtk.immodules.old.2.

 

File /usr/lib/vmware-tools/lib64/libconf/etc/gtk-2.0/gdk-pixbuf.loaders is 

backed up to 

/usr/lib/vmware-tools/lib64/libconf/etc/gtk-2.0/gdk-pixbuf.loaders.old.2.

 

This program previously created the file 

/usr/lib/vmware-tools/libconf/etc/gtk-2.0/gdk-pixbuf.loaders, and was about to 

remove it.  Somebody else apparently did it already.

 

This program previously created the file 

/usr/lib/vmware-tools/lib64/libconf/etc/pango/pangorc, and was about to remove 

it.  Somebody else apparently did it already.

 

This program previously created the file 

/usr/lib/vmware-tools/libconf/etc/gtk-2.0/gtk.immodules, and was about to 

remove it.  Somebody else apparently did it already.

 

This program previously created the file 

/usr/lib/vmware-tools/lib64/libconf/etc/pango/pangox.aliases, and was about to 

remove it.  Somebody else apparently did it already.

 

This program previously created the directory /etc/vmware-tools, and was about 

to remove it. Since there are files in that directory that this program did not

create, it will not be removed.

 

File /etc/X11/xorg.conf is backed up to /etc/X11/xorg.conf.old.2.

 

The removal of VMware Tools 8.8.2 build-590212 for Linux completed 

successfully.

 

Installing VMware Tools.

 

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/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? 

[/usr/sbin] 

 

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

[/usr/lib/vmware-tools] 

 

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 program 

is going to create it, including needed parent directories. Is this what you 

want? [yes] 

 

The installation of VMware Tools 8.8.2 build-590212 for Linux completed 

successfully. You can decide to remove this software from your system at any 

time by invoking the following command: "/usr/bin/vmware-uninstall-tools.pl".

 

Before running VMware Tools for the first time, you need to configure it by 

invoking the following command: "/usr/bin/vmware-config-tools.pl". Do you want 

this program to invoke the command for you now? [yes] 

 

Initializing...

 

 

Making sure services for VMware Tools are stopped.

 

Stopping VMware Tools services in the virtual machine:

   Guest operating system daemon:[  OK  ]

   Virtual Printing daemon:[  OK  ]

   VMware User Agent (vmware-user):[  OK  ]

   Blocking file system:[  OK  ]

   Unmounting HGFS shares:[  OK  ]

   Guest filesystem driver:[  OK  ]

   VM communication interface socket family:[  OK  ]

   VM communication interface:[  OK  ]

 

 

[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] no

 

 

Before you can compile modules, you need to have the following installed... 

 

make

gcc

kernel headers of the running kernel

 

 

Searching for GCC...

Detected GCC binary at "/usr/bin/gcc".

The path "/usr/bin/gcc" appears to be a valid path to the gcc binary.

Would you like to change it? [no] no

 

Searching for a valid kernel header path...

Detected the kernel headers at 

"/lib/modules/2.6.32-200.13.1.el5uek/build/include".

The path "/lib/modules/2.6.32-200.13.1.el5uek/build/include" appears to be a 

valid path to the 2.6.32-200.13.1.el5uek kernel headers.

Would you like to change it? [no] 

 

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-root/modules/vmci-only‘

make -C /lib/modules/2.6.32-200.13.1.el5uek/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

          MODULEBUILDDIR= modules

make[1]: Entering directory `/usr/src/kernels/2.6.32-200.13.1.el5uek‘

  CC [M]  /tmp/vmware-root/modules/vmci-only/linux/driver.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciContext.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDatagram.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDoorbell.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDriver.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciEvent.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciHashtable.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciQPair.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciQueuePair.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciResource.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciRoute.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/driverLog.o

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

  Building modules, stage 2.

  MODPOST 1 modules

  CC      /tmp/vmware-root/modules/vmci-only/vmci.mod.o

  LD [M]  /tmp/vmware-root/modules/vmci-only/vmci.ko.unsigned

  NO SIGN [M] /tmp/vmware-root/modules/vmci-only/vmci.ko

make[1]: Leaving directory `/usr/src/kernels/2.6.32-200.13.1.el5uek‘

make -C $PWD SRCROOT=$PWD/. \

          MODULEBUILDDIR= postbuild

make[1]: Entering directory `/tmp/vmware-root/modules/vmci-only‘

make[1]: `postbuild‘ is up to date.

make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only‘

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

make: Leaving directory `/tmp/vmware-root/modules/vmci-only‘

 

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-root/modules/vmci-only‘

make -C /lib/modules/2.6.32-200.13.1.el5uek/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

          MODULEBUILDDIR= modules

make[1]: Entering directory `/usr/src/kernels/2.6.32-200.13.1.el5uek‘

  CC [M]  /tmp/vmware-root/modules/vmci-only/linux/driver.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciContext.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDatagram.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDoorbell.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDriver.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciEvent.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciHashtable.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciQPair.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciQueuePair.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciResource.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciRoute.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/driverLog.o

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

  Building modules, stage 2.

  MODPOST 1 modules

  CC      /tmp/vmware-root/modules/vmci-only/vmci.mod.o

  LD [M]  /tmp/vmware-root/modules/vmci-only/vmci.ko.unsigned

  NO SIGN [M] /tmp/vmware-root/modules/vmci-only/vmci.ko

make[1]: Leaving directory `/usr/src/kernels/2.6.32-200.13.1.el5uek‘

make -C $PWD SRCROOT=$PWD/. \

          MODULEBUILDDIR= postbuild

make[1]: Entering directory `/tmp/vmware-root/modules/vmci-only‘

make[1]: `postbuild‘ is up to date.

make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only‘

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

make: Leaving directory `/tmp/vmware-root/modules/vmci-only‘

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-root/modules/vsock-only‘

make -C /lib/modules/2.6.32-200.13.1.el5uek/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

          MODULEBUILDDIR= modules

make[1]: Entering directory `/usr/src/kernels/2.6.32-200.13.1.el5uek‘

  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/af_vsock.o

  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/notify.o

  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/notifyQState.o

  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/stats.o

  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/util.o

  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/vsockAddr.o

  CC [M]  /tmp/vmware-root/modules/vsock-only/driverLog.o

  LD [M]  /tmp/vmware-root/modules/vsock-only/vsock.o

  Building modules, stage 2.

  MODPOST 1 modules

  CC      /tmp/vmware-root/modules/vsock-only/vsock.mod.o

  LD [M]  /tmp/vmware-root/modules/vsock-only/vsock.ko.unsigned

  NO SIGN [M] /tmp/vmware-root/modules/vsock-only/vsock.ko

make[1]: Leaving directory `/usr/src/kernels/2.6.32-200.13.1.el5uek‘

make -C $PWD SRCROOT=$PWD/. \

          MODULEBUILDDIR= postbuild

make[1]: Entering directory `/tmp/vmware-root/modules/vsock-only‘

make[1]: `postbuild‘ is up to date.

make[1]: Leaving directory `/tmp/vmware-root/modules/vsock-only‘

cp -f vsock.ko ./../vsock.o

make: Leaving directory `/tmp/vmware-root/modules/vsock-only‘

 

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-root/modules/vmxnet3-only‘

make -C /lib/modules/2.6.32-200.13.1.el5uek/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

          MODULEBUILDDIR= modules

make[1]: Entering directory `/usr/src/kernels/2.6.32-200.13.1.el5uek‘

  CC [M]  /tmp/vmware-root/modules/vmxnet3-only/vmxnet3_drv.o

  CC [M]  /tmp/vmware-root/modules/vmxnet3-only/vmxnet3_ethtool.o

  CC [M]  /tmp/vmware-root/modules/vmxnet3-only/vmxnet3_shm.o

  LD [M]  /tmp/vmware-root/modules/vmxnet3-only/vmxnet3.o

  Building modules, stage 2.

  MODPOST 1 modules

  CC      /tmp/vmware-root/modules/vmxnet3-only/vmxnet3.mod.o

  LD [M]  /tmp/vmware-root/modules/vmxnet3-only/vmxnet3.ko.unsigned

  NO SIGN [M] /tmp/vmware-root/modules/vmxnet3-only/vmxnet3.ko

make[1]: Leaving directory `/usr/src/kernels/2.6.32-200.13.1.el5uek‘

make -C $PWD SRCROOT=$PWD/. \

          MODULEBUILDDIR= postbuild

make[1]: Entering directory `/tmp/vmware-root/modules/vmxnet3-only‘

make[1]: `postbuild‘ is up to date.

make[1]: Leaving directory `/tmp/vmware-root/modules/vmxnet3-only‘

cp -f vmxnet3.ko ./../vmxnet3.o

make: Leaving directory `/tmp/vmware-root/modules/vmxnet3-only‘

 

The module pvscsi has already been installed on this system by another 

installer or package and will not be modified by this installer.  Use the flag 

--clobber-kernel-modules=pvscsi to override.

 

The module vmmemctl has already been installed on this system by another 

installer or package and will not be modified by this installer.  Use the flag 

--clobber-kernel-modules=vmmemctl to override.

 

The VMware Host-Guest Filesystem allows for shared folders between the host OS 

and the guest OS in a Fusion or Workstation virtual environment.  Do you wish 

to enable this feature? [yes] 

 

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-root/modules/vmci-only‘

make -C /lib/modules/2.6.32-200.13.1.el5uek/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

          MODULEBUILDDIR= modules

make[1]: Entering directory `/usr/src/kernels/2.6.32-200.13.1.el5uek‘

  CC [M]  /tmp/vmware-root/modules/vmci-only/linux/driver.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciContext.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDatagram.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDoorbell.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDriver.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciEvent.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciHashtable.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciQPair.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciQueuePair.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciResource.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciRoute.o

  CC [M]  /tmp/vmware-root/modules/vmci-only/driverLog.o

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

  Building modules, stage 2.

  MODPOST 1 modules

  CC      /tmp/vmware-root/modules/vmci-only/vmci.mod.o

  LD [M]  /tmp/vmware-root/modules/vmci-only/vmci.ko.unsigned

  NO SIGN [M] /tmp/vmware-root/modules/vmci-only/vmci.ko

make[1]: Leaving directory `/usr/src/kernels/2.6.32-200.13.1.el5uek‘

make -C $PWD SRCROOT=$PWD/. \

          MODULEBUILDDIR= postbuild

make[1]: Entering directory `/tmp/vmware-root/modules/vmci-only‘

make[1]: `postbuild‘ is up to date.

make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only‘

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

make: Leaving directory `/tmp/vmware-root/modules/vmci-only‘

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-root/modules/vmhgfs-only‘

make -C /lib/modules/2.6.32-200.13.1.el5uek/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

          MODULEBUILDDIR= modules

make[1]: Entering directory `/usr/src/kernels/2.6.32-200.13.1.el5uek‘

  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/backdoor.o

  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/backdoorGcc64.o

  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/bdhandler.o

  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/cpName.o

  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/cpNameLinux.o

  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/cpNameLite.o

  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/dentry.o

  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/dir.o

  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/file.o

  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/filesystem.o

  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/fsutil.o

  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/hgfsBd.o

  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/hgfsEscape.o

  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/hgfsUtil.o

  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/inode.o

  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/link.o

  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/message.o

  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/module.o

  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/page.o

  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/request.o

  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/rpcout.o

  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/stubs.o

  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/super.o

  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/tcp.o

  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/transport.o

  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/vmci.o

  CC [M]  /tmp/vmware-root/modules/vmhgfs-only/kernelStubsLinux.o

  LD [M]  /tmp/vmware-root/modules/vmhgfs-only/vmhgfs.o

  Building modules, stage 2.

  MODPOST 1 modules

  CC      /tmp/vmware-root/modules/vmhgfs-only/vmhgfs.mod.o

  LD [M]  /tmp/vmware-root/modules/vmhgfs-only/vmhgfs.ko.unsigned

  NO SIGN [M] /tmp/vmware-root/modules/vmhgfs-only/vmhgfs.ko

make[1]: Leaving directory `/usr/src/kernels/2.6.32-200.13.1.el5uek‘

make -C $PWD SRCROOT=$PWD/. \

          MODULEBUILDDIR= postbuild

make[1]: Entering directory `/tmp/vmware-root/modules/vmhgfs-only‘

make[1]: `postbuild‘ is up to date.

make[1]: Leaving directory `/tmp/vmware-root/modules/vmhgfs-only‘

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

make: Leaving directory `/tmp/vmware-root/modules/vmhgfs-only‘

 

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-root/modules/vmxnet-only‘

make -C /lib/modules/2.6.32-200.13.1.el5uek/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

          MODULEBUILDDIR= modules

make[1]: Entering directory `/usr/src/kernels/2.6.32-200.13.1.el5uek‘

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

  Building modules, stage 2.

  MODPOST 1 modules

  CC      /tmp/vmware-root/modules/vmxnet-only/vmxnet.mod.o

  LD [M]  /tmp/vmware-root/modules/vmxnet-only/vmxnet.ko.unsigned

  NO SIGN [M] /tmp/vmware-root/modules/vmxnet-only/vmxnet.ko

make[1]: Leaving directory `/usr/src/kernels/2.6.32-200.13.1.el5uek‘

make -C $PWD SRCROOT=$PWD/. \

          MODULEBUILDDIR= postbuild

make[1]: Entering directory `/tmp/vmware-root/modules/vmxnet-only‘

make[1]: `postbuild‘ is up to date.

make[1]: Leaving directory `/tmp/vmware-root/modules/vmxnet-only‘

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

make: Leaving directory `/tmp/vmware-root/modules/vmxnet-only‘

 

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-root/modules/vmblock-only‘

make -C /lib/modules/2.6.32-200.13.1.el5uek/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

          MODULEBUILDDIR= modules

make[1]: Entering directory `/usr/src/kernels/2.6.32-200.13.1.el5uek‘

  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/block.o

  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/control.o

  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/dbllnklst.o

  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/dentry.o

  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/file.o

  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/filesystem.o

  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/inode.o

  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/module.o

  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/stubs.o

  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/super.o

  LD [M]  /tmp/vmware-root/modules/vmblock-only/vmblock.o

  Building modules, stage 2.

  MODPOST 1 modules

  CC      /tmp/vmware-root/modules/vmblock-only/vmblock.mod.o

  LD [M]  /tmp/vmware-root/modules/vmblock-only/vmblock.ko.unsigned

  NO SIGN [M] /tmp/vmware-root/modules/vmblock-only/vmblock.ko

make[1]: Leaving directory `/usr/src/kernels/2.6.32-200.13.1.el5uek‘

make -C $PWD SRCROOT=$PWD/. \

          MODULEBUILDDIR= postbuild

make[1]: Entering directory `/tmp/vmware-root/modules/vmblock-only‘

make[1]: `postbuild‘ is up to date.

make[1]: Leaving directory `/tmp/vmware-root/modules/vmblock-only‘

cp -f vmblock.ko ./../vmblock.o

make: Leaving directory `/tmp/vmware-root/modules/vmblock-only‘

 

!!! [EXPERIMENTAL] !!!

VMware automatic kernel modules enables automatic building and installation of

VMware kernel modules at boot they are not already present.  By selecting yes,

you will be enabling this experimental feature.  You can always disable this

feature by re-running vmware-config-tools.pl.

 

Would you like to enable VMware automatic kernel modules?

[no] no

 

 

 

Detected X version 7.1

 

 

 

Do you want to change the starting screen display size? (yes/no) [no] 

 

 

X is running fine with the new config file.

 

Creating a new initrd boot image for the kernel.

   Checking acpi hot plug[  OK  ]

Starting VMware Tools services in the virtual machine:

   Switching to guest configuration:[  OK  ]

   VM communication interface:[  OK  ]

   VM communication interface socket family:[  OK  ]

   Guest filesystem driver:[  OK  ]

   Mounting HGFS shares:[  OK  ]

   Blocking file system:[  OK  ]

   Guest operating system daemon:[  OK  ]

   Virtual Printing daemon:[  OK  ]

The configuration of VMware Tools 8.8.2 build-590212 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 "/usr/bin/vmware-toolbox-cmd" from the

command line or by invoking "/usr/bin/vmware-toolbox" from the command line 

during an X server session.

 

To enable advanced X features (e.g., guest resolution fit, drag and drop, and 

file and text copy/paste), you will need to do one (or more) of the following:

1. Manually start /usr/bin/vmware-user

2. Log out and log back into your desktop session; and,

3. Restart your X session.

 

Enjoy,

 

--the VMware team

Oracle Linux 5.7安装VMware Tools的问题

时间： 2024-11-10 01:03:02

Oracle Linux 5.7安装VMware Tools的问题的相关文章

如何实现在虚拟机上的Linux系统上安装vmware tools

如何实现在虚拟机上的Linux系统上安装vmware tools工具 作者:何扬   时间:2017年9月23日  上午8:29:16 [安装目的]Linux下需要安装VMware Tools工具来实现主机和虚拟机直接文件复制粘贴功能. [基本流程] 1.首先,打开虚拟机,进入Linux系统登录界面,请以以root用户登入系统. 2.点击虚拟机VM菜单栏--虚拟机--安装VMware Tools,如图A-1所示(作者这里显示的是"重新安装VMware Tools",是因为作者之前已经安

在LINUX环境下安装VMware tools

引言: 对于linux初学者来说,在虚拟VMware tools软件环境中没有安装VMware tools是一件头疼的事,你要从宿主机拖拽文件到虚拟机是不行的.安装VMware tools增强虚拟系统性能. 在虚拟LIUNX环境中安装VMware tools不像是虚拟环境win7那样简单,在虚拟w7中只要点击安装就OK-下一步-下一步.下面就来安装. 安装过程: 放入光盘 先卸载cdrom 进入misc下面的cd 拷贝红字处压缩文件到/tmp目录并且cd /tmp查看 查看压缩类型为gzip.

使用编译器在 Linux 虚拟机中安装 VMware Tools

要使用编译器在 Linux 客户机操作系统中安装 VMware Tools,请执行以下操作: 确保 Linux 虚拟机已打开电源. 如果正在运行 GUI 界面,请打开命令 shell. 注意:以 root 用户身份登录,或使用 sudo 命令完成以下每个步骤. 在虚拟机菜单中单击虚拟机,然后单击客户机 > 安装/升级 VMware Tools. 单击确定.注意:在某些情况下,请查看虚拟机 编辑设置 选项中 CDROM 设备的状态须为 已连接. 要创建一个装载点,请运行以下命令: mkdir /m

Linux字符界面安装VMware tools

以往用VMware虚拟机都是装的桌面版,无奈实验室电脑属于老爷机,跑桌面linux实在有点吃不消,只能装个Basic Server玩玩了... 在桌面环境下装VMwaretools很简单,直接点击VM--Settings就会自动弹出VM的光盘,然后拷贝VMwareTools-xxx.tar.gz到桌面,解压安装即可... 无奈字符界面点击VM--Settings没啥反应,这让俺去哪里找VMwareTools-xxx.tar.gz啊... 后来,摸索了发现在装完虚拟机之后,光驱内默认装载的市\VM

(已解决)在linux的虚拟机上安装vmware tools(实现windows与虚拟机之间的文件交互复制粘贴)

Linux下需要安装VMware Tools工具来实现主机和虚拟机直接文件复制粘贴功能,安装方法如下: ①点击虚拟机VM菜单栏--虚拟机--安装VMware Tools. ②然后RedHat系统中弹出的安装包,找到VMwareTools-9.2.3-1031360.tar.gz 然后右键解压到/media目录下. ③进入/media用终端命令进行安装. 1 2 3 4 5 6 7 8 9 10 11 [[email protected] VMware Tools]# cd /media/VMwa

如何给Red Hat Linux安装Vmware Tools

众所周知在VMware虚拟机中安装好了VMware Tools,才能实现主机与虚拟机之间的文件共享,同时可支持自由拖拽的功能,鼠标也可在虚拟机与主机之前自由移动(而不再用按Ctrl+Alt释放),而且还可以令虚拟机屏幕也可实现全屏化,重要一点能使得虚拟机的来宾系统时间与宿主机一致. 那么Red Hat Linux系统如何安装VMware tools的呢? 下面就介绍该工具(Vmware-Tools)在Linux环境中的安装步骤: 1. 在安装Linux的虚拟机中,单击"虚拟机"菜单下的

【Linux】在Debian安装VMware Tools

在Linux安装一个东西,不像Windows那样不停点下一步一下步,就能够完成安装,尤其像VMware Tools这些驱动级别的安装,你不得不费一番心思,才能弄好. Linux安装东西最大的一个特点就是使用终端不停地敲命令.下面边以VMware Tools的在Debian7安装,边讲解Linux的基本使用.使用的虚拟机是VMware9.0 相信熟悉Windows的朋友,刚像我一样,装完Linux系统还根本不知道Linux怎么用. 1.首先是VMWare的部分,在VMWare的菜单栏中,选择VM-

Linux下 安装VMware Tools工具

Linux下需要安装VMware Tools工具 Linux下需要安装VMware Tools工具来实现主机和虚拟机直接文件复制粘贴功能,安装方法如下: ①点击虚拟机VM菜单栏--虚拟机--安装VMware Tools. ②然后RedHat系统中弹出的安装包,找到VMwareTools-9.2.3-1031360.tar.gz 然后右键解压到/media目录下. ③进入/media用终端命令进行安装. [[email protected]?VMware?Tools]#?cd?/media/VMw

基于RHEL 6.5安装Oracle 11g详细教程（3）——安装VMware Tools

3  安装VMware Tools 1)如下图所示,依次选择虚拟机 -- 客户机 -- 安装/升级VMware Tools. 2)如下图所示,单击确定. 3)如下图所示,单击确定. 4)如下图所示,可以看到VMware Tools的安装介质. 5)如下图所示,在VMware Tools目录内点击右键选择Open in Terminal. 6)如下图所示,Terminal已经打开. [[email protected] VMware Tools]# ls manifest.txt VMwareTo