Vmware can’t start network service

Erz3 · 26 October 2021 21:08

Dear Manjaro comunity, I need help with this problem

At the moment I run Manjaro with kernel 5.10 and I am trying to start vmware-networks.service , however I get error code “status 1”.

My problem is so similar to an other topic posted here but don’t work for me that solution. I have been looking on /usr/lib/modules/5.10.70-1-MANJARO , however I have not found any “vmware” module there:

ls /usr/lib/modules/5.10.70-1-MANJARO 
extramodules	   modules.builtin.alias.bin  modules.order
kernel		   modules.builtin.bin	      modules.softdep
kernelbase	   modules.builtin.modinfo    modules.symbols
modules.alias	   modules.dep		      modules.symbols.bin
modules.alias.bin  modules.dep.bin	      pkgbase
modules.builtin    modules.devname	      vmlinuz

Neither here:

ls /usr/lib/modules/extramodules-5.10-MANJARO 
nvidia-drm.ko.gz  nvidia-modeset.ko.gz	version
nvidia.ko.gz	  nvidia-uvm.ko.gz

Here you have service status:

vmware-networks.service - VMware Networks
     Loaded: loaded (/usr/lib/systemd/system/vmware-networks.service; disable>
     Active: failed (Result: exit-code) since Tue 2021-10-26 21:41:29 WEST; 2>
    Process: 2645 ExecStartPre=/sbin/modprobe vmnet (code=exited, status=1/FA>
    Process: 2646 ExecStart=/usr/bin/vmware-networks --start (code=exited, st>
        CPU: 75ms

oct 26 21:41:29 sedentario vmware-networks[2646]: Failed to start DHCP servic>
oct 26 21:41:29 sedentario vmware-networks[2646]: Failed to start NAT service>
oct 26 21:41:29 sedentario vmware-networks[2646]: Failed to enable hostonly v>
oct 26 21:41:29 sedentario vmware-networks[2646]: Failed to start DHCP servic>
oct 26 21:41:29 sedentario vmware-networks[2646]: Failed to start some/all se>
oct 26 21:41:29 sedentario vmware-networks[2646]: Started Bridge networking o>
oct 26 21:41:29 sedentario systemd[1]: vmware-networks.service: Control proce>
oct 26 21:41:29 sedentario vmnetBridge[2664]: Bridge process exiting.
oct 26 21:41:29 sedentario systemd[1]: vmware-networks.service: Failed with r>
oct 26 21:41:29 sedentario systemd[1]: Failed to start VMware Networks.

Also journalctl:

journalctl -xeu vmware-networks.service
oct 26 21:36:54 sedentario vmnetBridge[2385]: RTM_NEWLINK: name:enp6s0 index:>
oct 26 21:36:54 sedentario vmnetBridge[2385]: Adding interface enp6s0 index:2
oct 26 21:36:54 sedentario vmnetBridge[2385]: Can't open vmnet device /dev/vm>
oct 26 21:36:54 sedentario vmnetBridge[2385]: RTM_NEWROUTE: index:2
oct 26 21:36:54 sedentario vmnetBridge[2385]: Can't open vmnet device /dev/vm>
oct 26 21:36:55 sedentario vmware-networks[2367]: Failed to enable hostonly v>
oct 26 21:36:55 sedentario vmware-networks[2367]: Failed to start DHCP servic>
oct 26 21:36:55 sedentario vmware-networks[2367]: Failed to start NAT service>
oct 26 21:36:55 sedentario vmware-networks[2367]: Failed to enable hostonly v>
oct 26 21:36:55 sedentario vmware-networks[2367]: Failed to start DHCP servic>
oct 26 21:36:55 sedentario vmware-networks[2367]: Failed to start some/all se>
oct 26 21:36:55 sedentario vmware-networks[2367]: Started Bridge networking o>
oct 26 21:36:55 sedentario systemd[1]: vmware-networks.service: Control proce>
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ An ExecStart= process belonging to unit vmware-networks.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
oct 26 21:36:55 sedentario vmnetBridge[2385]: Bridge process exiting.
oct 26 21:36:55 sedentario systemd[1]: vmware-networks.service: Failed with r>
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ The unit vmware-networks.service has entered the 'failed' state with resul>
oct 26 21:36:55 sedentario systemd[1]: Failed to start VMware Networks.
░░ Subject: A start job for unit vmware-networks.service has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit vmware-networks.service has finished with a failure.
░░ 
░░ The job identifier is 1824 and the job result is failed.
lines 58-92/92 (END)
oct 26 21:36:53 sedentario modprobe[2366]: modprobe: FATAL: Module vmnet not found in directory /lib/modules/5.10.70-1-MANJARO
oct 26 21:36:54 sedentario vmnetBridge[2385]: Bridge process created.
-- Journal begins at Fri 2021-04-09 00:35:32 WEST, ends at Tue 2021-10-26 21:36:59 WEST. --
oct 26 21:27:55 sedentario systemd[1]: Starting VMware Networks...
░░ Subject: A start job for unit vmware-networks.service has begun execution
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit vmware-networks.service has begun execution.
░░ 
░░ The job identifier is 1941.
oct 26 21:27:55 sedentario modprobe[21018]: modprobe: FATAL: Module vmnet not found in directory /lib/modules/5.10.70-1-MANJARO
oct 26 21:27:55 sedentario vmnetBridge[21037]: Bridge process created.
oct 26 21:27:55 sedentario vmnetBridge[21037]: RTM_NEWLINK: name:enp6s0 index:2 flags:0x00011043
oct 26 21:27:55 sedentario vmnetBridge[21037]: Adding interface enp6s0 index:2
oct 26 21:27:55 sedentario vmnetBridge[21037]: Can't open vmnet device /dev/vmnet0 (No such device or address).
oct 26 21:27:55 sedentario vmnetBridge[21037]: RTM_NEWROUTE: index:2
oct 26 21:27:55 sedentario vmnetBridge[21037]: Can't open vmnet device /dev/vmnet0 (No such device or address).
oct 26 21:27:56 sedentario vmware-networks[21019]: Failed to enable hostonly virtual adapter on vmnet1
oct 26 21:27:56 sedentario vmware-networks[21019]: Failed to start DHCP service on vmnet1
oct 26 21:27:56 sedentario vmware-networks[21019]: Failed to start NAT service on vmnet8
oct 26 21:27:56 sedentario vmware-networks[21019]: Failed to enable hostonly virtual adapter on vmnet8
oct 26 21:27:56 sedentario vmware-networks[21019]: Failed to start DHCP service on vmnet8
oct 26 21:27:56 sedentario vmware-networks[21019]: Failed to start some/all services
oct 26 21:27:56 sedentario vmware-networks[21019]: Started Bridge networking on vmnet0
oct 26 21:27:56 sedentario systemd[1]: vmware-networks.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ An ExecStart= process belonging to unit vmware-networks.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
oct 26 21:27:56 sedentario vmnetBridge[21037]: Bridge process exiting.
oct 26 21:27:56 sedentario systemd[1]: vmware-networks.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ The unit vmware-networks.service has entered the 'failed' state with result 'exit-code'.
oct 26 21:27:56 sedentario systemd[1]: Failed to start VMware Networks.
░░ Subject: A start job for unit vmware-networks.service has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit vmware-networks.service has finished with a failure.
░░ 
░░ The job identifier is 1941 and the job result is failed.
-- Boot c4f64563ead94a39b68b470658f9a5d8 --
oct 26 21:36:53 sedentario systemd[1]: Starting VMware Networks...
░░ Subject: A start job for unit vmware-networks.service has begun execution
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit vmware-networks.service has begun execution.
░░ 
░░ The job identifier is 1824.
oct 26 21:36:53 sedentario modprobe[2366]: modprobe: FATAL: Module vmnet not found in directory /lib/modules/5.10.70-1-MANJARO
oct 26 21:36:54 sedentario vmnetBridge[2385]: Bridge process created.
oct 26 21:36:54 sedentario vmnetBridge[2385]: RTM_NEWLINK: name:enp6s0 index:2 flags:0x00011043
oct 26 21:36:54 sedentario vmnetBridge[2385]: Adding interface enp6s0 index:2
oct 26 21:36:54 sedentario vmnetBridge[2385]: Can't open vmnet device /dev/vmnet0 (No such device or address).
oct 26 21:36:54 sedentario vmnetBridge[2385]: RTM_NEWROUTE: index:2
oct 26 21:36:54 sedentario vmnetBridge[2385]: Can't open vmnet device /dev/vmnet0 (No such device or address).
oct 26 21:36:55 sedentario vmware-networks[2367]: Failed to enable hostonly virtual adapter on vmnet1
oct 26 21:36:55 sedentario vmware-networks[2367]: Failed to start DHCP service on vmnet1
oct 26 21:36:55 sedentario vmware-networks[2367]: Failed to start NAT service on vmnet8
oct 26 21:36:55 sedentario vmware-networks[2367]: Failed to enable hostonly virtual adapter on vmnet8
oct 26 21:36:55 sedentario vmware-networks[2367]: Failed to start DHCP service on vmnet8
oct 26 21:36:55 sedentario vmware-networks[2367]: Failed to start some/all services
oct 26 21:36:55 sedentario vmware-networks[2367]: Started Bridge networking on vmnet0
oct 26 21:36:55 sedentario systemd[1]: vmware-networks.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ An ExecStart= process belonging to unit vmware-networks.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.

Thanks you in advance.

sawdoctor · 26 October 2021 21:32

Not sure if it helps but for me I installed vmware workstation from the aur and then vmware tools. That seemed to fix the network issue for me

Erz3 · 27 October 2021 16:40

Thanks you @sawdoctor but don’t work .

(vmware-tools was out of date so I have tested with vmware-open-tools too)

I suppose that Open-VM-Tools is to run Manjaro or Arch Linux like a guest, that’s why it fails me running it such as host.

cfinnberg · 27 October 2021 20:00

VMWare modules are compiled at (vmware’s AUR package) installation time. But you need to have kernel headers for your kernel installed beforehand.

So, install linux510-headers package and then reinstall vmware package from AUR.

Erz3 · 28 October 2021 18:53

@cfinnberg thanks you.

Now I can load manually the specified modules, however * vmware-networks.service* continue without work:

oct 28 19:48:25 sedentario systemd[1]: Starting VMware Networks...
░░ Subject: A start job for unit vmware-networks.service has begun execution
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit vmware-networks.service has begun execution.
░░ 
░░ The job identifier is 2942.
oct 28 19:48:25 sedentario vmnetBridge[14673]: Bridge process created.
oct 28 19:48:25 sedentario vmnetBridge[14673]: RTM_NEWLINK: name:enp6s0 index:2 flags:0x00011043
oct 28 19:48:25 sedentario vmnetBridge[14673]: Adding interface enp6s0 index:2
oct 28 19:48:25 sedentario vmnetBridge[14673]: Started bridge enp6s0 to virtual network 0.
oct 28 19:48:25 sedentario vmnetBridge[14673]: RTM_NEWROUTE: index:2
oct 28 19:48:26 sedentario vmware-networks[14655]: Failed to start DHCP service on vmnet1
oct 28 19:48:26 sedentario vmware-networks[14655]: Failed to start NAT service on vmnet8
oct 28 19:48:26 sedentario vmware-networks[14655]: Failed to start DHCP service on vmnet8
oct 28 19:48:26 sedentario vmware-networks[14655]: Failed to start some/all services
oct 28 19:48:26 sedentario vmware-networks[14655]: Started Bridge networking on vmnet0
oct 28 19:48:26 sedentario vmware-networks[14655]: Enabled hostonly virtual adapter on vmnet1
oct 28 19:48:26 sedentario vmware-networks[14655]: Enabled hostonly virtual adapter on vmnet8
oct 28 19:48:26 sedentario systemd[1]: vmware-networks.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ An ExecStart= process belonging to unit vmware-networks.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
oct 28 19:48:26 sedentario vmnetBridge[14673]: Stopped bridge enp6s0 to virtual network 0.
oct 28 19:48:26 sedentario vmnetBridge[14673]: Bridge process exiting.
oct 28 19:48:26 sedentario systemd[1]: vmware-networks.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ The unit vmware-networks.service has entered the 'failed' state with result 'exit-code'.
oct 28 19:48:26 sedentario systemd[1]: Failed to start VMware Networks.
░░ Subject: A start job for unit vmware-networks.service has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit vmware-networks.service has finished with a failure.
░░ 
░░ The job identifier is 2942 and the job result is failed.

cfinnberg · 28 October 2021 20:11

Can you again provide the journalctl log about this? That gives significant information about what is actually happening.

Erz3 · 2 November 2021 00:56

Here you go again:

nov 02 00:53:08 sedentario systemd[1]: Starting VMware Networks...
░░ Subject: A start job for unit vmware-networks.service has begun execution
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit vmware-networks.service has begun execution.
░░ 
░░ The job identifier is 3547.
nov 02 00:53:08 sedentario vmnetBridge[10713]: Bridge process created.
nov 02 00:53:08 sedentario vmnetBridge[10713]: RTM_NEWLINK: name:enp6s0 index:2 flags:0x00011043
nov 02 00:53:08 sedentario vmnetBridge[10713]: Adding interface enp6s0 index:2
nov 02 00:53:08 sedentario vmnetBridge[10713]: Started bridge enp6s0 to virtual network 0.
nov 02 00:53:08 sedentario vmnetBridge[10713]: RTM_NEWROUTE: index:2
nov 02 00:53:09 sedentario vmware-networks[10695]: Failed to start DHCP service on vmnet1
nov 02 00:53:09 sedentario vmware-networks[10695]: Failed to start NAT service on vmnet8
nov 02 00:53:09 sedentario vmware-networks[10695]: Failed to start DHCP service on vmnet8
nov 02 00:53:09 sedentario vmware-networks[10695]: Failed to start some/all services
nov 02 00:53:09 sedentario vmware-networks[10695]: Started Bridge networking on vmnet0
nov 02 00:53:09 sedentario vmware-networks[10695]: Enabled hostonly virtual adapter on vmnet1
nov 02 00:53:09 sedentario vmware-networks[10695]: Enabled hostonly virtual adapter on vmnet8
nov 02 00:53:09 sedentario systemd[1]: vmware-networks.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ An ExecStart= process belonging to unit vmware-networks.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
nov 02 00:53:09 sedentario vmnetBridge[10713]: Stopped bridge enp6s0 to virtual network 0.
nov 02 00:53:09 sedentario vmnetBridge[10713]: Bridge process exiting.
nov 02 00:53:09 sedentario systemd[1]: vmware-networks.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ The unit vmware-networks.service has entered the 'failed' state with result 'exit-code'.
nov 02 00:53:09 sedentario systemd[1]: Failed to start VMware Networks.
░░ Subject: A start job for unit vmware-networks.service has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit vmware-networks.service has finished with a failure.
░░ 
░░ The job identifier is 3547 and the job result is failed.

cfinnberg · 2 November 2021 13:18

Does sudo modprobe vmnet work for you?

Do you have /dev/vmnet0, /dev/vmnet1 and /dev/vmnet8?

Erz3 · 2 November 2021 16:57

@cfinnberg ** sudo modprobe vmnet** work for me.

Nope, this is what I have:

$ ls /dev/vm*        
/dev/vmci  /dev/vmmon

Also, you should need to know that Vmware fail when I try to run it. Check it:

$ vmware
zsh: segmentation fault (core dumped)  vmware

Probably, the reason behind that have been because the firs time I installed Vmware, I did with the installer that their provide on Vmware’s website. After that, I removed manually (following the steps of this website) because I decided to install it through Manjaro repository. In resume, something there is not working properly for that.