eon0jenny
Contributor
Contributor

"Could not open /dev/vmmon: No such file or directory. Please make sure that the kernel module `vmmon' is loaded."

Jump to solution

I installed vmware Player on an Open Suse linux machine (32 bit), from the provided .bundle file. It ran fine, and I could load my virtual machine file just fine. Then, my machine had a random power outage. When it rebooted, I could no longer use my virtual machine, always getting the error:

"Could not open /dev/vmmon: No such file or directory.

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

I look in /dev and sure enough, there is no vmmon. I see a lot of archived posts mentioning that you have to run the "vmware-config.pl script"....(specifically the following link: http://blog.solutionperspectivemedia.co.uk/?p=6)

but I didn't get this. It sounds like maybe this was a part of an older (non-bundle) install?

What should I do? Is this a known issue, as that website suggests? Or did the random outage cause something? I'm pretty confused.

1 Solution

Accepted Solutions
AndreiVajnaII
Enthusiast
Enthusiast

Have you tried uninstalling as root? Otherwise I think it won't work.

As for your original problem, I've had it, too, and this is what I did:

sudo mv /usr/lib/vmware/modules/binary /usr/lib/vmware/modules/binary.old

sudo vmware-modconfig --console --install-all --appname="VMware Player" --icon="vmware-player"

View solution in original post

14 Replies
eon0jenny
Contributor
Contributor

No answers, huh... Am I not being clear enough? Is my problem confusing? What can I do to make this question more attractive?

0 Kudos
eon0jenny
Contributor
Contributor

I just tried uninstalling VMware Player, and reinstalling it, to see if that would help (since it DID work right after install). Problem is, it won't let me uninstall it. It says it was uninstalled unsuccesfully every time I try:

vmware-installer -u vmware-player

Is it normal that it won't let me uninstall it?

AndreiVajnaII
Enthusiast
Enthusiast

Have you tried uninstalling as root? Otherwise I think it won't work.

As for your original problem, I've had it, too, and this is what I did:

sudo mv /usr/lib/vmware/modules/binary /usr/lib/vmware/modules/binary.old

sudo vmware-modconfig --console --install-all --appname="VMware Player" --icon="vmware-player"

View solution in original post

eon0jenny
Contributor
Contributor

I did indeed do it as root (couldn't even execute the command other wise) and no dice.

Yep, that actually did work: Thanks! It looks like it's just reinstalling it?

0 Kudos
AndreiVajnaII
Enthusiast
Enthusiast

From what I've read, this happens on OpenSUSE. VMware comes with some pre-built binaries which somehow don't work on this OS. So you're deleting them, and by running that tool they are built again, this time for your system.

Here is where I found the solution: http://forums.fedoraforum.org/showthread.php?t=206983

0 Kudos
eon0jenny
Contributor
Contributor

Hrrm...that does make sense I suppose, the only thing that confuses me is that I have to delete and reinstall the binaries every single time I turn my computer on. That is, the original problem shows back up after every power off. You'd think the binaries would, you know, stay good. This time I'm even turning VMware Player off correctly, and everything.

0 Kudos
AndreiVajnaII
Enthusiast
Enthusiast

Oh, damn! That shouldn't happen. For me it works ok.

Our problem was that after an install, it worked fine. Until the first restart that is. When we restarted the computer, the vmmon error would come up. But if we applied the solution I just gave you, that wouldn't happen and it all works ok after any restart.

Perhaps if you could uninstall and install again? How is it going with that problem?

0 Kudos
farkasharry
Hot Shot
Hot Shot

I had the same problem and thanks to your comment I could fix it! great, thanks!

*** If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful! *** vExpert 2019, VCAP-DCA,VCP,MCSE,MCITS and some more...
0 Kudos
tgraupmann
Contributor
Contributor

sudo modprobe vmmon

PJAL
Contributor
Contributor

I am experiencing this error too. Anytime I even check for Linux updates vmware forces the console module to be rebuilt. This is SOP anytime new Linux RPMs are applied since vmware must know about kernel updates. However, it should not be necessary to rebuild the console module unless updates are applied to the system. This is a vmware bug and it is very annoying. Please include a fix in the next update. I am using vmware-player 3.1.1. This bug was not present in version 3.1

0 Kudos
misterich
Contributor
Contributor

I realize I am a Johnny-come-lately here....

I hit this problem today using Ubuntu 12.04 (Precise Pangolin) and VMPlayer 4.0.2.  Indeed, it is very annoying.  Judging by the greif that some have posted here and elsewhere (specifically that it keeps bloody occuring), I created a script to apply the fix on an as-needed basis (attached).

System Details:

#    Description:     Ubuntu 12.04 LTS
#    Codename:          precise
#    Linux watson 3.2.0-24-generic #39-Ubuntu SMP Mon May 21 16:52:17 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
#    VMware Player 4.0.2 build-591240
0 Kudos
youngwha
Contributor
Contributor

Thanks misterich!

Your patch works pretty well at 4.0.4(build 744019) as well.

0 Kudos
sshetty
VMware Employee
VMware Employee

Given specifically the case you have, can you check if the information on this Knowledge base helps?

http://kb.vmware.com/kb/1007454

0 Kudos
BeanheadTux
Contributor
Contributor

There is no need to reinstall.

sudo modprobe vmmon

will load the kernel module needed.

Then it may ask for vmci when the VM starts

sudo modprobe vmci

Then you should be running.

my system is ubuntu 13.04 and vmware workstation 8 X64

0 Kudos