aalesilva
Contributor
Contributor

After install kernel 2.6.32-504 Could not open /dev/vmmon

Hi!

Yesterday when update my RHEL 6.2 for 6.6, my VMWare Workstation 10.0.3 dont't work, when start the vm appear the error.

could open /dev/vmmon: No such file or directory.

Please make sure that the kernel module `vmmon' is loaded.

I try this command sudo vmware-modconfig --console --install-all but the problem yet continue.

somebody have find the solution.

Thank's!

Tags (1)
26 Replies
Samas33
Contributor
Contributor

Hi!

look my post above October, 20 2014.

i can;t resolve this problem

i think the uninstall vmware in old kernel and then install again under new kernel may be useful

0 Kudos
raz3k
Contributor
Contributor

The solution is as follows:

cd /tmp

tar -xzvf /usr/lib/vmware/modules/source/vmmon.tar

cd vmmon-only/

make

cp vmmon.ko /lib/modules/2.6.32-504.el6.x86_64/misc/vmmon.ko

modprobe vmmon

Start the VM.

aalesilva
Contributor
Contributor

Hello! I try make this, but not work, always appear this error.

[root@tic34-linux vmmon-only]# make

Using standalone build system.

In file included from ./autoconf/geninclude.c:20:

./include/compat_autoconf.h:36:31: error: linux/autoconf.h: No such file or directory

In file included from .././autoconf/geninclude.c:20:

.././include/compat_autoconf.h:36:31: error: linux/autoconf.h: No such file or directory

Dependencies for driverLog.c

In file included from .././linux/driverLog.c:26:

.././include/driver-config.h:43:5: error: #error "No Module support in this kernel.  Please configure with CONFIG_MODULES"

make[1]: *** [driverLog.d] Error 1

make: *** [deps] Error 2

Smiley Sad

0 Kudos
aalesilva
Contributor
Contributor

Hello! Samas33, I try this option, but not work.

Tahnk's!Smiley Sad

0 Kudos
raz3k
Contributor
Contributor

yum install automake gcc kernel-devel

I think these should do the trick.

0 Kudos
aalesilva
Contributor
Contributor

Hi raz3k !

Thank you very much! For your help, now is working!

Smiley Happy:smileylaugh:

0 Kudos
Samas33
Contributor
Contributor

To raz3k:

many thanks. everything is working now. Smiley Happy

0 Kudos
cscarff
Contributor
Contributor

Yup, confirmed.  These raz3k's instructions work great.  Though at first I thought they didn't, but then a co-worker reminded me of your umask settings.

Sure enough, the "misc" directory under the .504 kernel directory was set to 500.  Once I compared the same directory under other kernel versions and corrected them vmware workstation started up fine.

Watch out for those silly security measures.  Darn umask settings.  Gets me everytime.

😕

Chris
0 Kudos
Robert0609
Contributor
Contributor

I had the same problem with 2.6.32-504 kernel, and other problems as well.

I reverted back to using the 2.6.32-431.29.2.el6.x86_64 kernel. I won't engage the 504 kernel again on any host.

0 Kudos
mntnbighker
Enthusiast
Enthusiast

In my case it was the CentOS 6.6 update that killed me. Rebuilding the modules didn't work, but reverting to the previous kernel version got my VM's starting again. Hopefully guidance will be forthcoming to get on the current kernel. Re-installing VMware Workstation didn't solve anything either.

0 Kudos
raz3k
Contributor
Contributor

mntbighker try the solution i posted above, for me it worked like a charm:

yum install automake gcc kernel-devel

cd /tmp

tar -xzvf /usr/lib/vmware/modules/source/vmmon.tar

cd vmmon-only/

make

cp vmmon.ko /lib/modules/2.6.32-504.el6.x86_64/misc/vmmon.ko

modprobe vmmon

Start the VM.

0 Kudos
mntnbighker
Enthusiast
Enthusiast

I tried rebuilding the module but it still didn't work with the new kernel. I think one of the problems is that those modules get built on boot. So even if you manually build the module, next time you reboot it will be broken again. If you look in the kernel modules directories for all of your kernel versions the only one that will have the VMware modules will be the booted system. At least that is the case on mine. So if you switch kernel versions the modules will be built at boot time in the "misc" directory. And the module you rebuilt in the other kernel directory will be gone.

0 Kudos
NobuoSha
Contributor
Contributor

,
Yes, you are right that the kernel modules will be rebuilt again (thus overwriting the one you put in manually) when it checks and decides that they have not been done yet. The following steps might help. Please give it a try and let me know how it goes:

# yum install make gcc kernel-devel kernel-headers-$(uname -r)

  • Do the following steps (again either as root or by using sudo):

# service vmware stop
# mv /usr/lib/vmware/modules/binary/bld-2.6.32-71.el6-x86_64-rhel6 /usr/lib/vmware/modules/binary/bld-2.6.32-71.el6-x86_64-rhel6-orig
# rm /lib/modules/$(uname -r)/misc/vmmon.ko
# vmware-modconfig --console --build-mod vmmon /usr/bin/gcc /lib/modules/$(uname -r)/build/include/
# depmod -a
# service vmware start

Then start the vmware workstation.

0 Kudos
mntnbighker
Enthusiast
Enthusiast

I guess my question is.. why go through all that drama if reverting the kernel one step restores operation? Will VMware release a Wkstn 10 patch that allows the newer kernel to work without all that messing about? It seem to me that at the moment you can't install VMware Workstation 10 on CentOS 6.6 or Redhat 6.6 freshly installed, so VMware has to do something, and fairly soon? Am I wrong?

0 Kudos
NobuoSha
Contributor
Contributor

In an ideal world, yes. But unless VMware can foresee the future -- the RHEL 6.6 was recently released and contains some changes that caused this pre-compiled kernel module to fail. Besides, the procedure I laid out is a one-time thing; i.e., once it's in place, you don't have to do it again when new kernels are released for RHEL/Centos 6.6 unless they make pretty drastic changes in the kernel again. 🙂

0 Kudos
mntnbighker
Enthusiast
Enthusiast

I guess I wonder what VMware will do to fix this, and will your "fix" get in the way of or break their fix?  😉  Or is it the advise of VMware to wait for their fix?  #facepalm

0 Kudos
NobuoSha
Contributor
Contributor

Well, I don't think my 'fix' will get in the future 'fix' released by VMware. But you have couple choices if you feel uneasy. One is to fall back to older kernel. The other is to wait to see if VMware will release a fix. (The Workstation 10.0.4 was released couple days ago but it's still broken on RHEL 6.6.) Or if yours is still under warranty, then bug them. 🙂

0 Kudos
mntnbighker
Enthusiast
Enthusiast

Like they said in the I Love Lucy laugh track:

Hahahahaahah... Oh oh 😞

I bought Wkstn 10 on 10/28/13 😞

In the immortal words of Maxwell Smart.. missed it by that much!

0 Kudos
NobuoSha
Contributor
Contributor

Oh.. no, on the same day as your first posting regarding this issue... 😞

0 Kudos