VMware Communities
andrewch
Contributor
Contributor

Unable to build vmmon and vmnet (Workstation 17.0) Linux Mint 21.1 with kernel 5.19.0-32-generic

I have installed workstation 17.0 this day, and got some errors when starting up a vm "/dev/vmmon: No such file or directory. Please make sure that the kernel module "vmmon" is loaded", "Failed to initialize monitor device." and "Unable to change virtual machine power state: Transport (VMDB) error -14: Pipe connection has been broken." . I did search on the internet but nothing helped me. Then I tried "sudo vmware-modconfig --console --install-all --appname="VMware Player" --icon="vmware-player" " which surprise surprise did not work either. here is the log of the command

Reply
0 Kudos
6 Replies
andrewch
Contributor
Contributor

Nope, didn't work. I still get this: 
Starting VMware services:
Virtual machine monitor failed
Virtual machine communication interface done
VM communication interface socket family done
Virtual ethernet failed
VMware Authentication Daemon done

Reply
0 Kudos
hwimmer
Contributor
Contributor

Please tell me you found a fix? I want to upgrade to 17 but I have mission critical VMs I run and am afraid. I had this vmmon thing under version 16. Basically, downloaded some files from github and replaced them in the VMWare installation folder...

I would be happy to give more information if you want to try it. 

Reply
0 Kudos
hwimmer
Contributor
Contributor

testing a sample reply to see if i get an email notification.

Reply
0 Kudos
hwimmer
Contributor
Contributor

I am giving up that anyone checks this stuff. If anyone has an answer please email me

Reply
0 Kudos
louyo
Virtuoso
Virtuoso

Well, you asked a person a question and they didn't answer.

I get notices because I made a reply above. Are you having that same problem? If so the most common reason for the error is updating the kernel to a version that isn't supported. Some distros are leading edge and go faster than Vmware. Fortunately a user provides patches, created on his own time, to update the source files.

This is a user to user forum, Vmware employees will occasionally stop by but rarely participate.

If you are not getting any errors, maybe you should state what your host is and the kernel level, operating system, etc. If you are not having a problem with version 16, when you install or open WS, I would not think that an upgrade to 17 would make a difference as long as your hardware and host OS is compatible. 

 

Reply
0 Kudos