我安装vmware的时候,出现如下问题:

一般虚拟机的常见场景是在WINDOWS下安装Linux虚拟机,但是有一些情况需要倒过来,比如在Linux下安装VMware虚拟机来反过来安装WINDOWS.

1、启动并进入Linux系统。
2、然后选择虚拟机菜单中的“虚拟机/安装VMware-Tools”,此时就会有把VMware-tools文件映像到CD-ROM中。
3、把“VMwareTools-6.0.2-59824.i386.rpm,VMwareTools-6.0.2-59824.tar.gz”文件复制到自己的需要的位置中,然后选择一种安装方式。在此我选VMwareTools-6.0.2-59824.tar.gz。
4、解压
# tar -zxvf VmwareTools-6.0.2-59824.tar.gz
5、进入/home/tsm/Tools/vmware-tools-distrib目录中,
cd /home/tsm/Tools/vmware-tools-distrib
6、输入
./vmware-install.pl进行安装,在安装过程中根据提示进行选择,在此我一路选择回车即可,周详安装过程如下:

None of the pre-built vmmon modules for VMware Workstation is suitable
for your running kernel. Do you want this program to try to build the
vmmon module for your system (you need to have a C compiler installed on
your system)? [yes] yes

  一.RHEL版本的VMWare的安装

在此时最好用root高级用户操作

Using compiler “/usr/bin/gcc”. Use environment variable CC to
override.

    可以从官网下载安装程序,VMWare Server是免费的,你可以从看到相关说明

su
[root@tsmpc vmware-tools-distrib]# ./vmware-install.pl,
Creating a new VMware Tools installer database using the tar4 format.
Installing VMware Tools.
In which directory do you want to install the binary files? 
[/home/tsm/software] 
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? 
[/home/tsm/sbin] 
The path “/home/tsm/sbin” does not exist currently. This program is
going to 
create it, including needed parent directories. Is this what you
want? 
[yes]    
In which directory do you want to install the library files? 
[/home/tsm/lib/vmware-tools] 
The path “/home/tsm/lib/vmware-tools” does not exist currently. This
program is
going to create it, including needed parent directories. Is this what
you want?
[yes] 
In which directory do you want to install the documentation files? 
[/home/tsm/doc/vmware-tools] 
The path “/home/tsm/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 6.0.2 build-59824 for Linux
completed 
successfully. You can decide to remove this software from your system at
any 
time by invoking the following command: 
“/home/tsm/software/vmware-uninstall-tools.pl”.
Before running VMware Tools for the first time, you need to configure it
by 
invoking the following command:
“/home/tsm/software/vmware-config-tools.pl”. Do
you want this program to invoke the command for you now? [yes] 
Stopping VMware Tools services in the virtual machine:
   Guest operating system daemon:                          [确定]
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? [/lib/modules/2.6.23.1-42.fc8/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.23.1-42.fc8/build/include/.. SUBDIRS=$PWD
SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.23.1-42.fc8-i686’
  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 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.23.1-42.fc8-i686’
cp -f vmmemctl.ko ./../vmmemctl.o
make: Leaving directory `/tmp/vmware-config0/vmmemctl-only’
The module loads perfectly in the running kernel.
Trying to find a suitable vmhgfs module for your 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.23.1-42.fc8/build/include/.. SUBDIRS=$PWD
SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.23.1-42.fc8-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/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 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.23.1-42.fc8-i686’
cp -f vmhgfs.ko ./../vmhgfs.o
make: Leaving directory `/tmp/vmware-config0/vmhgfs-only’
The module loads perfectly in the running kernel.
pcnet32                31429  0 
Unloading pcnet32 module
Trying to find a suitable vmxnet module for your 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.23.1-42.fc8/build/include/.. SUBDIRS=$PWD
SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.23.1-42.fc8-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.23.1-42.fc8-i686’
cp -f vmxnet.ko ./../vmxnet.o
make: Leaving directory `/tmp/vmware-config0/vmxnet-only’
The module loads perfectly in the running kernel.
Trying to find a suitable vmblock module for your 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] 
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 /lib/modules/2.6.23.1-42.fc8/build/include/.. SUBDIRS=$PWD
SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/kernels/2.6.23.1-42.fc8-i686’
  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
必发88官网,  LD [M]  /tmp/vmware-config0/vmblock-only/vmblock.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-config0/vmblock-only/vmblock.mod.o
  LD [M]  /tmp/vmware-config0/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.23.1-42.fc8-i686’
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] 
Detected X.org version 1.3.
No drivers for X.org version: 1.3.
Please choose one of the following display sizes that X will start with
(1 – 
15):
[1]  “640×480”
[2]< “800×600”
[3]  “1024×768”
[4]  “1152×864”
[5]  “1280×800”
[6]  “1152×900”
[7]  “1280×1024”
[8]  “1376×1032”
[9]  “1400×900”
[10]  “1400×1050”
[11]  “1440×900”
[12]  “1680×1050”
[13]  “1600×1200”
[14]  “1920×1200”
[15]  “2364×1773”
Please enter a number between 1 and 15:
[2] 3
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:                       [确定]
   Blocking file system:                                   [确定]
   DMA setup:                                              [确定]
   Guest operating system daemon:                          [确定]
/etc/rc.d/init.d/vmware-tools: line 822: vmware-guestd: command not
found
The configuration of VMware Tools 6.0.2 build-59824 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: 
“/home/tsm/software/vmware-toolbox” during an X server 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
To make use of the virtual printer, you will need to restart the CUPS
service
Enjoy,
–the VMware team

What is the location of the directory of C header files that match your
running kernel? [/usr/src/linux/include]

    

这是在网上的方法,当我自己装的过程的出现 the path “” is not valid 
然后是否改变路径,按回车后一直循环,解决方法:

然后系统就找不到/usr/src/linux/include这个目录,终于找了解决办法。出现这种问题是因为缺少一个文件linux-headers,不过用如下一个vmware的补丁就可以解决了:vmware-any-any-update109.tar.gz。

    我使用提 VMware-server-1.0.10-203137.i386.rpm这个安装包.

有两种方法可以供楼主选择:
1、在终端中执行su命令,然后按提示输入密码,获取root权限,然后分别执行下列命令:
(这里内核版本号可能有所不同,要在终端中执行uname -r查看当前内核版本)
cd /usr/src/linux-headers-2.6.35-22-generic/include
cp -p generated/utsrelease.h linux/utsrelease.h
cp -p generated/autoconf.h linux/autoconf.h
再重新安装vmware tools2、进入终端,执行:
sudo -s
cd /lib/modules/$(uname -r)/build/include/linux
ln -s ../generated/utsrelease.h
ln -s ../generated/autoconf.h
再重新安装vmware tools即可。

他的下载地址:wget

    

出现本人用第一种方法安装出现

在要求输入[/usr/src/linux/include]时,用ctul+c断开,然后安装vmware-any-any-update109.tar.gz

    在命令行下执行如下命令安装

Ubuntu VMware tools make: *** [vsock.ko] 错误 2

#tar zxvf vmware-any-any-update109.tar.gz

      rpm -ivh VMware-server-1.0.10-203137.i386.rpm 

没解决,网上结论vm版本问题,需下载高级版本。]

#cd vmware-any-any-update109

   Preparing…              
 ###########################################
[100%]

#./runme.pl必发88官网 1

   1:VMware-server        
 ###########################################
[100%]

  

   

    成功后,直接执行vmware,第一次运行提醒需要运行vmware-config.pl
进行配置.

  1. [root@hxy tools]# vmware
  2. vmware is installed, but it has not been (correctly) configured
  3. for this system. To (re-)configure it, invoke the following command:
  4. /usr/bin/vmware-config.pl.

      

   配置过程,主要都采用缺省值

     

  1. [root@hxy tools]# /usr/bin/vmware-config.pl
  2. Making sure services for VMware Server are stopped.
    1. Stopping VMware services:
  3. Virtual machine monitor [ OK ]
    1. You must read and accept the End User License Agreement to
      continue.
  4. Press enter to display it.
    1. Do you accept? (yes/no) yes
    1. Thank you.
    1. Configuring fallback GTK+ 2.4 libraries.
    1. In which directory do you want to install the mime type icons?
  5. [/usr/share/icons]
      1. What directory contains your desktop menu entry files? These
        files have a
  6. .desktop file extension. [/usr/share/applications]
      1. In which directory do you want to install the application’s
        icon?
  7. [/usr/share/pixmaps]

   

接下来编译了VMMon模块

  1. Trying to find a suitable vmmon module for your running kernel.
    1. None of the pre-built vmmon modules for VMware Server is
      suitable for your
  2. running kernel. Do you want this program to try to build the vmmon
    module for
  3. your system (you need to have a C compiler installed on your
    system)? [yes]
          1. Trying to find a suitable vmmon module for your
            running kernel.
    1. None of the pre-built vmmon modules for VMware Server is
      suitable for your
  4. running kernel. Do you want this program to try to build the vmmon
    module for
  5. your system (you need to have a C compiler installed on your
    system)? [yes] yes
    1. Using compiler “/usr/bin/gcc”. Use environment variable CC to
      override.
    1. What is the location of the directory of C header files that
      match your running
  6. kernel? [/lib/modules/2.6.18-194.el5/build/include]
    1. Extracting the sources of the vmmon module.
    1. tar: vmmon-only/linux/driver.h: time stamp 2009-10-21 05:06:44
      is 183125436 s in the future
  7. tar: vmmon-only/linux/driver.c: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  8. tar: vmmon-only/linux/hostif.c: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  9. tar: vmmon-only/linux/vmmonInt.h: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  10. tar: vmmon-only/linux/vmhost.h: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  11. tar: vmmon-only/linux: time stamp 2009-10-21 05:06:44 is 183125436 s
    in the future
  12. tar: vmmon-only/common/memtrack.c: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  13. tar: vmmon-only/common/memtrack.h: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  14. tar: vmmon-only/common/task.c: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  15. tar: vmmon-only/common/task.h: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  16. tar: vmmon-only/common/vmx86.c: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  17. tar: vmmon-only/common/vmx86.h: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  18. tar: vmmon-only/common/hostif.h: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  19. tar: vmmon-only/common/hostKernel.h: time stamp 2009-10-21 05:06:44
    is 183125436 s in the future
  20. tar: vmmon-only/common/phystrack.c: time stamp 2009-10-21 05:06:44
    is 183125436 s in the future
  21. tar: vmmon-only/common/phystrack.h: time stamp 2009-10-21 05:06:44
    is 183125436 s in the future
  22. tar: vmmon-only/common/cpuid.c: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  23. tar: vmmon-only/common/cpuid.h: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  24. tar: vmmon-only/common/hash.c: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  25. tar: vmmon-only/common: time stamp 2009-10-21 05:06:44 is 183125436
    s in the future
  26. tar: vmmon-only/vmcore/driver_vmcore.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  27. tar: vmmon-only/vmcore/moduleloop.c: time stamp 2009-10-21 05:06:44
    is 183125436 s in the future
  28. tar: vmmon-only/vmcore: time stamp 2009-10-21 05:06:44 is 183125436
    s in the future
  29. tar: vmmon-only/include/initblock.h: time stamp 2009-10-21 05:06:44
    is 183125436 s in the future
  30. tar: vmmon-only/include/machine.h: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  31. tar: vmmon-only/include/modulecall.h: time stamp 2009-10-21 05:06:44
    is 183125436 s in the future
  32. tar: vmmon-only/include/vm_asm.h: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  33. tar: vmmon-only/include/vm_asm_x86.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  34. tar: vmmon-only/include/vm_asm_x86_64.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  35. tar: vmmon-only/include/vm_time.h: time stamp 2009-10-21 05:06:44
    is 183125436 s in the future
  36. tar: vmmon-only/include/vcpuset.h: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  37. tar: vmmon-only/include/x86.h: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  38. tar: vmmon-only/include/x86types.h: time stamp 2009-10-21 05:06:44
    is 183125436 s in the future
  39. tar: vmmon-only/include/x86desc.h: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  40. tar: vmmon-only/include/x86apic.h: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  41. tar: vmmon-only/include/x86vt.h: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  42. tar: vmmon-only/include/vmm_constants.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  43. tar: vmmon-only/include/contextinfo.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  44. tar: vmmon-only/include/uccostTable.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  45. tar: vmmon-only/include/x86cpuid.h: time stamp 2009-10-21 05:06:44
    is 183125436 s in the future
  46. tar: vmmon-only/include/speaker_reg.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  47. tar: vmmon-only/include/vmware.h: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  48. tar: vmmon-only/include/vm_assert.h: time stamp 2009-10-21 05:06:44
    is 183125436 s in the future
  49. tar: vmmon-only/include/vm_atomic.h: time stamp 2009-10-21 05:06:44
    is 183125436 s in the future
  50. tar: vmmon-only/include/vm_basic_asm.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  51. tar: vmmon-only/include/vm_basic_asm_x86.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  52. tar: vmmon-only/include/vm_basic_asm_x86_64.h: time stamp
    2009-10-21 05:06:44 is 183125436 s in the future
  53. tar: vmmon-only/include/vm_basic_defs.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  54. tar: vmmon-only/include/vm_basic_types.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  55. tar: vmmon-only/include/vcpuid.h: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  56. tar: vmmon-only/include/iocontrols.h: time stamp 2009-10-21 05:06:44
    is 183125436 s in the future
  57. tar: vmmon-only/include/pshare_ext.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  58. tar: vmmon-only/include/cpuid_info.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  59. tar: vmmon-only/include/vmware_pack_init.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  60. tar: vmmon-only/include/vmware_pack_begin.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  61. tar: vmmon-only/include/vmware_pack_end.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  62. tar: vmmon-only/include/driver-config.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  63. tar: vmmon-only/include/compat_highmem.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  64. tar: vmmon-only/include/compat_pgtable.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  65. tar: vmmon-only/include/compat_spinlock.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  66. tar: vmmon-only/include/compat_uaccess.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  67. tar: vmmon-only/include/compat_mm.h: time stamp 2009-10-21 05:06:44
    is 183125436 s in the future
  68. tar: vmmon-only/include/compat_file.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  69. tar: vmmon-only/include/compat_wait.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  70. tar: vmmon-only/include/compat_page.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  71. tar: vmmon-only/include/compat_version.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  72. tar: vmmon-only/include/compat_timer.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  73. tar: vmmon-only/include/compat_semaphore.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  74. tar: vmmon-only/include/compat_sched.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  75. tar: vmmon-only/include/compat_kernel.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  76. tar: vmmon-only/include/compat_completion.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  77. tar: vmmon-only/include/pgtbl.h: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  78. tar: vmmon-only/include/hash.h: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  79. tar: vmmon-only/include/includeCheck.h: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  80. tar: vmmon-only/include: time stamp 2009-10-21 05:06:44 is 183125436
    s in the future
  81. tar: vmmon-only/autoconf/geninclude.c: time stamp 2009-10-21
    05:06:44 is 183125436 s in the future
  82. tar: vmmon-only/autoconf/nopage1.c: time stamp 2009-10-21 05:06:44
    is 183125436 s in the future
  83. tar: vmmon-only/autoconf/skas1.c: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  84. tar: vmmon-only/autoconf/epoll.c: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  85. tar: vmmon-only/autoconf/setnice.c: time stamp 2009-10-21 05:06:44
    is 183125436 s in the future
  86. tar: vmmon-only/autoconf: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  87. tar: vmmon-only/Makefile.normal: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  88. tar: vmmon-only/Makefile.kernel: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  89. tar: vmmon-only/README: time stamp 2009-10-21 05:06:44 is 183125436
    s in the future
  90. tar: vmmon-only/Makefile: time stamp 2009-10-21 05:06:44 is
    183125436 s in the future
  91. tar: vmmon-only: time stamp 2009-10-21 05:06:44 is 183125436 s in
    the future
  92. Building the vmmon module.
    1. Using 2.6.x kernel build system.
  93. make: Entering directory `/tmp/vmware-config0/vmmon-only’
  94. make: Warning: File `Makefile.kernel’ has modification time
    1.8e+08 s in the future
  95. make -C /lib/modules/2.6.18-194.el5/build/include/.. SUBDIRS=$PWD
    SRCROOT=$PWD/. modules
  96. make[1]: Entering directory
    `/usr/src/kernels/2.6.18-194.el5-i686′
  97. make[1]: Warning: File
    `/usr/src/kernels/2.6.18-194.el5-i686/arch/i386/Makefile.cpu’ has
    modification time 2e+08 s in the future
  98. make[2]: Warning: File `scripts/Makefile.lib’ has modification
    time 8.6e+07 s in the future
  99. CC [M] /tmp/vmware-config0/vmmon-only/linux/driver.o
  100. CC [M] /tmp/vmware-config0/vmmon-only/linux/hostif.o
  101. CC [M] /tmp/vmware-config0/vmmon-only/common/cpuid.o
  102. CC [M] /tmp/vmware-config0/vmmon-only/common/hash.o
  103. CC [M] /tmp/vmware-config0/vmmon-only/common/memtrack.o
  104. CC [M] /tmp/vmware-config0/vmmon-only/common/phystrack.o
  105. CC [M] /tmp/vmware-config0/vmmon-only/common/task.o
  106. CC [M] /tmp/vmware-config0/vmmon-only/common/vmx86.o
  107. CC [M] /tmp/vmware-config0/vmmon-only/vmcore/moduleloop.o
  108. LD [M] /tmp/vmware-config0/vmmon-only/vmmon.o
  109. make[2]: warning: Clock skew detected. Your build may be
    incomplete.
  110. Building modules, stage 2.
  111. make[2]: Warning: File `scripts/Makefile.lib’ has modification
    time 8.6e+07 s in the future
  112. MODPOST
  113. CC /tmp/vmware-config0/vmmon-only/vmmon.mod.o
  114. LD [M] /tmp/vmware-config0/vmmon-only/vmmon.ko
  115. make[2]: warning: Clock skew detected. Your build may be
    incomplete.
  116. make[1]: warning: Clock skew detected. Your build may be
    incomplete.
  117. make[1]: Leaving directory
    `/usr/src/kernels/2.6.18-194.el5-i686′
  118. cp -f vmmon.ko ./../vmmon.o
  119. make: warning: Clock skew detected. Your build may be incomplete.
  120. make: Leaving directory `/tmp/vmware-config0/vmmon-only’
  121. The module loads perfectly in the running kernel.

 配置网络,这里强烈建议选择一个桥接,一个HOST
Only,这是做嵌入式开发必须的配置双网卡配置.

  1. Do you want networking for your virtual machines? (yes/no/help)
    [yes]
      1. Configuring a bridged network for vmnet0.
    1. Your computer has multiple ethernet network interfaces
      available: eth0, eth1.
  2. Which one do you want to bridge to vmnet0? [eth0] eth0
    1. The following bridged networks have been defined:
    1. . vmnet0 is bridged to eth0
    1. Do you wish to configure another bridged network? (yes/no)
      [no]
      1. Do you want to be able to use NAT networking in your virtual
        machines? (yes/no)
  3. [yes] no
    1. Do you want to be able to use host-only networking in your
      virtual machines?
  4. [no] yes
    1. Configuring a host-only network for vmnet1.
    1. Do you want this program to probe for an unused private subnet?
      (yes/no/help)
  5. [yes]
    1. Probing for an unused private subnet (this can take some
      time)…

必发88官网 2

相关文章