Hi all,
I am using Ubuntu 12.04 (with the old visualization - no unity) as guest system in OS 10.10.2 (Yosemite) with VMware fusion 7.0.1 and compatibility to use hardware version 10. At some point, some of the vmware tools stop working. Among the issues that are improved installing VMware tools (KB1022048), I have lost some functionalities (although I can share folders, I have sound and network):
- Low video resolution, meaning that I cannot resize the window freely
- Restricted movement of the mouse
- Inability to copy and paste and drag-and-drop files
It is not clear to me if solution in KB1014988 is still of application to fusion 7. But I tried to wait more than 60 seconds, I have to enter a password to log in and I tried to shut down and start rather than reboot.
I have connected only one monitor and disabled multiple accounts in the host system as suggested in (KB1027884)
During installation of the VMware tools this message appears: "The vmxnet driver is no longer supported on kernels 3.3 and greater. Please vmware: upgrade to a newer virtual NIC. (e.g., vmxnet3 or e1000e)". But it seems that is just a generic message from vmware-tools that seems to appear regardless of the adapter type. Just in case, I added ethernet0.virtualDev = "vmxnet3" to the virtual machine's configuration file (as suggested at Notes of a Programmer: VMWare Tools Failed to Load on Ubuntu 13.10 (Saucy) .
First I tried to reinstall but some posts suggested to uninstall, and perform a clean installation (KB1022525), so I did. And still no luck. Something that might be worth to mention is that after installing vmware tools, "install vmware tools" is clickable in the vmware menu while I guess it should say "reinstall vmware tools".
I would appreaciate any advice on how to proceed. Thanks in advanced.
In case it helps, you can see below the result of the installation. In addition, you can see the kernel, the modules that are running (lsmod) and the content of the mtab file
lourdes@ubuntu:~/Documents/
vmware-tools-distrib$ sudo ./vmware-install.pl
[sudo] password for lourdes:
The installer has detected an existing installation of open-vm-tools on this
system and will not attempt to remove and replace these user-space
applications. It is recommended to use the open-vm-tools packages provided by
the operating system. If you do not want to use the existing installation of
open-vm-tools and attempt to install VMware Tools, you must uninstall the
open-vm-tools packages and re-run this installer.
The installer will next check if there are any missing kernel drivers. Type yes
if you want to do this, otherwise type no [yes]
Creating a new VMware Tools installer database using the tar4 format.
Installing VMware Tools.
In which directory do you want to install the binary files?
[/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.8.4 build-2202052 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.
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-36-generic/build/include".
The path "/lib/modules/3.8.0-36-generic/build/include" appears to be a valid
path to the 3.8.0-36-generic kernel headers.
Would you like to change it? [no]
Using kernel build system.
make: Entering directory `/tmp/modconfig-uZZ2bK/vmci-only'
/usr/bin/make -C /lib/modules/3.8.0-36-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.8.0-36-generic'
CC [M] /tmp/modconfig-uZZ2bK/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-uZZ2bK/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-uZZ2bK/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-uZZ2bK/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-uZZ2bK/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-uZZ2bK/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-uZZ2bK/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-uZZ2bK/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-uZZ2bK/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-uZZ2bK/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-uZZ2bK/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-uZZ2bK/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-uZZ2bK/vmci-only/driverLog.o
LD [M] /tmp/modconfig-uZZ2bK/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-uZZ2bK/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-uZZ2bK/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.8.0-36-generic'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-uZZ2bK/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-uZZ2bK/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/modconfig-uZZ2bK/vmci-only'
Using kernel build system.
make: Entering directory `/tmp/modconfig-BoTgsT/vmci-only'
/usr/bin/make -C /lib/modules/3.8.0-36-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.8.0-36-generic'
CC [M] /tmp/modconfig-BoTgsT/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-BoTgsT/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-BoTgsT/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-BoTgsT/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-BoTgsT/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-BoTgsT/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-BoTgsT/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-BoTgsT/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-BoTgsT/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-BoTgsT/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-BoTgsT/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-BoTgsT/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-BoTgsT/vmci-only/driverLog.o
LD [M] /tmp/modconfig-BoTgsT/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-BoTgsT/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-BoTgsT/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.8.0-36-generic'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-BoTgsT/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-BoTgsT/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/modconfig-BoTgsT/vmci-only'
Using kernel build system.
make: Entering directory `/tmp/modconfig-BoTgsT/vsock-only'
/usr/bin/make -C /lib/modules/3.8.0-36-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.8.0-36-generic'
CC [M] /tmp/modconfig-BoTgsT/vsock-only/linux/af_vsock.o
CC [M] /tmp/modconfig-BoTgsT/vsock-only/linux/notify.o
CC [M] /tmp/modconfig-BoTgsT/vsock-only/linux/notifyQState.o
CC [M] /tmp/modconfig-BoTgsT/vsock-only/linux/stats.o
CC [M] /tmp/modconfig-BoTgsT/vsock-only/linux/util.o
CC [M] /tmp/modconfig-BoTgsT/vsock-only/linux/vsockAddr.o
CC [M] /tmp/modconfig-BoTgsT/vsock-only/driverLog.o
LD [M] /tmp/modconfig-BoTgsT/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-BoTgsT/vsock-only/vsock.mod.o
LD [M] /tmp/modconfig-BoTgsT/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.8.0-36-generic'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-BoTgsT/vsock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-BoTgsT/vsock-only'
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/modconfig-BoTgsT/vsock-only'
The module vmxnet3 has already been installed on this system by another
installer or package and will not be modified by this installer.
The module pvscsi has already been installed on this system by another
installer or package and will not be modified by this installer.
The module vmmemctl has already been installed on this system by another
installer or package and will not be modified by this installer.
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 kernel build system.
make: Entering directory `/tmp/modconfig-Go80sd/vmci-only'
/usr/bin/make -C /lib/modules/3.8.0-36-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.8.0-36-generic'
CC [M] /tmp/modconfig-Go80sd/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-Go80sd/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-Go80sd/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-Go80sd/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-Go80sd/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-Go80sd/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-Go80sd/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-Go80sd/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-Go80sd/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-Go80sd/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-Go80sd/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-Go80sd/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-Go80sd/vmci-only/driverLog.o
LD [M] /tmp/modconfig-Go80sd/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-Go80sd/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-Go80sd/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.8.0-36-generic'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-Go80sd/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-Go80sd/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/modconfig-Go80sd/vmci-only'
Using kernel build system.
make: Entering directory `/tmp/modconfig-Go80sd/vmhgfs-only'
/usr/bin/make -C /lib/modules/3.8.0-36-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.8.0-36-generic'
CC [M] /tmp/modconfig-Go80sd/vmhgfs-only/backdoor.o
CC [M] /tmp/modconfig-Go80sd/vmhgfs-only/backdoorGcc32.o
CC [M] /tmp/modconfig-Go80sd/vmhgfs-only/bdhandler.o
CC [M] /tmp/modconfig-Go80sd/vmhgfs-only/cpName.o
CC [M] /tmp/modconfig-Go80sd/vmhgfs-only/cpNameLinux.o
CC [M] /tmp/modconfig-Go80sd/vmhgfs-only/cpNameLite.o
CC [M] /tmp/modconfig-Go80sd/vmhgfs-only/dentry.o
CC [M] /tmp/modconfig-Go80sd/vmhgfs-only/dir.o
CC [M] /tmp/modconfig-Go80sd/vmhgfs-only/file.o
CC [M] /tmp/modconfig-Go80sd/vmhgfs-only/filesystem.o
CC [M] /tmp/modconfig-Go80sd/vmhgfs-only/fsutil.o
CC [M] /tmp/modconfig-Go80sd/vmhgfs-only/hgfsBd.o
CC [M] /tmp/modconfig-Go80sd/vmhgfs-only/hgfsEscape.o
CC [M] /tmp/modconfig-Go80sd/vmhgfs-only/hgfsUtil.o
CC [M] /tmp/modconfig-Go80sd/vmhgfs-only/inode.o
CC [M] /tmp/modconfig-Go80sd/vmhgfs-only/link.o
CC [M] /tmp/modconfig-Go80sd/vmhgfs-only/message.o
CC [M] /tmp/modconfig-Go80sd/vmhgfs-only/module.o
CC [M] /tmp/modconfig-Go80sd/vmhgfs-only/page.o
CC [M] /tmp/modconfig-Go80sd/vmhgfs-only/request.o
CC [M] /tmp/modconfig-Go80sd/vmhgfs-only/rpcout.o
CC [M] /tmp/modconfig-Go80sd/vmhgfs-only/stubs.o
CC [M] /tmp/modconfig-Go80sd/vmhgfs-only/super.o
CC [M] /tmp/modconfig-Go80sd/vmhgfs-only/transport.o
CC [M] /tmp/modconfig-Go80sd/vmhgfs-only/kernelStubsLinux.o
LD [M] /tmp/modconfig-Go80sd/vmhgfs-only/vmhgfs.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-Go80sd/vmhgfs-only/vmhgfs.mod.o
LD [M] /tmp/modconfig-Go80sd/vmhgfs-only/vmhgfs.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.8.0-36-generic'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-Go80sd/vmhgfs-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-Go80sd/vmhgfs-only'
cp -f vmhgfs.ko ./../vmhgfs.o
make: Leaving directory `/tmp/modconfig-Go80sd/vmhgfs-only'
The vmxnet driver is no longer supported on kernels 3.3 and greater. Please
upgrade to a newer virtual NIC. (e.g., vmxnet3 or e1000e)
VMware automatic kernel modules enables automatic building and installation of
VMware kernel modules at boot that are not already present. This feature can be
enabled/disabled 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]
Creating a new initrd boot image for the kernel.
update-initramfs: Generating /boot/initrd.img-3.8.0-36-generic
vmware-tools-thinprint start/running
vmware-tools start/running
The configuration of VMware Tools 9.8.4 build-2202052 for Linux for this
running kernel completed successfully.
Enjoy,
--the VMware team
Found VMware Tools CDROM mounted at /media/VMware Tools. Ejecting device
/dev/sr0 ...
lourdes@ubuntu:~/Documents$ uname -a
Linux ubuntu 3.8.0-36-generic #52~precise1-Ubuntu SMP Mon Feb 3 21:56:56 UTC 2014 i686 i686 i386 GNU/Linux
lourdes@ubuntu:~/Documents$ lsmod | grep vm
vmhgfs 48052 1
vmw_balloon 12700 0
vmwgfx 115982 3
ttm 76149 1 vmwgfx
drm 233935 4 vmwgfx,ttm
vmci 76246 1 vsock
vmw_pvscsi 22432 0
vmxnet3 44863 0
lourdes@ubuntu:~/Documents$ cat /etc/mtab
/dev/sda1 / ext4 rw,errors=remount-ro 0 0
proc /proc proc rw,noexec,nosuid,nodev 0 0
sysfs /sys sysfs rw,noexec,nosuid,nodev 0 0
none /sys/fs/fuse/connections fusectl rw 0 0
none /sys/kernel/debug debugfs rw 0 0
none /sys/kernel/security securityfs rw 0 0
udev /dev devtmpfs rw,mode=0755 0 0
devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=0620 0 0
tmpfs /run tmpfs rw,noexec,nosuid,size=10%,mode=0755 0 0
none /run/lock tmpfs rw,noexec,nosuid,nodev,size=5242880 0 0
none /run/shm tmpfs rw,nosuid,nodev 0 0
.host:/ /mnt/hgfs vmhgfs rw,ttl=1 0 0
gvfs-fuse-daemon /home/lourdes/.gvfs fuse.gvfs-fuse-daemon rw,nosuid,nodev,user=lourdes 0 0