原创 Fedora Core Linux 9 中安装VMware Tools-6.5.0

近日因为要在Linux中开发软件，安装了VMware
Workstation 6.5-118166.

以下为安装VMware
Tools-6.5.0的过程。

1。安装内核开发包（FC9默认没有安装，可以在网上找到并下载安装）

root@localhost
arm]# rpm -ivh kernel-devel-2.6.25-14.fc9.i686.rpm

2。安装VMwareTools-6.5.0-118166.i386.rpm（也可以通过源码安装，需要有GCC）

root@localhost
arm]# rpm -ivh VmwareTools-6.5.0-118166.i386.rpm

3。配置，一路Enter。

root@localhost
arm]# vmware-config-tools.pl

Stopping
VMware Tools services in the virtual machine:

Guest
operating system daemon: [确定]

Virtual
Printing daemon: [确定]

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.25-14.fc9.i686/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.25-14.fc9.i686/build/include/.. SUBDIRS=$PWD
SRCROOT=$PWD/. modules

make[1]:
Entering directory `/usr/src/kernels/2.6.25-14.fc9.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
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.25-14.fc9.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.25-14.fc9.i686/build/include/.. SUBDIRS=$PWD
SRCROOT=$PWD/. modules

make[1]:
Entering directory `/usr/src/kernels/2.6.25-14.fc9.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
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.25-14.fc9.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.25-14.fc9.i686/build/include/.. SUBDIRS=$PWD
SRCROOT=$PWD/. modules

make[1]:
Entering directory `/usr/src/kernels/2.6.25-14.fc9.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.25-14.fc9.i686'

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

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

The
vmxnet module loads perfectly into the 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]
no
// 因为我不需要宿主系统和FC9的交互应用和切换，这里选no，建议直接Enter.

The
vmblock module enables dragging or copying files from within a host
and

dropping
or pasting them onto your guest (host to guest drag and drop and file

copy/paste).
The rest of the software provided by VMware Tools is designed to

work
independently of this feature (including guest to host drag and drop
and

file
copy/paste).

If
you would like the host to guest drag and drop and file copy/paste
features,

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 ]

[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-config0/vmci-only'

make
-C /lib/modules/2.6.25-14.fc9.i686/build/include/.. SUBDIRS=$PWD
SRCROOT=$PWD/. modules

make[1]:
Entering directory `/usr/src/kernels/2.6.25-14.fc9.i686'

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/vmciEvent.o

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

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

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

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

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

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

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

Building
modules, stage 2.

MODPOST
1 modules

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

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

make[1]:
Leaving directory `/usr/src/kernels/2.6.25-14.fc9.i686'

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

make:
Leaving directory `/tmp/vmware-config0/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-config0/vsock-only'

make
-C /lib/modules/2.6.25-14.fc9.i686/build/include/.. SUBDIRS=$PWD
SRCROOT=$PWD/. modules

make[1]:
Entering directory `/usr/src/kernels/2.6.25-14.fc9.i686'

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

CC
[M] /tmp/vmware-config0/vsock-only/linux/driverLog.o

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

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

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

Building
modules, stage 2.

MODPOST
1 modules

WARNING:
"VMCIDatagram_CreateHnd"
[/tmp/vmware-config0/vsock-only/vsock.ko] undefined!

WARNING:
"VMCIDatagram_DestroyHnd"
[/tmp/vmware-config0/vsock-only/vsock.ko] undefined!

WARNING:
"VMCIEvent_Subscribe"
[/tmp/vmware-config0/vsock-only/vsock.ko] undefined!

WARNING:
"VMCI_DeviceGet" [/tmp/vmware-config0/vsock-only/vsock.ko]
undefined!

WARNING:
"VMCIMemcpyFromQueueV"
[/tmp/vmware-config0/vsock-only/vsock.ko] undefined!

WARNING:
"VMCIQueuePair_Detach"
[/tmp/vmware-config0/vsock-only/vsock.ko] undefined!

WARNING:
"VMCI_GetContextID"
[/tmp/vmware-config0/vsock-only/vsock.ko] undefined!

WARNING:
"VMCIDatagram_Send"
[/tmp/vmware-config0/vsock-only/vsock.ko] undefined!

WARNING:
"VMCIQueuePair_Alloc"
[/tmp/vmware-config0/vsock-only/vsock.ko] undefined!

WARNING:
"VMCIEvent_Unsubscribe"
[/tmp/vmware-config0/vsock-only/vsock.ko] undefined!

WARNING:
"VMCIMemcpyToQueueV"
[/tmp/vmware-config0/vsock-only/vsock.ko] undefined!

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

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

make[1]:
Leaving directory `/usr/src/kernels/2.6.25-14.fc9.i686'

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

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

The
vsock module loads perfectly into the running kernel.

Detected
X.org version 7.3.99.

No
drivers for X.org version: 7.3.99.

Please
choose one of the following display sizes that X will start with (1 -

29):

[1]
"320x200"

[2]
"320x240"

[3]
"400x300"

[4]
"512x384"

[5]
"640x400"

[6]
"640x480"

[7]
"720x480"

[8]
"800x480"

[9]
"854x480"

[10]
"720x576"

[11]
"800x600"

[12]
"1024x768"

[13]
"1280x720"

[14]
"1280x768"

[15]<
"1152x864"

[16]
"1280x800"

[17]
"1366x768"

[18]
"1280x960"

[19]
"1440x900"

[20]
"1280x1024"

[21]
"1400x1050"

[22]
"1680x1050"

[23]
"1600x1200"

[24]
"1920x1080"

[25]
"1920x1200"

[26]
"1920x1440"

[27]
"2048x1536"

[28]
"2560x1600"

[29]
"2560x1920"

Please
enter a number between 1 and 29:

[15]

X.Org
X Server 1.4.99.901 (1.5.0 RC 1)

Release
Date: 5 September 2007

X
Protocol Version 11, Revision 0

Build
Operating System: Linux 2.6.18-53.1.14.el5xen i686

Current
Operating System: Linux localhost.localdomain 2.6.25-14.fc9.i686 #1
SMP Thu May 1 06:28:41 EDT 2008 i686

Build
Date: 06 May 2008 03:35:07PM

Build
ID: xorg-x11-server 1.4.99.901-29.20080415.fc9

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.3124", Time:
Mon Oct 20 14:19:38 2008

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

X
is running fine with the new config file.

expected
keysym, got XF86Info: line 914 of inet

expected
keysym, got XF86Info: line 914 of inet

Checking
acpi hot plug [确定]

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: [确定]

VM
communication interface: [确定]

VM
communication interface socket family: [确定]

Guest
operating system daemon: [确定]

Virtual
Printing daemon: [确定]

The
configuration of VMware Tools 6.5.0 build-118166 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
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.

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

If
the virtual printer feature is enabled, you will need to restart the
CUPS

service
to make use of this feature.

Enjoy,

--the
VMware team

到此完全装好了。