虚拟机VMware与主机共享文件介绍-阿里云开发者社区

我们经常会在 Windows平台安装虚拟机VMware，不管是出于实验测试还是工作需要，伴随而来的就是经常需要在Windows系统和虚拟机系统之间进行共享数据文件，例如，需要将Window主机上的Oracle安装镜像文件拷贝到VMware上的Linux系统下....诸如此类需求，两者之间共享数据文件的方法其实蛮多的，下面介绍几种比较常用的共享文件方法(有些详细介绍、有些略有介绍):

1: 通过FTP共享文件数据

使用这类方法共享文件数据，通常虚拟机系统是Linux操作系统，当然Windows系统也一样。前提条件是其中一个必须安装有FTP组件。例如如下所示：

本机Windows 7 64位专业版，虚拟机Oracle Linux 5.7，我如果想将主机的文件拷贝到Oracle Linux 5.7,我可以通过SecureCRT下的STFP进行数据文件的拷贝传输。当然你也可以利用FTP软件进行数据文件传输。在此不做细说。如果虚拟机是 Windows系统，可以在主机或虚拟机安装FileZilla FTP Client之类的FTP软件来实现FTP共享文件数据。

clip_image001

2：通过共享文件夹功能

虚拟机VMware提供了在宿主机与虚拟机系统之间交换文件的共享文件夹（Shared Folder）功能。不管虚拟机操作系统是Linux还是Windows都可用。你可以通过设置（ Settings）>共享文件夹（Shared Folder）来设置。但是此功能选项必须要安装虚拟机工具（VMware Tools），否则如下所示，否则该功能选项不可用。

clip_image002

安装虚拟机工具步骤如下所示：

1：在对应虚拟机的设置选项（Settings)下，为虚拟机光驱指定虚拟机系统的镜像文件。注意：在执行下面步骤前，必须确保虚拟机的电源开启、虚拟机系统正在运行。

clip_image003

2：在VM下选择"Install VMware Tools".

clip_image004

然后安装虚拟机组件工具，详细步骤如下所示：

 
   [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"选项

clip_image005

clip_image006

clip_image007

clip_image008

clip_image009

此时在/mnt/hgfs下就会有一个tmp目录，在主机往E:\VMWARE下拷贝文件就能在Linux系统/mnt/hgfs/tmp目录下访问这些文件了。

对于虚拟机系统是Windows平台的，可以如下设置。然后接下来也是一些大家所熟知的基本配置.

clip_image010

3：组建局域网共享文件夹

此方法适用于虚拟机系统为Windows系统。网上有比较多的资料,都是一些基本配置,弄起来也有一些麻烦.感觉没啥可以说的.在此略过.

4：利用虚拟光驱共享文件

这种方法有点奇葩，第一次见到这种共享文件的方法，我当时的反应就是居然可以这样共享文件。其实就是利用软件将文件打包成镜像文件，然后在虚拟机设置（Settings）——“CD/DVD（IDE）”里面指定ISO镜像文件位置。这种方法适用于虚拟机系统是Linux、Windows系统。不足之处就是只能从主机拷贝文件到虚拟机，不能从虚拟机拷贝文件到主机，而且折腾起来相当麻烦。

clip_image011

5：利用网盘实现共享文件

这个是我在论坛里面看到的一种方法，没有尝试过。这种方法只适用于小文件的共享，大文件共享适用这类方法不太合适。毕竟网络传输是瓶颈.

虚拟机VMware与主机共享文件介绍

热门文章

最新文章

相关课程

相关电子书

相关实验场景