VMware Tools is a group of utilities that enhances the overall performance of the virtual machine\u2019s guest operating system (OS) and improves management of the virtual machine (VM). This is one of important components in order to provide perfect VM OS. Without the VMware Tools, guest OS performance will lacks some of the important functionality. Please follow below steps to install the VMware Tools on CentOS 6.3:<\/p>\n
1. Install prerequisites :<\/p>\n
\n[root@centos63 ~]# yum install perl gcc make kernel-headers kernel-devel -y\n<\/pre>\n2. Right click on the VM, goto Guest, Install\/Upgrade VMware tools.<\/p>\n
3. Mount VMware-tool installer :<\/p>\n
\n[root@centos63 ~]# mount \/dev\/cdrom \/mnt\nmount: block device \/dev\/sr0 is write-protected, mounting read-only\n<\/pre>\n4. Extract and install :<\/p>\n
\n[root@centos63 ~]# cd \/mnt\n[root@centos63 mnt]# cp VMwareTools-2.0.0-122956.tar.gz \/tmp\n[root@centos63 mnt]# cd \/tmp\n[root@centos63 tmp]# umount \/mnt\n[root@centos63 tmp]# tar xzvf VMwareTools-2.0.0-122956.tar.gz\n[root@centos63 tmp]# cd vmware-tools-distrib\n[root@centos63 vmware-tools-distrib]# .\/vmware-install.pl\n<\/pre>\nDuring the installation wizard, just press enter for default selection. For certain cases, you will get stuck on the following :<\/p>\n
\n..\n..\n..\n..\nStopping VMware Tools services in the virtual machine:\n Guest operating system daemon: [ OK ]\nNone of the pre-built vmmemctl modules for VMware Tools is suitable for your\nrunning kernel. Do you want this program to try to build the vmmemctl module\nfor your system (you need to have a C compiler installed on your system)?\n[yes]\n\nUsing compiler \"\/usr\/bin\/gcc\". Use environment variable CC to override.\n\nWhat is the location of the directory of C header files that match your running\nkernel? [\/usr\/src\/linux\/include]\n<\/pre>\nSolution :<\/strong><\/p>\n
What you can do is perform kernel updates, then reboot and finally re-run the VMware-tools installation script.<\/p>\n
Steps<\/strong>
\n1. Perform update to kernel :<\/p>\n\n[root@centos63 vmware-tools-distrib]# yum update kernel -y\nLoaded plugins: fastestmirror, presto\nLoading mirror speeds from cached hostfile\n * base: mirrors.hostemo.com\n * extras: mirrors.hostemo.com\n * updates: mirrors.hostemo.com\nfile:\/\/\/mnt\/repodata\/repomd.xml: [Errno 14] Could not open\/read file:\/\/\/mnt\/repodata\/repomd.xml\nTrying other mirror.\nSetting up Update Process\nResolving Dependencies\n--> Running transaction check\n---> Package kernel.i686 0:2.6.32-279.1.1.el6 will be installed\n--> Processing Dependency: kernel-firmware >= 2.6.32-279.1.1.el6 for package: kernel-2.6.32-279.1.1.el6.i686\n--> Running transaction check\n---> Package kernel-firmware.noarch 0:2.6.32-279.el6 will be updated\n---> Package kernel-firmware.noarch 0:2.6.32-279.1.1.el6 will be an update\n--> Finished Dependency Resolution\n\nDependencies Resolved\n\n====================================================================================================\n Package Arch Version Repository Size\n====================================================================================================\nInstalling:\n kernel i686 2.6.32-279.1.1.el6 updates 23 M\nUpdating for dependencies:\n kernel-firmware noarch 2.6.32-279.1.1.el6 updates 8.7 M\n\nTransaction Summary\n====================================================================================================\nInstall 1 Package(s)\nUpgrade 1 Package(s)\n\nTotal download size: 32 M\nDownloading Packages:\nSetting up and reading Presto delta metadata\nupdates\/prestodelta | 41 kB 00:00\nProcessing delta metadata\nDownload delta size: 6.8 M\n(1\/2): kernel-2.6.32-279.el6_2.6.32-279.1.1.el6.i686.drpm | 5.6 MB 00:49\n(2\/2): kernel-firmware-2.6.32-279.el6_2.6.32-279.1.1.el6.noarch.drpm | 1.2 MB 00:11\nFinishing rebuild of rpms, from deltarpms\n| 32 MB 00:20\nPresto reduced the update size by 79% (from 32 M to 6.8 M).\nRunning rpm_check_debug\nRunning Transaction Test\nTransaction Test Succeeded\nRunning Transaction\n Updating : kernel-firmware-2.6.32-279.1.1.el6.noarch 1\/3\n Installing : kernel-2.6.32-279.1.1.el6.i686 2\/3\n Cleanup : kernel-firmware-2.6.32-279.el6.noarch 3\/3\n Verifying : kernel-firmware-2.6.32-279.1.1.el6.noarch 1\/3\n Verifying : kernel-2.6.32-279.1.1.el6.i686 2\/3\n Verifying : kernel-firmware-2.6.32-279.el6.noarch 3\/3\n\nInstalled:\n kernel.i686 0:2.6.32-279.1.1.el6\n\nDependency Updated:\n kernel-firmware.noarch 0:2.6.32-279.1.1.el6\n\nComplete!\n<\/pre>\n 2. Reboot the CentOS 6.3<\/p>\n
3. Re-run VMware-Tools installation :<\/p>\n
\n[root@centos63 vmware-tools-distrib]# .\/vmware-install.pl\nA previous installation of VMware Tools has been detected.\n\nThe previous installation was made by the tar installer (version 4).\n\nKeeping the tar4 installer database format.\n\nYou have a version of VMware Tools installed. Continuing this install will\nfirst uninstall the currently installed version. Do you wish to continue?\n(yes\/no) [yes]\n\nUninstalling the tar installation of VMware Tools.\n\nStopping services for VMware Tools\n\nStopping VMware Tools services in the virtual machine:\n Guest operating system daemon: [ OK ]\n\nFile \/usr\/lib\/vmware-tools\/lib32\/libconf\/etc\/pango\/pangorc is backed up to\n\/usr\/lib\/vmware-tools\/lib32\/libconf\/etc\/pango\/pangorc.old.2.\n\nThis program previously created the file\n\/usr\/lib\/vmware-tools\/libconf\/etc\/gtk-2.0\/gtk.immodules, and was about to\nremove it. Somebody else apparently did it already.\n\nFile \/usr\/lib\/vmware-tools\/lib32\/libconf\/etc\/pango\/pangox.aliases is backed up\nto \/usr\/lib\/vmware-tools\/lib32\/libconf\/etc\/pango\/pangox.aliases.old.2.\n\nFile \/usr\/lib\/vmware-tools\/lib32\/libconf\/etc\/gtk-2.0\/gdk-pixbuf.loaders is\nbacked up to\n\/usr\/lib\/vmware-tools\/lib32\/libconf\/etc\/gtk-2.0\/gdk-pixbuf.loaders.old.2.\n\nThis program previously created the file\n\/usr\/lib\/vmware-tools\/libconf\/etc\/pango\/pangorc, and was about to remove it.\nSomebody else apparently did it already.\n\nThis program previously created the file\n\/usr\/lib\/vmware-tools\/libconf\/etc\/pango\/pangox.aliases, and was about to remove\nit. Somebody else apparently did it already.\n\nThis program previously created the file\n\/usr\/lib\/vmware-tools\/lib32\/libconf\/etc\/pango\/pango.modules, and was about to\nremove it. Somebody else apparently did it already.\n\nThis program previously created the file\n\/usr\/lib\/vmware-tools\/libconf\/etc\/gtk-2.0\/gdk-pixbuf.loaders, and was about to\nremove it. Somebody else apparently did it already.\n\nFile \/usr\/lib\/vmware-tools\/lib32\/libconf\/etc\/gtk-2.0\/gtk.immodules is backed up\nto \/usr\/lib\/vmware-tools\/lib32\/libconf\/etc\/gtk-2.0\/gtk.immodules.old.2.\n\nThe removal of VMware Tools 2.0.0 build-122956 for Linux completed\nsuccessfully.\n\nInstalling VMware Tools.\n\nIn which directory do you want to install the binary files?\n[\/usr\/bin]\n\nWhat is the directory that contains the init directories (rc0.d\/ to rc6.d\/)?\n[\/etc\/rc.d]\n\nWhat is the directory that contains the init scripts?\n[\/etc\/rc.d\/init.d]\n\nIn which directory do you want to install the daemon files?\n[\/usr\/sbin]\n\nIn which directory do you want to install the library files?\n[\/usr\/lib\/vmware-tools]\n\n\nIn which directory do you want to install the documentation files?\n[\/usr\/share\/doc\/vmware-tools]\nThe path \"\/usr\/share\/doc\/vmware-tools\" does not exist currently. This program\nis going to create it, including needed parent directories. Is this what you\nwant? [yes]\n\nThe installation of VMware Tools 2.0.0 build-122956 for Linux completed\nsuccessfully. You can decide to remove this software from your system at any\ntime by invoking the following command: \"\/usr\/bin\/vmware-uninstall-tools.pl\".\n\nBefore running VMware Tools for the first time, you need to configure it by\ninvoking the following command: \"\/usr\/bin\/vmware-config-tools.pl\". Do you want\nthis program to invoke the command for you now? [yes]\n\nIt looks like you are trying to run this program in a remote session. This\nprogram will temporarily shut down your network connection, so you should only\nrun it from a local console session. Are you SURE you want to continue?\n[no] yes\n\n\nStopping VMware Tools services in the virtual machine:\n Guest operating system daemon: [ OK ]\nNone of the pre-built vmmemctl modules for VMware Tools is suitable for your\nrunning kernel. Do you want this program to try to build the vmmemctl module\nfor your system (you need to have a C compiler installed on your system)?\n[yes]\n\nUsing compiler \"\/usr\/bin\/gcc\". Use environment variable CC to override.\n\nWhat is the location of the directory of C header files that match your running\nkernel?\n[\/lib\/modules\/2.6.32-279.1.1.el6.i686\/build\/include]\n\nExtracting the sources of the vmmemctl module.\n\nBuilding the vmmemctl module.\n\nUsing 2.6.x kernel build system.\nmake: Entering directory `\/tmp\/vmware-config0\/vmmemctl-only'\nmake -C \/lib\/modules\/2.6.32-279.1.1.el6.i686\/build\/include\/.. SUBDIRS=$PWD SRCROOT=$PWD\/. modules\nmake[1]: Entering directory `\/usr\/src\/kernels\/2.6.32-279.1.1.el6.i686'\n CC [M] \/tmp\/vmware-config0\/vmmemctl-only\/backdoorGcc32.o\nIn file included from \/tmp\/vmware-config0\/vmmemctl-only\/backdoor.h:29,\n from \/tmp\/vmware-config0\/vmmemctl-only\/backdoorGcc32.c:45:\n\/tmp\/vmware-config0\/vmmemctl-only\/vm_basic_types.h:108:7: warning: \"__FreeBSD__\" is not defined\n CC [M] \/tmp\/vmware-config0\/vmmemctl-only\/os.o\nIn file included from \/tmp\/vmware-config0\/vmmemctl-only\/os.c:51:\n\/tmp\/vmware-config0\/vmmemctl-only\/compat_wait.h:78: error: conflicting types for \u00e2poll_initwait\u00e2\ninclude\/linux\/poll.h:70: note: previous declaration of \u00e2poll_initwait\u00e2 was here\nmake[2]: *** [\/tmp\/vmware-config0\/vmmemctl-only\/os.o] Error 1\nmake[1]: *** [_module_\/tmp\/vmware-config0\/vmmemctl-only] Error 2\nmake[1]: Leaving directory `\/usr\/src\/kernels\/2.6.32-279.1.1.el6.i686'\nmake: *** [vmmemctl.ko] Error 2\nmake: Leaving directory `\/tmp\/vmware-config0\/vmmemctl-only'\nUnable to build the vmmemctl module.\n\nThe memory manager driver (vmmemctl module) is used by VMware host software to\nefficiently reclaim memory from a virtual machine.\nIf the driver is not available, VMware host software may instead need to swap\nguest memory to disk, which may reduce performance.\nThe rest of the software provided by VMware Tools is designed to work\nindependently of this feature.\nIf you want the memory management feature, you can install the driver by\nrunning vmware-config-tools.pl again after making sure that gcc, binutils, make\nand the kernel sources for your running kernel are installed on your machine.\nThese packages are available on your distribution's installation CD.\n[ Press Enter key to continue ]\n\nNone of the pre-built vmxnet modules for VMware Tools is suitable for your\nrunning kernel. Do you want this program to try to build the vmxnet module for\nyour system (you need to have a C compiler installed on your system)? [yes]\n\nExtracting the sources of the vmxnet module.\n\nBuilding the vmxnet module.\n\nUsing 2.6.x kernel build system.\nmake: Entering directory `\/tmp\/vmware-config1\/vmxnet-only'\nmake -C \/lib\/modules\/2.6.32-279.1.1.el6.i686\/build\/include\/.. SUBDIRS=$PWD SRCROOT=$PWD\/. modules\nmake[1]: Entering directory `\/usr\/src\/kernels\/2.6.32-279.1.1.el6.i686'\n CC [M] \/tmp\/vmware-config1\/vmxnet-only\/vmxnet.o\nIn file included from \/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c:48:\n\/tmp\/vmware-config1\/vmxnet-only\/vm_basic_types.h:108:7: warning: \"__FreeBSD__\" is not defined\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c: In function \u00e2vmxnet_change_mtu\u00e2:\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c:193: error: \u00e2struct net_device\u00e2 has no member named \u00e2priv\u00e2\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c: In function \u00e2vmxnet_get_drvinfo\u00e2:\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c:267: error: \u00e2struct net_device\u00e2 has no member named \u00e2priv\u00e2\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c: In function \u00e2vmxnet_set_tso\u00e2:\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c:305: error: \u00e2struct net_device\u00e2 has no member named \u00e2priv\u00e2\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c: In function \u00e2vmxnet_link_check\u00e2:\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c:659: error: \u00e2struct net_device\u00e2 has no member named \u00e2priv\u00e2\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c: In function \u00e2vmxnet_probe_device\u00e2:\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c:841: error: \u00e2struct net_device\u00e2 has no member named \u00e2priv\u00e2\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c:993: warning: cast to pointer from integer of different size\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c:1058: error: \u00e2struct net_device\u00e2 has no member named \u00e2open\u00e2\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c:1059: error: \u00e2struct net_device\u00e2 has no member named \u00e2hard_start_xmit\u00e2\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c:1060: error: \u00e2struct net_device\u00e2 has no member named \u00e2stop\u00e2\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c:1061: error: \u00e2struct net_device\u00e2 has no member named \u00e2get_stats\u00e2\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c:1062: error: \u00e2struct net_device\u00e2 has no member named \u00e2set_multicast_list\u00e2\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c:1064: error: \u00e2struct net_device\u00e2 has no member named \u00e2change_mtu\u00e2\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c:1067: error: \u00e2struct net_device\u00e2 has no member named \u00e2tx_timeout\u00e2\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c:1071: error: \u00e2struct net_device\u00e2 has no member named \u00e2poll_controller\u00e2\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c:1075: error: \u00e2struct net_device\u00e2 has no member named \u00e2set_mac_address\u00e2\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c: In function \u00e2vmxnet_remove_device\u00e2:\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c:1142: error: \u00e2struct net_device\u00e2 has no member named \u00e2priv\u00e2\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c: In function \u00e2vmxnet_init_ring\u00e2:\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c:1213: error: \u00e2struct net_device\u00e2 has no member named \u00e2priv\u00e2\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c: In function \u00e2vmxnet_open\u00e2:\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c:1338: error: \u00e2struct net_device\u00e2 has no member named \u00e2priv\u00e2\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c: In function \u00e2check_tx_queue\u00e2:\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c:1594: error: \u00e2struct net_device\u00e2 has no member named \u00e2priv\u00e2\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c: In function \u00e2vmxnet_tx\u00e2:\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c:1658: error: \u00e2struct net_device\u00e2 has no member named \u00e2priv\u00e2\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c: In function \u00e2vmxnet_rx\u00e2:\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c:2057: error: \u00e2struct net_device\u00e2 has no member named \u00e2priv\u00e2\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c: In function \u00e2vmxnet_interrupt\u00e2:\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c:2232: error: \u00e2struct net_device\u00e2 has no member named \u00e2priv\u00e2\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c: In function \u00e2vmxnet_close\u00e2:\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c:2314: error: \u00e2struct net_device\u00e2 has no member named \u00e2priv\u00e2\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c: In function \u00e2vmxnet_load_multicast\u00e2:\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c:2404: error: \u00e2struct net_device\u00e2 has no member named \u00e2priv\u00e2\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c: In function \u00e2vmxnet_set_multicast_list\u00e2:\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c:2465: error: \u00e2struct net_device\u00e2 has no member named \u00e2priv\u00e2\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c: In function \u00e2vmxnet_get_stats\u00e2:\n\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.c:2545: error: \u00e2struct net_device\u00e2 has no member named \u00e2priv\u00e2\nmake[2]: *** [\/tmp\/vmware-config1\/vmxnet-only\/vmxnet.o] Error 1\nmake[1]: *** [_module_\/tmp\/vmware-config1\/vmxnet-only] Error 2\nmake[1]: Leaving directory `\/usr\/src\/kernels\/2.6.32-279.1.1.el6.i686'\nmake: *** [vmxnet.ko] Error 2\nmake: Leaving directory `\/tmp\/vmware-config1\/vmxnet-only'\nUnable to build the vmxnet module.\n\nThe fast network device driver (vmxnet module) is used only for our fast\nnetworking interface. The rest of the software provided by VMware Tools is\ndesigned to work independently of this feature.\nIf you wish to have the fast network driver enabled, you can install the driver\nby running vmware-config-tools.pl again after making sure that gcc, binutils,\nmake and the kernel sources for your running kernel are installed on your\nmachine. These packages are available on your distribution's installation CD.\n[ Press Enter key to continue ]\n\nNone of the pre-built vmblock modules for VMware Tools is suitable for your\nrunning kernel. Do you want this program to try to build the vmblock module\nfor your system (you need to have a C compiler installed on your system)?\n[yes]\n\nExtracting the sources of the vmblock module.\n\nBuilding the vmblock module.\n\nUsing 2.6.x kernel build system.\nmake: Entering directory `\/tmp\/vmware-config2\/vmblock-only'\nmake -C \/lib\/modules\/2.6.32-279.1.1.el6.i686\/build\/include\/.. SUBDIRS=$PWD SRCROOT=$PWD\/. modules\nmake[1]: Entering directory `\/usr\/src\/kernels\/2.6.32-279.1.1.el6.i686'\n CC [M] \/tmp\/vmware-config2\/vmblock-only\/linux\/block.o\nIn file included from \/tmp\/vmware-config2\/vmblock-only\/linux\/os.h:35,\n from \/tmp\/vmware-config2\/vmblock-only\/linux\/block.c:26:\n\/tmp\/vmware-config2\/vmblock-only\/.\/include\/compat_wait.h:78: error: conflicting types for \u00e2poll_initwait\u00e2\ninclude\/linux\/poll.h:70: note: previous declaration of \u00e2poll_initwait\u00e2 was here\nIn file included from \/tmp\/vmware-config2\/vmblock-only\/linux\/vmblockInt.h:40,\n from \/tmp\/vmware-config2\/vmblock-only\/linux\/block.c:29:\n\/tmp\/vmware-config2\/vmblock-only\/.\/include\/vm_basic_types.h:108:7: warning: \"__FreeBSD__\" is not defined\nmake[2]: *** [\/tmp\/vmware-config2\/vmblock-only\/linux\/block.o] Error 1\nmake[1]: *** [_module_\/tmp\/vmware-config2\/vmblock-only] Error 2\nmake[1]: Leaving directory `\/usr\/src\/kernels\/2.6.32-279.1.1.el6.i686'\nmake: *** [vmblock.ko] Error 2\nmake: Leaving directory `\/tmp\/vmware-config2\/vmblock-only'\nUnable to build the vmblock module.\n\nThe vmblock module enables dragging or copying files from within a host and\ndropping or pasting them onto your guest (host to guest drag and drop and file\ncopy\/paste). The rest of the software provided by VMware Tools is designed to\nwork independently of this feature (including guest to host drag and drop and\nfile copy\/paste).\n\nIf you would like the host to guest drag and drop and file copy\/paste features,\nyou can install the driver by running vmware-config-tools.pl again after making\nsure that gcc, binutils, make and the kernel sources for your running kernel\nare installed on your machine. These packages are available on your\ndistribution's installation CD.\n[ Press Enter key to continue ]\n\n[EXPERIMENTAL] The VMware FileSystem Sync Driver (vmsync) is a new feature that\ncreates backups of virtual machines. Please refer to the VMware Knowledge Base\nfor more details on this capability. Do you wish to enable this feature?\n[no]\n\nNone of the pre-built vmci modules for VMware Tools is suitable for your\nrunning kernel. Do you want this program to try to build the vmci module for\nyour system (you need to have a C compiler installed on your system)? [yes]\n\nExtracting the sources of the vmci module.\n\nBuilding the vmci module.\n\nUsing 2.6.x kernel build system.\nmake: Entering directory `\/tmp\/vmware-config3\/vmci-only'\nmake -C \/lib\/modules\/2.6.32-279.1.1.el6.i686\/build\/include\/.. SUBDIRS=$PWD SRCROOT=$PWD\/. modules\nmake[1]: Entering directory `\/usr\/src\/kernels\/2.6.32-279.1.1.el6.i686'\n CC [M] \/tmp\/vmware-config3\/vmci-only\/kernelStubsLinux.o\nIn file included from \/tmp\/vmware-config3\/vmci-only\/kernelStubs.h:35,\n from \/tmp\/vmware-config3\/vmci-only\/kernelStubsLinux.c:28:\n\/tmp\/vmware-config3\/vmci-only\/vm_basic_types.h:108:7: warning: \"__FreeBSD__\" is not defined\n CC [M] \/tmp\/vmware-config3\/vmci-only\/vmciDatagram.o\nIn file included from \/tmp\/vmware-config3\/vmci-only\/vmciDatagram.c:42:\n\/tmp\/vmware-config3\/vmci-only\/vm_basic_types.h:108:7: warning: \"__FreeBSD__\" is not defined\nIn file included from \/tmp\/vmware-config3\/vmci-only\/vmci_kernel_if.h:41,\n from \/tmp\/vmware-config3\/vmci-only\/vmciDatagram.c:45:\n\/tmp\/vmware-config3\/vmci-only\/compat_wait.h:78: error: conflicting types for \u00e2poll_initwait\u00e2\ninclude\/linux\/poll.h:70: note: previous declaration of \u00e2poll_initwait\u00e2 was here\nIn file included from \/tmp\/vmware-config3\/vmci-only\/vmci_queue_pair.h:36,\n from \/tmp\/vmware-config3\/vmci-only\/vmciGuestKernelAPI.h:43,\n from \/tmp\/vmware-config3\/vmci-only\/vmciUtil.h:33,\n from \/tmp\/vmware-config3\/vmci-only\/vmciDatagram.c:48:\n\/tmp\/vmware-config3\/vmci-only\/vm_atomic.h:329:7: warning: \"_MSC_VER\" is not defined\n\/tmp\/vmware-config3\/vmci-only\/vm_atomic.h:333:7: warning: \"_MSC_VER\" is not defined\n\/tmp\/vmware-config3\/vmci-only\/vm_atomic.h:401:7: warning: \"_MSC_VER\" is not defined\n\/tmp\/vmware-config3\/vmci-only\/vm_atomic.h:407:7: warning: \"_MSC_VER\" is not defined\n\/tmp\/vmware-config3\/vmci-only\/vm_atomic.h:506:7: warning: \"_MSC_VER\" is not defined\n\/tmp\/vmware-config3\/vmci-only\/vm_atomic.h:595:7: warning: \"_MSC_VER\" is not defined\n\/tmp\/vmware-config3\/vmci-only\/vm_atomic.h:684:7: warning: \"_MSC_VER\" is not defined\n\/tmp\/vmware-config3\/vmci-only\/vm_atomic.h:773:7: warning: \"_MSC_VER\" is not defined\n\/tmp\/vmware-config3\/vmci-only\/vm_atomic.h:775:7: warning: \"_MSC_VER\" is not defined\n\/tmp\/vmware-config3\/vmci-only\/vm_atomic.h:860:7: warning: \"_MSC_VER\" is not defined\n\/tmp\/vmware-config3\/vmci-only\/vm_atomic.h:862:7: warning: \"_MSC_VER\" is not defined\n\/tmp\/vmware-config3\/vmci-only\/vm_atomic.h:945:7: warning: \"_MSC_VER\" is not defined\n\/tmp\/vmware-config3\/vmci-only\/vm_atomic.h:947:7: warning: \"_MSC_VER\" is not defined\n\/tmp\/vmware-config3\/vmci-only\/vm_atomic.h:1028:7: warning: \"_MSC_VER\" is not defined\n\/tmp\/vmware-config3\/vmci-only\/vm_atomic.h:1030:7: warning: \"_MSC_VER\" is not defined\n\/tmp\/vmware-config3\/vmci-only\/vm_atomic.h:1223:7: warning: \"_MSC_VER\" is not defined\n\/tmp\/vmware-config3\/vmci-only\/vm_atomic.h:1227:7: warning: \"_MSC_VER\" is not defined\n\/tmp\/vmware-config3\/vmci-only\/vm_atomic.h:1536:7: warning: \"_MSC_VER\" is not defined\n\/tmp\/vmware-config3\/vmci-only\/vm_atomic.h:1663:7: warning: \"_MSC_VER\" is not defined\nmake[2]: *** [\/tmp\/vmware-config3\/vmci-only\/vmciDatagram.o] Error 1\nmake[1]: *** [_module_\/tmp\/vmware-config3\/vmci-only] Error 2\nmake[1]: Leaving directory `\/usr\/src\/kernels\/2.6.32-279.1.1.el6.i686'\nmake: *** [vmci.ko] Error 2\nmake: Leaving directory `\/tmp\/vmware-config3\/vmci-only'\nUnable to build the vmci module.\n\nThe communication service is used in addition to the standard communication\nbetween the guest and the host. The rest of the software provided by VMware\nTools is designed to work independently of this feature.\nIf you wish to have the VMCI feature, you can install the driver by running\nvmware-config-tools.pl again after making sure that gcc, binutils, make and the\nkernel sources for your running kernel are installed on your machine. These\npackages are available on your distribution's installation CD.\n[ Press Enter key to continue ]\n\nNo X install found.\n\n Checking acpi hot plug [ OK ]\nStarting VMware Tools services in the virtual machine:\n Switching to guest configuration: [ OK ]\n Guest operating system daemon: [ OK ]\n\nThe configuration of VMware Tools 2.0.0 build-122956 for Linux for this running\nkernel completed successfully.\n\nYou must restart your X session before any mouse or graphics changes take\neffect.\n\nYou can now run VMware Tools by invoking the following command:\n\"\/usr\/bin\/vmware-toolbox\" during an X server session.\n\nYou will need to either manually start \/usr\/bin\/vmware-user or log out and log\nback in to this desktop session to obtain the following features: guest\nresolution fit, drag and drop, and file and text copy\/paste. vmware-user is\nconfigured to automatically start at a graphical login, but that won't take\neffect until the next login.\n\nEnjoy,\n\n--the VMware team\n\n<\/pre>\n","protected":false},"excerpt":{"rendered":"VMware Tools is a group of utilities that enhances the overall performance of the virtual machine\u2019s guest operating system (OS) and improves management of the virtual machine (VM). This is…<\/p>\n","protected":false},"author":6,"featured_media":316,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"wds_primary_category":0,"footnotes":""},"categories":[2055,1083],"tags":[1536,1895],"class_list":["post-3560","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-centos","category-vmware","tag-linux","tag-vmware"],"_links":{"self":[{"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/posts\/3560","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/comments?post=3560"}],"version-history":[{"count":0,"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/posts\/3560\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/media\/316"}],"wp:attachment":[{"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/media?parent=3560"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/categories?post=3560"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/tags?post=3560"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}