VMware Communities
kjmn
Contributor
Contributor

Failed to start SYSV: This service starts and stops VMware services.

Need help !

My VMware Workstation 15 Pro started experiencing this error: Failed to start SYSV: This service starts and stops VMware services. I cannot make this service go up with the command systemctl start vmware.service. I have already uninstalled and installed again and the error persists. Guys what is this error and how to solve? Do you have a correction path? I use the fedora 32 kernel 5.7.Me help please!

Output:

systemctl status vmware.service

● 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 Sat 2020-07-04 22:09:09 -03; 2min 5s ago

       Docs: man:systemd-sysv-generator(8)

        CPU: 237ms

jul 04 22:09:09 vostro3560 vmware[20570]: [44B blob data]

jul 04 22:09:09 vostro3560 systemd[1]: vmware.service: Control process exited, code=exited, status=1/FAILURE

jul 04 22:09:09 vostro3560 systemd[1]: vmware.service: Failed with result 'exit-code'.

jul 04 22:09:09 vostro3560 systemd[1]: Failed to start SYSV: This service starts and stops VMware services.

jul 04 22:10:30 vostro3560 vmnetBridge[19444]: RTM_NEWLINK: name:wlp8s0 index:3 flags:0x00001002

jul 04 22:10:35 vostro3560 vmnetBridge[19444]: Can't open vmnet device /dev/vmnet0 (No such device or address).

jul 04 22:10:35 vostro3560 vmnetBridge[19444]: RTM_NEWLINK: name:wlp8s0 index:3 flags:0x00001002

jul 04 22:10:40 vostro3560 vmnetBridge[19444]: Can't open vmnet device /dev/vmnet0 (No such device or address).

jul 04 22:10:40 vostro3560 vmnetBridge[19444]: RTM_NEWLINK: name:wlp8s0 index:3 flags:0x00001003

jul 04 22:10:45 vostro3560 vmnetBridge[19444]: Can't open vmnet device /dev/vmnet0 (No such device or address).

Tags (1)
Reply
0 Kudos
2 Replies
louiswust
Contributor
Contributor

This happens occasionally on Fedora due to very new kernel versions. You'll probably see that both of these services failed:

# systemctl list-units --state=failed

UNIT                             LOAD    ACTIVE

vmware.service                    loaded  failed

vmware-workstation-server.service loaded  failed

And you'll probably see that the vmmon and vmnet kernel modules are missing:

# vmware-modconfig --console --install-status

vmmon: unknown

vmnet: unknown

vmci: other

vsock: other

In order to fix this, you need to either revert to a supported kernel version — the last one which worked for me was 5.6.19-300.fc32.x86_64 — or you'll need to follow the (reasonably straightforward) instructions to compile the kernel modules yourself using this repository:

GitHub - mkubecek/vmware-host-modules: Patches needed to build VMware (Player and Workstation) host ...

Reply
0 Kudos
watcher1
Enthusiast
Enthusiast

I'm running VMware 15.5.6 on Linux 5.7.7 (Fedora). Applying the patch successfully allowed VMware to run, however I've found that Drag&Drop only works one way. I can drag from Host to Guest fine, but attempting to drag or copy from Guest to Host produces an error such as:

Error when getting information for file “/Hj1Ipo/asdf.txt”: No such file or directory

The directory indicated does not exist and seems to be randomly generated. This was just a test "txt" file on the guest desktop.

I get the same error from both Linux and Windows Guests, although the non-existant directory changes.

... also Shared Folders don't work but USB does.

I've left a comment with the patch author.

Reply
0 Kudos