[问题]WinXP下VMware的Ubuntu7.04的vmware-tools装不上
发表于 ： 2008-04-07 14:24
麻烦各位高手帮忙看下， 万分感谢
Stopping VMware Tools services in the virtual machine:
Guest operating system daemon: done
The bld-2.6.22-14-i386generic-Ubuntu7.10 - vmmemctl module loads perfectly into
the running kernel.
The bld-2.6.22-14-i386generic-Ubuntu7.10 - 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]
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.22-14-generic/build/include]
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.22-14-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.22-14-generic'
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/linux-headers-2.6.22-14-generic'
cp -f vmxnet.ko ./../vmxnet.o
make: Leaving directory `/tmp/vmware-config0/vmxnet-only'
Unable to make a vmxnet module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-config0/vmxnet.o': -1 File exists
There is probably a slight difference in the kernel configuration between the
set of C header files you specified and your running kernel. You may want to
rebuild a kernel based on that directory, or specify another directory.
The fast network device driver (vmxnet module) is used only for our fast
networking interface. The rest of the software provided by VMware Tools is
designed to work independently of this feature.
If you wish to have the fast network driver enabled, 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 ]
The bld-2.6.22-14-i386generic-Ubuntu7.10 - vmblock module loads perfectly into
the running kernel.
The bld-2.6.22-14-i386generic-Ubuntu7.10 - vmsync module loads perfectly into
the running kernel.
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-config1/vmci-only'
make -C /lib/modules/2.6.22-14-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.22-14-generic'
CC [M] /tmp/vmware-config1/vmci-only/kernelStubsLinux.o
CC [M] /tmp/vmware-config1/vmci-only/vmciDatagram.o
CC [M] /tmp/vmware-config1/vmci-only/vmci_drv.o
CC [M] /tmp/vmware-config1/vmci-only/vmciEvent.o
CC [M] /tmp/vmware-config1/vmci-only/vmciGuestDs.o
CC [M] /tmp/vmware-config1/vmci-only/vmciGuestKernelIf.o
CC [M] /tmp/vmware-config1/vmci-only/vmciKernelIf.o
CC [M] /tmp/vmware-config1/vmci-only/vmciProcess.o
CC [M] /tmp/vmware-config1/vmci-only/vmciQueuePair.o
CC [M] /tmp/vmware-config1/vmci-only/vmciUtil.o
LD [M] /tmp/vmware-config1/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config1/vmci-only/vmci.mod.o
LD [M] /tmp/vmware-config1/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.22-14-generic'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/vmware-config1/vmci-only'
Unable to make a vmci module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-config1/vmci.o': -1 Invalid module format
There is probably a slight difference in the kernel configuration between the
set of C header files you specified and your running kernel. You may want to
rebuild a kernel based on that directory, or specify another directory.
The communication service is used in addition to the standard communication
between the guest and the host. The rest of the software provided by VMware
Tools is designed to work independently of this feature.
If you wish to have the VMCI feature, 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 ]
None of the pre-built vmxnet3 modules for VMware Tools is suitable for your
running kernel. Do you want this program to try to build the vmxnet3 module
for your system (you need to have a C compiler installed on your system)?
[yes]
Extracting the sources of the vmxnet3 module.
Building the vmxnet3 module.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config2/vmxnet3-only'
make -C /lib/modules/2.6.22-14-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.22-14-generic'
CC [M] /tmp/vmware-config2/vmxnet3-only/vmxnet3.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config2/vmxnet3-only/vmxnet3.mod.o
LD [M] /tmp/vmware-config2/vmxnet3-only/vmxnet3.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.22-14-generic'
cp -f vmxnet3.ko ./../vmxnet3.o
make: Leaving directory `/tmp/vmware-config2/vmxnet3-only'
Unable to make a vmxnet3 module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-config2/vmxnet3.o': -1 File exists
There is probably a slight difference in the kernel configuration between the
set of C header files you specified and your running kernel. You may want to
rebuild a kernel based on that directory, or specify another directory.
The advanced network device driver (vmxnet3 module) is used only for our
advanced networking interface. The rest of the software provided by VMware
Tools is designed to work independently of this feature.
If you wish to have the advanced network driver enabled, 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 ]
Detected X.org version 7.1.0.
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]
X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Linux Ubuntu (xorg-server 2:1.3.0.0.dfsg-12ubuntu8)
Current Operating System: Linux wunan-desktop 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686
Build Date: 29 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-config3/XF86ConfigLog.9026", Time: Mon Apr 7 14:25:34 2008
(++) Using config file: "/tmp/vmware-config3/XF86Config.9026"
X is running fine with the new config file.
(II) Module already built-in
(EE) AIGLX: Screen 0 is not DRI capable
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
Blocking file system: done
File system sync driver: done
DMA setup: done
Guest operating system daemon: done
The configuration of VMware Tools e.x.p build-84113 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.
Enjoy,
--the VMware team
Unknown command
wunan@wunan-desktop:~/vmware-tools-distrib$
Stopping VMware Tools services in the virtual machine:
Guest operating system daemon: done
The bld-2.6.22-14-i386generic-Ubuntu7.10 - vmmemctl module loads perfectly into
the running kernel.
The bld-2.6.22-14-i386generic-Ubuntu7.10 - 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]
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.22-14-generic/build/include]
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.22-14-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.22-14-generic'
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/linux-headers-2.6.22-14-generic'
cp -f vmxnet.ko ./../vmxnet.o
make: Leaving directory `/tmp/vmware-config0/vmxnet-only'
Unable to make a vmxnet module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-config0/vmxnet.o': -1 File exists
There is probably a slight difference in the kernel configuration between the
set of C header files you specified and your running kernel. You may want to
rebuild a kernel based on that directory, or specify another directory.
The fast network device driver (vmxnet module) is used only for our fast
networking interface. The rest of the software provided by VMware Tools is
designed to work independently of this feature.
If you wish to have the fast network driver enabled, 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 ]
The bld-2.6.22-14-i386generic-Ubuntu7.10 - vmblock module loads perfectly into
the running kernel.
The bld-2.6.22-14-i386generic-Ubuntu7.10 - vmsync module loads perfectly into
the running kernel.
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-config1/vmci-only'
make -C /lib/modules/2.6.22-14-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.22-14-generic'
CC [M] /tmp/vmware-config1/vmci-only/kernelStubsLinux.o
CC [M] /tmp/vmware-config1/vmci-only/vmciDatagram.o
CC [M] /tmp/vmware-config1/vmci-only/vmci_drv.o
CC [M] /tmp/vmware-config1/vmci-only/vmciEvent.o
CC [M] /tmp/vmware-config1/vmci-only/vmciGuestDs.o
CC [M] /tmp/vmware-config1/vmci-only/vmciGuestKernelIf.o
CC [M] /tmp/vmware-config1/vmci-only/vmciKernelIf.o
CC [M] /tmp/vmware-config1/vmci-only/vmciProcess.o
CC [M] /tmp/vmware-config1/vmci-only/vmciQueuePair.o
CC [M] /tmp/vmware-config1/vmci-only/vmciUtil.o
LD [M] /tmp/vmware-config1/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config1/vmci-only/vmci.mod.o
LD [M] /tmp/vmware-config1/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.22-14-generic'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/vmware-config1/vmci-only'
Unable to make a vmci module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-config1/vmci.o': -1 Invalid module format
There is probably a slight difference in the kernel configuration between the
set of C header files you specified and your running kernel. You may want to
rebuild a kernel based on that directory, or specify another directory.
The communication service is used in addition to the standard communication
between the guest and the host. The rest of the software provided by VMware
Tools is designed to work independently of this feature.
If you wish to have the VMCI feature, 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 ]
None of the pre-built vmxnet3 modules for VMware Tools is suitable for your
running kernel. Do you want this program to try to build the vmxnet3 module
for your system (you need to have a C compiler installed on your system)?
[yes]
Extracting the sources of the vmxnet3 module.
Building the vmxnet3 module.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config2/vmxnet3-only'
make -C /lib/modules/2.6.22-14-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.22-14-generic'
CC [M] /tmp/vmware-config2/vmxnet3-only/vmxnet3.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/vmware-config2/vmxnet3-only/vmxnet3.mod.o
LD [M] /tmp/vmware-config2/vmxnet3-only/vmxnet3.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.22-14-generic'
cp -f vmxnet3.ko ./../vmxnet3.o
make: Leaving directory `/tmp/vmware-config2/vmxnet3-only'
Unable to make a vmxnet3 module that can be loaded in the running kernel:
insmod: error inserting '/tmp/vmware-config2/vmxnet3.o': -1 File exists
There is probably a slight difference in the kernel configuration between the
set of C header files you specified and your running kernel. You may want to
rebuild a kernel based on that directory, or specify another directory.
The advanced network device driver (vmxnet3 module) is used only for our
advanced networking interface. The rest of the software provided by VMware
Tools is designed to work independently of this feature.
If you wish to have the advanced network driver enabled, 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 ]
Detected X.org version 7.1.0.
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]
X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Linux Ubuntu (xorg-server 2:1.3.0.0.dfsg-12ubuntu8)
Current Operating System: Linux wunan-desktop 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686
Build Date: 29 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-config3/XF86ConfigLog.9026", Time: Mon Apr 7 14:25:34 2008
(++) Using config file: "/tmp/vmware-config3/XF86Config.9026"
X is running fine with the new config file.
(II) Module already built-in
(EE) AIGLX: Screen 0 is not DRI capable
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
Blocking file system: done
File system sync driver: done
DMA setup: done
Guest operating system daemon: done
The configuration of VMware Tools e.x.p build-84113 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.
Enjoy,
--the VMware team
Unknown command
wunan@wunan-desktop:~/vmware-tools-distrib$
我也刚想问同样的问题，不过我是虚拟8.04，如果说这样提示是安装完毕的话那我在重启后一点效果都没看到，至少鼠标在进入桌面后就动不了，什么操作也进行不下去，不知到是怎么回事。望高手帮忙～～～