Not sure if anyone else is having nightmare issues on Fedora with VMware and others...
After getting through the issues with Kernel Headers, GCC, etc... so that installation is successful, I setup a machine and try to start it but get:
Error: Could not open /dev/vmmon: No such file or directory. Please make sure that the kernel module `vmmon' is loaded. |
I've done a lot of searching through VMwares KB's, Communities, as this appears to be a consistent issue. I've also gone through a lot of 3rd party sites too, but nothing is resolving.
I have used the following corrections but no luck:
mv /usr/lib/vmware/modules/binary /usr/lib/vmware/modules/binary.old
... See section below for rebuilding modules
Starting VMware services: Virtual machine monitor [FAILED] Virtual machine communication interface [ OK ] VM communication interface socket family [ OK ] Blocking file system [ OK ] Virtual ethernet [FAILED] VMware Authentication Daemon [ OK ] |
I'm sure there is something simple that I'm missing, right? It seems that before the service can work right, I need to get vmmon properly working?
Journalctl logs attached as well.
Thanks for your help!
I encountered exactly the same issue, and finally solved by disabling "Secure Boot" from BIOS.
When "Secure Boot" is enabled, unsigned kernel extensions will not allowed to be loaded. vmmon.ko and vmnet.ko are of course not signed with Fedora cert, so they just won't run.
Just came across post:
VMware v7 Linux ~ vmmon error.
which says to run:
mknod /dev/vmmon c 10 165
Did this and get an error that I've exceeded the max number of VM's... Reboot and old error returns...
dttd86 wrote:
Tried adding vmmon to kernel using: modprobe vmmon, but get error: modprobe: ERROR: could not insert 'vmmon' : Required key not available
Looking through [SOLVED] Need virtualization of some sort - FedoraForum.org, post #14, it makes me wonder if maybe this is failing due to a secure-boot issue and that I need a signed key? I did not see one anywhere, nor is it in my education edition links.
I encountered exactly the same issue, and finally solved by disabling "Secure Boot" from BIOS.
When "Secure Boot" is enabled, unsigned kernel extensions will not allowed to be loaded. vmmon.ko and vmnet.ko are of course not signed with Fedora cert, so they just won't run.
swarmfree wrote:
I encountered exactly the same issue, and finally solved by disabling "Secure Boot" from BIOS.
When "Secure Boot" is enabled, unsigned kernel extensions will not allowed to be loaded. vmmon.ko and vmnet.ko are of course not signed with Fedora cert, so they just won't run.
Perfect, that worked. Thanks again!
VMware Support, I think this would make an excellent KB Article as it is not mentioned anywhere.
Thanks dttd86! I've requested a KB to cover this issue.
thanks from egypt
It's so nice!