虛擬機VMware與主機共享文件介紹

時間 2019-12-02

原文原文鏈接

咱們常常會在Windows平臺安裝虛擬機VMware，無論是出於實驗測試仍是工做須要，伴隨而來的就是常常須要在Windows系統和虛擬機系統之間進行共享數據文件，例如，須要將Window主機上的Oracle安裝鏡像文件拷貝到VMware上的Linux系統下....諸如此類需求，二者之間共享數據文件的方法其實蠻多的，下面介紹幾種比較經常使用的共享文件方法(有些詳細介紹、有些略有介紹): node

1: 經過FTP共享文件數據 linux

使用這類方法共享文件數據，一般虛擬機系統是Linux操做系統，固然Windows系統也同樣。前提條件是其中一個必須安裝有FTP組件。例如以下所示：網絡

本機Windows 7 64位專業版，虛擬機Oracle Linux 5.7，我若是想將主機的文件拷貝到Oracle Linux 5.7,我能夠經過SecureCRT下的STFP進行數據文件的拷貝傳輸。固然你也能夠利用FTP軟件進行數據文件傳輸。在此不作細說。若是虛擬機是Windows系統，能夠在主機或虛擬機安裝FileZilla FTP Client之類的FTP軟件來實現FTP共享文件數據。 session

2：經過共享文件夾功能 app

虛擬機VMware提供了在宿主機與虛擬機系統之間交換文件的共享文件夾（Shared Folder）功能。無論虛擬機操做系統是Linux仍是Windows均可用。你能夠經過設置（ Settings）>共享文件夾（Shared Folder）來設置。可是此功能選項必需要安裝虛擬機工具（VMware Tools），不然以下所示，不然該功能選項不可用。 ssh

安裝虛擬機工具步驟以下所示： socket

1：在對應虛擬機的設置選項（Settings)下，爲虛擬機光驅指定虛擬機系統的鏡像文件。注意：在執行下面步驟前，必須確保虛擬機的電源開啓、虛擬機系統正在運行。 tcp

2：在VM下選擇"Install VMware Tools". ide

而後安裝虛擬機組件工具，詳細步驟以下所示：工具

 
  [root@DB-Server ~]# cd /mnt 
   
  [root@DB-Server mnt]# mkdir cdrom 
   
  [root@DB-Server mnt]# mount /dev/cdrom  /mnt/cdrom 
   
  [root@DB-Server mnt]# cd /mnt/cdrom 
   
  [root@DB-Server cdrom]# cp  VMwareTools-8.8.2-590212.tar.gz /tmp 
   
  [root@DB-Server cdrom]#tar xz 
   
  [root@DB-Server tmp]# ls 
   
  gconfd-root     orbit-root           VMwareTools-8.8.2-590212.tar.gz 
   
  keyring-qO15Cg  ssh-EWUeHQ4064       vmware-tools-distrib 
   
  mapping-root    virtual-root.9mZzaq 
   
  [root@DB-Server tmp]# cd vmware-tools-distrib/ 
   
  [root@DB-Server vmware-tools-distrib]# ls 
   
  bin  doc  etc  FILES  INSTALL  installer  lib  vmware-install.pl 
   
  [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

官網關於手工安裝升級虛擬機的文檔以下所示：

 
  Manually Install or Upgrade VMware Tools in a Linux Virtual Machine 
   
  For Linux virtual machines, you manually install or upgrade VMware Tools by using the command line. 
   
  Install the latest version of VMware Tools to enhance the performance of the virtual machine's guest operating system and improve virtual machine management. When you power on a virtual machine, if a new version of VMware Tools is available, you see a notification in the status bar of the guest operating system. 
   
  Prerequisites 
   
  ■ Power on the virtual machine.  
   
  ■ Verify that the guest operating system is running.  
   
  ■ Because the VMware Tools installer is written in Perl, verify that Perl is installed in the guest operating system.  
   
  Procedure 
   
  1 On the host, from the Workstation menu bar, select VM > Manage > Install VMware Tools.  
   
  If an earlier version of VMware Tools is installed, the menu item is Update VMware Tools. 
   
  2 In the virtual machine, log in to the guest operating system as root and open a terminal window.  
   
  3 Run the mount command with no arguments to determine whether your Linux distribution automatically mounted the VMware Tools virtual CD-ROM image.  
   
  If the CD-ROM device is mounted, the CD-ROM device and its mount point are listed as something like this: 
   
  /dev/cdrom on /mnt/cdrom type iso9660 (ro,nosuid,nodev)4 If the VMware Tools virtual CD-ROM image is not mounted, mount the CD-ROM drive.  
   
  a If a mount point directory does not already exist, create it.  
   
  mkdir /mnt/cdromSome Linux distributions use different mount point names. For example, on some distributions the mount point is /media/VMware Tools rather than /mnt/cdrom. Modify the command to reflect the conventions that your distribution uses. 
   
  b Mount the CD-ROM drive.  
   
  mount /dev/cdrom /mnt/cdromSome Linux distributions use different device names or organize the /dev directory differently. If your CD-ROM drive is not /dev/cdrom or if the mount point for a CD-ROM is not /mnt/cdrom, modify the command to reflect the conventions that your distribution uses. 
   
  5 Change to a working directory (for example, /tmp).  
   
  cd /tmp 
   
  6 Delete any previous vmware-tools-distrib directory before you install VMware Tools.  
   
  The location of this directory depends on where you placed it during the previous installation. Often this directory is placed in /tmp/vmware-tools-distrib. 
   
  7 List the contents of the mount point directory and note the filename of the VMware Tools tar installer.  
   
  ls mount-point8 Uncompress the installer.  
   
  tar zxpf /mnt/cdrom/VMwareTools-x.x.x-yyyy.tar.gzThe value x.x.x is the product version number, and yyyy is the build number of the product release. 
   
  If you attempt to install a tar installation over an RPM installation, or the reverse, the installer detects the previous installation and must convert the installer database format before continuing. 
   
  9 If necessary, unmount the CD-ROM image.  
   
  umount /dev/cdrom If your Linux distribution automatically mounted the CD-ROM, you do not need to unmount the image. 
   
  10 Run the installer and configure VMware Tools.  
   
  cd vmware-tools-distrib./vmware-install.plUsually, the vmware-config-tools.pl configuration file runs after the installer file finishes running. 
   
  11 Respond to the prompts by pressing Enter to accept the default values, if appropriate for your configuration.  
   
  12 Follow the instructions at the end of the script.  
   
  Depending on the features you use, these instructions can include restarting the X session, restarting networking, logging in again, and starting the VMware User process. You can alternatively reboot the guest operating system to accomplish all these tasks. 
   
  What to do next 
   
  If a new virtual hardware version is available for the virtual machine, upgrade the virtual hardware.

而後在Options > Shared Folders下選擇「Always enabled"選項。固然你也能夠選擇"Enabled until next power off or suspend"選項

此時在/mnt/hgfs下就會有一個tmp目錄，在主機往E:\VMWARE下拷貝文件就能在Linux系統/mnt/hgfs/tmp目錄下訪問這些文件了。

對於虛擬機系統是Windows平臺的，能夠以下設置。而後接下來也是一些你們所熟知的基本配置.

3：組建局域網共享文件夾

此方法適用於虛擬機系統爲Windows系統。網上有比較多的資料,都是一些基本配置,弄起來也有一些麻煩.感受沒啥能夠說的.在此略過.

4：利用虛擬光驅共享文件

這種方法有點奇葩，第一次見到這種共享文件的方法，我當時的反應就是竟然能夠這樣共享文件。其實就是利用軟件將文件打包成鏡像文件，而後在虛擬機設置（Settings）——「CD/DVD（IDE）」裏面指定ISO鏡像文件位置。這種方法適用於虛擬機系統是Linux、Windows系統。不足之處就是隻能從主機拷貝文件到虛擬機，不能從虛擬機拷貝文件到主機，並且折騰起來至關麻煩。

5：利用網盤實現共享文件

這個是我在論壇裏面看到的一種方法，沒有嘗試過。這種方法只適用於小文件的共享，大文件共享適用這類方法不太合適。畢竟網絡傳輸是瓶頸.