Closed Cesarsk closed 1 year ago
If you did only that, you did not reload the newly built module. Also, did you check that the module is actually loaded as the error message tells you?
@mkubecek any idea on how to reload the newly built module ?
The easiest way is to run /etc/init.d/vmware restart
(as suggested in the INSTALL
file).
I have tried that, still not working, sadly. @mkubecek
systemctl daemon-reload
systemctl restart vmware
Job for vmware.service failed because the control process exited with error code.
See "systemctl status vmware.service" and "journalctl -xeu vmware.service" for details.
systemctl status vmware
× vmware.service - SYSV: This service starts and stops VMware services
Loaded: loaded (/etc/rc.d/init.d/vmware; generated)
Active: failed (Result: exit-code) since Sun 2023-03-12 12:27:56 CET; 2s ago
Docs: man:systemd-sysv-generator(8)
Process: 38059 ExecStart=/etc/rc.d/init.d/vmware start (code=exited, status=1/FAILURE)
Tasks: 1 (limit: 18791)
Memory: 7.0M
CPU: 46ms
CGroup: /system.slice/vmware.service
└─1513 /usr/sbin/vmware-authdlauncher
Mar 12 12:27:56 fedora vmware[38059]: Virtual machine communication interface[ OK ]
Mar 12 12:27:56 fedora vmware[38059]: VM communication interface socket family[ OK ]
Mar 12 12:27:56 fedora vmware[38059]: Virtual ethernet[FAILED]
Mar 12 12:27:56 fedora vmware[38059]: VMware Authentication Daemon[ OK ]
Mar 12 12:27:56 fedora systemd[1]: vmware.service: Control process exited, code=exited, status=1/FAILURE
Mar 12 12:27:56 fedora systemd[1]: vmware.service: Failed with result 'exit-code'.
Mar 12 12:27:56 fedora systemd[1]: vmware.service: Unit process 1513 (vmware-authdlau) remains running after unit stopped.
Mar 12 12:27:56 fedora systemd[1]: vmware.service: Unit process 38110 (vmware-authdlau) remains running after unit stopped.
Mar 12 12:27:56 fedora systemd[1]: vmware.service: Unit process 38111 (logger) remains running after unit stopped.
Mar 12 12:27:56 fedora systemd[1]: Failed to start vmware.service - SYSV: This service starts and stops VMware services.
Then try to unload and load the modules manually and see what happens.
This can be closed.
I solved by re-enrolling the keys for vmmon and vmnet after the kernel update. I noticed they got lost going into the BIOS.
:)
Hello. After update to kernel 6.1.15-200 the installation of the modules is not working properly anymore.
What I get is
could not open /dev/vmmon: No such file or directory. Please make sure that the kernel module 'vmmon' is loaded. Failed to initialize monitor device
This happens when I try to start my VM.
The steps to install are
make
sudo make install