when configuring the latest VMWare tools, I receive the following error:
"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)"
I have followed instructions on a few different posts to try to fix this, and none have worked.
I have tried running the vmware tools configuration script with --clobber-kernel-modules=vmxnet - that didn't help.
I tried changing ethernet0.virtualDev = "vmxnet" to "vmxnet3" in the .vmx file - that didn't help either.
Running Ubuntu 14.04 on VMWare Player 6.0.6 build-2700073 on Windows 7. The VM image in question is Ubuntu 14.04 on Linux kernel 1.13.0-43.
This is for bridged mode (which I need) - running in NAT mode works fine.
$ uname -a
Linux ubuntu 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
dust@ubuntu:~/Desktop/vmware-tools-distrib
$ sudo ./vmware-install.pl --clobber-kernel-modules=vmxnet
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
vmware-tools stop/waiting
Stopping services for vmware-tools-thinprint
vmware-tools-thinprint stop/waiting
File /etc/pulse/default.pa is backed up to /etc/pulse/default.pa.old.8.
update-initramfs: Generating /boot/initrd.img-3.13.0-43-generic
update-initramfs: Generating /boot/initrd.img-3.13.0-39-generic
The removal of VMware Tools 9.6.5 build-2700074 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]
The path "/usr/lib/vmware-tools" does not exist currently. This program is
going to create it, including needed parent directories. Is this what you want?
[yes]
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.6.5 build-2700074 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 module vmci has already been installed on this system by another installer
or package and will not be modified by this installer.
The module vsock has already been installed on this system by another installer
or package and will not be modified by this installer.
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]
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.13.0-43-generic/build/include".
The path "/lib/modules/3.13.0-43-generic/build/include" appears to be a valid
path to the 3.13.0-43-generic kernel headers.
Would you like to change it? [no]
Using 2.6.x kernel build system.
make: Entering directory `/tmp/modconfig-OyHNrF/vmhgfs-only'
/usr/bin/make -C /lib/modules/3.13.0-43-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.13.0-43-generic'
CC [M] /tmp/modconfig-OyHNrF/vmhgfs-only/backdoor.o
CC [M] /tmp/modconfig-OyHNrF/vmhgfs-only/backdoorGcc64.o
CC [M] /tmp/modconfig-OyHNrF/vmhgfs-only/bdhandler.o
CC [M] /tmp/modconfig-OyHNrF/vmhgfs-only/cpName.o
CC [M] /tmp/modconfig-OyHNrF/vmhgfs-only/cpNameLinux.o
CC [M] /tmp/modconfig-OyHNrF/vmhgfs-only/cpNameLite.o
CC [M] /tmp/modconfig-OyHNrF/vmhgfs-only/dentry.o
CC [M] /tmp/modconfig-OyHNrF/vmhgfs-only/dir.o
CC [M] /tmp/modconfig-OyHNrF/vmhgfs-only/file.o
CC [M] /tmp/modconfig-OyHNrF/vmhgfs-only/filesystem.o
CC [M] /tmp/modconfig-OyHNrF/vmhgfs-only/fsutil.o
CC [M] /tmp/modconfig-OyHNrF/vmhgfs-only/hgfsBd.o
CC [M] /tmp/modconfig-OyHNrF/vmhgfs-only/hgfsEscape.o
CC [M] /tmp/modconfig-OyHNrF/vmhgfs-only/hgfsUtil.o
CC [M] /tmp/modconfig-OyHNrF/vmhgfs-only/inode.o
CC [M] /tmp/modconfig-OyHNrF/vmhgfs-only/link.o
CC [M] /tmp/modconfig-OyHNrF/vmhgfs-only/message.o
CC [M] /tmp/modconfig-OyHNrF/vmhgfs-only/module.o
CC [M] /tmp/modconfig-OyHNrF/vmhgfs-only/page.o
CC [M] /tmp/modconfig-OyHNrF/vmhgfs-only/request.o
CC [M] /tmp/modconfig-OyHNrF/vmhgfs-only/rpcout.o
CC [M] /tmp/modconfig-OyHNrF/vmhgfs-only/stubs.o
CC [M] /tmp/modconfig-OyHNrF/vmhgfs-only/super.o
CC [M] /tmp/modconfig-OyHNrF/vmhgfs-only/transport.o
CC [M] /tmp/modconfig-OyHNrF/vmhgfs-only/vmci.o
CC [M] /tmp/modconfig-OyHNrF/vmhgfs-only/kernelStubsLinux.o
LD [M] /tmp/modconfig-OyHNrF/vmhgfs-only/vmhgfs.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-OyHNrF/vmhgfs-only/vmhgfs.mod.o
LD [M] /tmp/modconfig-OyHNrF/vmhgfs-only/vmhgfs.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-43-generic'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/modconfig-OyHNrF/vmhgfs-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/modconfig-OyHNrF/vmhgfs-only'
cp -f vmhgfs.ko ./../vmhgfs.o
make: Leaving directory `/tmp/modconfig-OyHNrF/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)
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?
[yes]
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?
[yes]
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.15.1
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.13.0-43-generic
vmware-tools-thinprint start/running
vmware-tools start/running
The configuration of VMware Tools 9.6.5 build-2700074 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
$ ~