Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- 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] y
- Uninstalling the tar installation of VMware Tools.
- Stopping services for vmware-tools
- vmware-tools stop/waiting
- Stopping services for vmware-tools-thinprint
- vmware-tools-thinprint stop/waiting
- 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.12.
- 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.12.
- File /usr/lib/vmware-tools/lib64/libconf/etc/fonts/fonts.conf is backed up to
- /usr/lib/vmware-tools/lib64/libconf/etc/fonts/fonts.conf.old.11.
- 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.12.
- 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.
- File /etc/initramfs-tools/modules is backed up to
- /etc/initramfs-tools/modules.old.11.
- File /etc/pulse/default.pa is backed up to /etc/pulse/default.pa.old.11.
- update-initramfs: Generating /boot/initrd.img-3.8.0-19-generic
- update-initramfs: Generating /boot/initrd.img-3.5.0-27-generic
- The removal of VMware Tools 9.2.3 build-1031360 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]
- What is the directory that contains the init scripts?
- [/etc/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 9.2.3 build-1031360 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.
- The VMware FileSystem Sync Driver (vmsync) allows external third-party backup
- software that is integrated with vSphere to create backups of the virtual
- machine. Do you wish to enable this feature? [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]
- Searching for a valid kernel header path...
- Detected the kernel headers at "/lib/modules/3.8.0-19-generic/build/include".
- The path "/lib/modules/3.8.0-19-generic/build/include" appears to be a valid
- path to the 3.8.0-19-generic kernel headers.
- Would you like to change it? [no]
- Using 2.6.x kernel build system.
- make: Entering directory `/tmp/modconfig-qBJBfC/vmci-only'
- /usr/bin/make -C /lib/modules/3.8.0-19-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
- MODULEBUILDDIR= modules
- make[1]: Entering directory `/usr/src/linux-headers-3.8.0-19-generic'
- CC [M] /tmp/modconfig-qBJBfC/vmci-only/linux/driver.o
- CC [M] /tmp/modconfig-qBJBfC/vmci-only/linux/vmciKernelIf.o
- CC [M] /tmp/modconfig-qBJBfC/vmci-only/common/vmciContext.o
- CC [M] /tmp/modconfig-qBJBfC/vmci-only/common/vmciDatagram.o
- CC [M] /tmp/modconfig-qBJBfC/vmci-only/common/vmciDoorbell.o
- CC [M] /tmp/modconfig-qBJBfC/vmci-only/common/vmciDriver.o
- CC [M] /tmp/modconfig-qBJBfC/vmci-only/common/vmciEvent.o
- CC [M] /tmp/modconfig-qBJBfC/vmci-only/common/vmciHashtable.o
- CC [M] /tmp/modconfig-qBJBfC/vmci-only/common/vmciQPair.o
- CC [M] /tmp/modconfig-qBJBfC/vmci-only/common/vmciQueuePair.o
- CC [M] /tmp/modconfig-qBJBfC/vmci-only/common/vmciResource.o
- CC [M] /tmp/modconfig-qBJBfC/vmci-only/common/vmciRoute.o
- CC [M] /tmp/modconfig-qBJBfC/vmci-only/driverLog.o
- LD [M] /tmp/modconfig-qBJBfC/vmci-only/vmci.o
- Building modules, stage 2.
- MODPOST 1 modules
- CC /tmp/modconfig-qBJBfC/vmci-only/vmci.mod.o
- LD [M] /tmp/modconfig-qBJBfC/vmci-only/vmci.ko
- make[1]: Leaving directory `/usr/src/linux-headers-3.8.0-19-generic'
- /usr/bin/make -C $PWD SRCROOT=$PWD/. \
- MODULEBUILDDIR= postbuild
- make[1]: Entering directory `/tmp/modconfig-qBJBfC/vmci-only'
- make[1]: `postbuild' is up to date.
- make[1]: Leaving directory `/tmp/modconfig-qBJBfC/vmci-only'
- cp -f vmci.ko ./../vmci.o
- make: Leaving directory `/tmp/modconfig-qBJBfC/vmci-only'
- Using 2.6.x kernel build system.
- make: Entering directory `/tmp/modconfig-wxwVAp/vmci-only'
- /usr/bin/make -C /lib/modules/3.8.0-19-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
- MODULEBUILDDIR= modules
- make[1]: Entering directory `/usr/src/linux-headers-3.8.0-19-generic'
- CC [M] /tmp/modconfig-wxwVAp/vmci-only/linux/vmciKernelIf.o
- CC [M] /tmp/modconfig-wxwVAp/vmci-only/linux/driver.o
- CC [M] /tmp/modconfig-wxwVAp/vmci-only/common/vmciContext.o
- CC [M] /tmp/modconfig-wxwVAp/vmci-only/common/vmciDatagram.o
- CC [M] /tmp/modconfig-wxwVAp/vmci-only/common/vmciDoorbell.o
- CC [M] /tmp/modconfig-wxwVAp/vmci-only/common/vmciDriver.o
- CC [M] /tmp/modconfig-wxwVAp/vmci-only/common/vmciEvent.o
- CC [M] /tmp/modconfig-wxwVAp/vmci-only/common/vmciHashtable.o
- CC [M] /tmp/modconfig-wxwVAp/vmci-only/common/vmciQPair.o
- CC [M] /tmp/modconfig-wxwVAp/vmci-only/common/vmciQueuePair.o
- CC [M] /tmp/modconfig-wxwVAp/vmci-only/common/vmciResource.o
- CC [M] /tmp/modconfig-wxwVAp/vmci-only/common/vmciRoute.o
- CC [M] /tmp/modconfig-wxwVAp/vmci-only/driverLog.o
- LD [M] /tmp/modconfig-wxwVAp/vmci-only/vmci.o
- Building modules, stage 2.
- MODPOST 1 modules
- CC /tmp/modconfig-wxwVAp/vmci-only/vmci.mod.o
- LD [M] /tmp/modconfig-wxwVAp/vmci-only/vmci.ko
- make[1]: Leaving directory `/usr/src/linux-headers-3.8.0-19-generic'
- /usr/bin/make -C $PWD SRCROOT=$PWD/. \
- MODULEBUILDDIR= postbuild
- make[1]: Entering directory `/tmp/modconfig-wxwVAp/vmci-only'
- make[1]: `postbuild' is up to date.
- make[1]: Leaving directory `/tmp/modconfig-wxwVAp/vmci-only'
- cp -f vmci.ko ./../vmci.o
- make: Leaving directory `/tmp/modconfig-wxwVAp/vmci-only'
- Using 2.6.x kernel build system.
- make: Entering directory `/tmp/modconfig-wxwVAp/vsock-only'
- /usr/bin/make -C /lib/modules/3.8.0-19-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
- MODULEBUILDDIR= modules
- make[1]: Entering directory `/usr/src/linux-headers-3.8.0-19-generic'
- CC [M] /tmp/modconfig-wxwVAp/vsock-only/linux/af_vsock.o
- CC [M] /tmp/modconfig-wxwVAp/vsock-only/linux/notify.o
- CC [M] /tmp/modconfig-wxwVAp/vsock-only/linux/notifyQState.o
- CC [M] /tmp/modconfig-wxwVAp/vsock-only/linux/stats.o
- CC [M] /tmp/modconfig-wxwVAp/vsock-only/linux/util.o
- CC [M] /tmp/modconfig-wxwVAp/vsock-only/linux/vsockAddr.o
- CC [M] /tmp/modconfig-wxwVAp/vsock-only/driverLog.o
- LD [M] /tmp/modconfig-wxwVAp/vsock-only/vsock.o
- Building modules, stage 2.
- MODPOST 1 modules
- CC /tmp/modconfig-wxwVAp/vsock-only/vsock.mod.o
- LD [M] /tmp/modconfig-wxwVAp/vsock-only/vsock.ko
- make[1]: Leaving directory `/usr/src/linux-headers-3.8.0-19-generic'
- /usr/bin/make -C $PWD SRCROOT=$PWD/. \
- MODULEBUILDDIR= postbuild
- make[1]: Entering directory `/tmp/modconfig-wxwVAp/vsock-only'
- make[1]: `postbuild' is up to date.
- make[1]: Leaving directory `/tmp/modconfig-wxwVAp/vsock-only'
- cp -f vsock.ko ./../vsock.o
- make: Leaving directory `/tmp/modconfig-wxwVAp/vsock-only'
- The module vmxnet3 has already been installed on this system by another package
- but has been marked for clobbering and will be overridden.
- Using 2.6.x kernel build system.
- make: Entering directory `/tmp/modconfig-bf4brN/vmxnet3-only'
- /usr/bin/make -C /lib/modules/3.8.0-19-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
- MODULEBUILDDIR= modules
- make[1]: Entering directory `/usr/src/linux-headers-3.8.0-19-generic'
- CC [M] /tmp/modconfig-bf4brN/vmxnet3-only/vmxnet3_ethtool.o
- CC [M] /tmp/modconfig-bf4brN/vmxnet3-only/vmxnet3_drv.o
- CC [M] /tmp/modconfig-bf4brN/vmxnet3-only/vmxnet3_shm.o
- LD [M] /tmp/modconfig-bf4brN/vmxnet3-only/vmxnet3.o
- Building modules, stage 2.
- MODPOST 1 modules
- CC /tmp/modconfig-bf4brN/vmxnet3-only/vmxnet3.mod.o
- LD [M] /tmp/modconfig-bf4brN/vmxnet3-only/vmxnet3.ko
- make[1]: Leaving directory `/usr/src/linux-headers-3.8.0-19-generic'
- /usr/bin/make -C $PWD SRCROOT=$PWD/. \
- MODULEBUILDDIR= postbuild
- make[1]: Entering directory `/tmp/modconfig-bf4brN/vmxnet3-only'
- make[1]: `postbuild' is up to date.
- make[1]: Leaving directory `/tmp/modconfig-bf4brN/vmxnet3-only'
- cp -f vmxnet3.ko ./../vmxnet3.o
- make: Leaving directory `/tmp/modconfig-bf4brN/vmxnet3-only'
- The module pvscsi has already been installed on this system by another package
- but has been marked for clobbering and will be overridden.
- Using 2.6.x kernel build system.
- make: Entering directory `/tmp/modconfig-MBV62y/pvscsi-only'
- /usr/bin/make -C /lib/modules/3.8.0-19-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
- MODULEBUILDDIR= modules
- make[1]: Entering directory `/usr/src/linux-headers-3.8.0-19-generic'
- CC [M] /tmp/modconfig-MBV62y/pvscsi-only/pvscsi.o
- Building modules, stage 2.
- MODPOST 1 modules
- CC /tmp/modconfig-MBV62y/pvscsi-only/pvscsi.mod.o
- LD [M] /tmp/modconfig-MBV62y/pvscsi-only/pvscsi.ko
- make[1]: Leaving directory `/usr/src/linux-headers-3.8.0-19-generic'
- /usr/bin/make -C $PWD SRCROOT=$PWD/. \
- MODULEBUILDDIR= postbuild
- make[1]: Entering directory `/tmp/modconfig-MBV62y/pvscsi-only'
- make[1]: `postbuild' is up to date.
- make[1]: Leaving directory `/tmp/modconfig-MBV62y/pvscsi-only'
- cp -f pvscsi.ko ./../pvscsi.o
- make: Leaving directory `/tmp/modconfig-MBV62y/pvscsi-only'
- The module vmmemctl has already been installed on this system by another
- package but has been marked for clobbering and will be overridden.
- Using 2.6.x kernel build system.
- make: Entering directory `/tmp/modconfig-WpXctk/vmmemctl-only'
- /usr/bin/make -C /lib/modules/3.8.0-19-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
- MODULEBUILDDIR= modules
- make[1]: Entering directory `/usr/src/linux-headers-3.8.0-19-generic'
- CC [M] /tmp/modconfig-WpXctk/vmmemctl-only/backdoorGcc64.o
- CC [M] /tmp/modconfig-WpXctk/vmmemctl-only/os.o
- CC [M] /tmp/modconfig-WpXctk/vmmemctl-only/vmballoon.o
- LD [M] /tmp/modconfig-WpXctk/vmmemctl-only/vmmemctl.o
- Building modules, stage 2.
- MODPOST 1 modules
- CC /tmp/modconfig-WpXctk/vmmemctl-only/vmmemctl.mod.o
- LD [M] /tmp/modconfig-WpXctk/vmmemctl-only/vmmemctl.ko
- make[1]: Leaving directory `/usr/src/linux-headers-3.8.0-19-generic'
- /usr/bin/make -C $PWD SRCROOT=$PWD/. \
- MODULEBUILDDIR= postbuild
- make[1]: Entering directory `/tmp/modconfig-WpXctk/vmmemctl-only'
- make[1]: `postbuild' is up to date.
- make[1]: Leaving directory `/tmp/modconfig-WpXctk/vmmemctl-only'
- cp -f vmmemctl.ko ./../vmmemctl.o
- make: Leaving directory `/tmp/modconfig-WpXctk/vmmemctl-only'
- 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/modconfig-ZJ54iS/vmci-only'
- /usr/bin/make -C /lib/modules/3.8.0-19-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
- MODULEBUILDDIR= modules
- make[1]: Entering directory `/usr/src/linux-headers-3.8.0-19-generic'
- CC [M] /tmp/modconfig-ZJ54iS/vmci-only/linux/driver.o
- CC [M] /tmp/modconfig-ZJ54iS/vmci-only/linux/vmciKernelIf.o
- CC [M] /tmp/modconfig-ZJ54iS/vmci-only/common/vmciContext.o
- CC [M] /tmp/modconfig-ZJ54iS/vmci-only/common/vmciDatagram.o
- CC [M] /tmp/modconfig-ZJ54iS/vmci-only/common/vmciDoorbell.o
- CC [M] /tmp/modconfig-ZJ54iS/vmci-only/common/vmciDriver.o
- CC [M] /tmp/modconfig-ZJ54iS/vmci-only/common/vmciEvent.o
- CC [M] /tmp/modconfig-ZJ54iS/vmci-only/common/vmciHashtable.o
- CC [M] /tmp/modconfig-ZJ54iS/vmci-only/common/vmciQPair.o
- CC [M] /tmp/modconfig-ZJ54iS/vmci-only/common/vmciQueuePair.o
- CC [M] /tmp/modconfig-ZJ54iS/vmci-only/common/vmciResource.o
- CC [M] /tmp/modconfig-ZJ54iS/vmci-only/common/vmciRoute.o
- CC [M] /tmp/modconfig-ZJ54iS/vmci-only/driverLog.o
- LD [M] /tmp/modconfig-ZJ54iS/vmci-only/vmci.o
- Building modules, stage 2.
- MODPOST 1 modules
- CC /tmp/modconfig-ZJ54iS/vmci-only/vmci.mod.o
- LD [M] /tmp/modconfig-ZJ54iS/vmci-only/vmci.ko
- make[1]: Leaving directory `/usr/src/linux-headers-3.8.0-19-generic'
- /usr/bin/make -C $PWD SRCROOT=$PWD/. \
- MODULEBUILDDIR= postbuild
- make[1]: Entering directory `/tmp/modconfig-ZJ54iS/vmci-only'
- make[1]: `postbuild' is up to date.
- make[1]: Leaving directory `/tmp/modconfig-ZJ54iS/vmci-only'
- cp -f vmci.ko ./../vmci.o
- make: Leaving directory `/tmp/modconfig-ZJ54iS/vmci-only'
- Using 2.6.x kernel build system.
- make: Entering directory `/tmp/modconfig-ZJ54iS/vmhgfs-only'
- /usr/bin/make -C /lib/modules/3.8.0-19-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
- MODULEBUILDDIR= modules
- make[1]: Entering directory `/usr/src/linux-headers-3.8.0-19-generic'
- CC [M] /tmp/modconfig-ZJ54iS/vmhgfs-only/backdoorGcc64.o
- CC [M] /tmp/modconfig-ZJ54iS/vmhgfs-only/backdoor.o
- CC [M] /tmp/modconfig-ZJ54iS/vmhgfs-only/cpName.o
- CC [M] /tmp/modconfig-ZJ54iS/vmhgfs-only/bdhandler.o
- CC [M] /tmp/modconfig-ZJ54iS/vmhgfs-only/cpNameLinux.o
- CC [M] /tmp/modconfig-ZJ54iS/vmhgfs-only/cpNameLite.o
- CC [M] /tmp/modconfig-ZJ54iS/vmhgfs-only/dentry.o
- CC [M] /tmp/modconfig-ZJ54iS/vmhgfs-only/dir.o
- CC [M] /tmp/modconfig-ZJ54iS/vmhgfs-only/file.o
- CC [M] /tmp/modconfig-ZJ54iS/vmhgfs-only/filesystem.o
- CC [M] /tmp/modconfig-ZJ54iS/vmhgfs-only/fsutil.o
- CC [M] /tmp/modconfig-ZJ54iS/vmhgfs-only/hgfsBd.o
- CC [M] /tmp/modconfig-ZJ54iS/vmhgfs-only/hgfsEscape.o
- CC [M] /tmp/modconfig-ZJ54iS/vmhgfs-only/hgfsUtil.o
- CC [M] /tmp/modconfig-ZJ54iS/vmhgfs-only/inode.o
- CC [M] /tmp/modconfig-ZJ54iS/vmhgfs-only/link.o
- /tmp/modconfig-ZJ54iS/vmhgfs-only/inode.c: In function ‘HgfsTruncatePages’:
- /tmp/modconfig-ZJ54iS/vmhgfs-only/inode.c:888:4: error: implicit declaration of function ‘vmtruncate’ [-Werror=implicit-function-declaration]
- cc1: some warnings being treated as errors
- make[2]: *** [/tmp/modconfig-ZJ54iS/vmhgfs-only/inode.o] Error 1
- make[2]: *** Waiting for unfinished jobs....
- make[1]: *** [_module_/tmp/modconfig-ZJ54iS/vmhgfs-only] Error 2
- make[1]: Leaving directory `/usr/src/linux-headers-3.8.0-19-generic'
- make: *** [vmhgfs.ko] Error 2
- make: Leaving directory `/tmp/modconfig-ZJ54iS/vmhgfs-only'
- The filesystem driver (vmhgfs module) is used only for the shared folder
- feature. The rest of the software provided by VMware Tools is designed to work
- independently of this feature.
- If you wish to have the shared folders feature, you can install the driver by
- running vmware-config-tools.pl again after making sure that gcc, binutils, make
- and the kernel sources for your running kernel are installed on your machine.
- These packages are available on your distribution's installation CD.
- [ Press Enter key to continue ]
- Using 2.6.x kernel build system.
- make: Entering directory `/tmp/modconfig-cqPD8U/vmxnet-only'
- /usr/bin/make -C /lib/modules/3.8.0-19-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
- MODULEBUILDDIR= modules
- make[1]: Entering directory `/usr/src/linux-headers-3.8.0-19-generic'
- CC [M] /tmp/modconfig-cqPD8U/vmxnet-only/vmxnet.o
- Building modules, stage 2.
- MODPOST 1 modules
- CC /tmp/modconfig-cqPD8U/vmxnet-only/vmxnet.mod.o
- LD [M] /tmp/modconfig-cqPD8U/vmxnet-only/vmxnet.ko
- make[1]: Leaving directory `/usr/src/linux-headers-3.8.0-19-generic'
- /usr/bin/make -C $PWD SRCROOT=$PWD/. \
- MODULEBUILDDIR= postbuild
- make[1]: Entering directory `/tmp/modconfig-cqPD8U/vmxnet-only'
- make[1]: `postbuild' is up to date.
- make[1]: Leaving directory `/tmp/modconfig-cqPD8U/vmxnet-only'
- cp -f vmxnet.ko ./../vmxnet.o
- make: Leaving directory `/tmp/modconfig-cqPD8U/vmxnet-only'
- The vmblock enables dragging or copying files between host and guest in a
- Fusion or Workstation virtual environment. Do you wish to enable this feature?
- [no]
- !!! [EXPERIMENTAL] !!!
- VMware automatic kernel modules enables automatic building and installation of
- VMware kernel modules at boot that 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]
- Thinprint provides driver-free printing. Do you wish to enable this feature?
- [yes]
- Disabling timer-based audio scheduling in pulseaudio.
- Detected X server version 1.13.3
- Distribution provided drivers for Xorg X server are used.
- Skipping X configuration because X drivers are not included.
- Creating a new initrd boot image for the kernel.
- update-initramfs: Generating /boot/initrd.img-3.8.0-19-generic
- vmware-tools-thinprint start/running
- vmware-tools start/running
- The configuration of VMware Tools 9.2.3 build-1031360 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.
- 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
Advertisement
Add Comment
Please, Sign In to add comment