Oracle Linux 5.7安装VMware Tools的问题-白红宇

Oracle Linux 5.7安装VMware Tools的问题

阅读量：5834 次

发布时间：2019-06-18

本文共 21275 字，大约阅读时间需要 70 分钟。

案例环境介绍：

虚拟机的版本：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目录下

[root@DB-Server 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
[root@DB-Server 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即可安装成功。安装过程如下所示：

[root@DB-Server 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

转载地址：http://gzucx.baihongyu.com/

你可能感兴趣的文章

argparse - 命令行选项与参数解析（转）

查看>>

修改上一篇文章的node.js代码，支持默认页及支持中文

查看>>

我理想中的前端工作流

查看>>

Chrome 广告屏蔽功能不影响浏览器性能

查看>>

Android状态栏实现沉浸式模式

查看>>

java只能的round,ceil,floor方法的使用

Spring Cloud 微服务分布式链路跟踪 Sleuth 与 Zipkin

查看>>

ORM数据库框架 SQLite 常用数据库框架比较 MD

Windows 下最佳的 C++ 开发的 IDE 是什么？