Arch Linux User Repository

After the first installation, please:

1) install the appropriate headers package(s) for your installed kernel(s): linux-headers for default kernel, linux-lts-headers for LTS kernel...

2) reboot or load vmw_vmci and vmmon kernel modules (modprobe -a vmw_vmci vmmon)

3) Enable the services you need (using .service units to activate them during boot or .path units to activate them when a VM is started) :

• vmware-networks: to have network access inside VMs

• vmware-usbarbitrator: to connect USB devices inside VMs

@Erz3

I would check the output of mkinitcpio -P. It is supposed to run automatically but something probably wrong happened at this step, or you simply forgot to reboot your system.

Hi,

Could someone help me with this issue? I have installed vmware-workstation 16.2.0-1 on my Manjaro with kernel version 5.10.70-1 (LTS), after that linux-headers and finally I have loaded modules. However when I try to start vmware-networks.service it fail with code error "status 1".

journalctl result:

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.

@jihem, thank you very much for your to the point and prompt reply! You're awesome! :)

So I did as you said. I first ran the "vmware-netcfg" command, to make sure that the "Use local DHCP service to distribute IP addresses to VMs" option was checked.

I then proceeded with the rest of your instructions. I brought the "vmware-networks.service" down by running "sudo systemctl stop vmware-networks.service", then I got rid of the aforementioned files and folders using "sudo rm -r /etc/vmware/{networking,netmap.conf,vmnet*}". Finally I brought the "vmware-networks.service" back up again using "sudo systemctl start vmware-networks.service".

That fixed all the issues. I noticed that all the deleted files and folders were created anew, and the vmnet* subnets had also changed. The VMs are now able to pick up the IPs upon boot. Thank you so much jihem!

sh1sh1n11: Firstly, check if your virtual network has DHCP enabled. For that, start vmware-netcfg and check if, in the network interface used by your VM, the option "Use local DHCP service to distribute IP addresses to VMs" is activated.

If it is not the problem, you can try to reinitialize network settings. Stop all running VMs and run the following commands:

systemctl stop vmware-networks.service
rm -r /etc/vmware/{networking,netmap.conf,vmnet*}
systemctl start vmware-networks.service

Hi,

Thank you for this package! I've run into an issue where none of my VM's are getting an IP address issued. I am currently on Manjaro Linux Kernel 5.10.56-1-MANJARO (I know. But since it is an Arch Linux derivative, here I am.).

Interestingly, when I edit the "/etc/vmware/vmnet8/dhcpd/dhcpd.leases" file manually, and assign an IP to my VM, then it is able to assign that IP to itself upon boot.

I could only get as far as understanding that Manjaro Linux (and maybe even Arch for that matter) does not have dhcpd service, and instead it has the dhcpcd service. where as the "vmware-networks.service" seems to be running "/usr/bin/vmnet-dhcpd". How can I make it so that I don't have to manually add IPs to the dhcpd.leases file, and the VMs get IPs on boot automatically. Any help in the matter would be awesome! Thank you all.

I got an error while installing: error: could not extract /usr/lib/vmware/isoimages/VirtualPrinter-Windows.iso (Truncated zstd input)

What can be wrong?

No idea why gorgiaxx didn't have the libdir variable set, but I can confirm that AUR packages are generating .pacnew files; actually AUR packages work exactly like official packages, the only difference is that they are not built and distributed by official maintainers.

@class101 To explain my choices, I finally didn't use the PathModified variable because it triggers not only file creation, but also file deletion and modification. During some tests, on one moment I wanted to "reset" my environment by stopping VMware services and removing /run/vmware directory; I realized that removing this directory restarted VMware services, which was clearly not the expected behavior. I know it's not a big deal because probably nobody will touch this directory in real conditions, but I find the PathExistsGlob solution more adapted: when a directory of this pattern is created, I am sure that it correspond to the start of a VM. Also, if a VMware service is stopped whereas at least one VM is still running, the corresponding directory still exists so the service is restarted immediately.

I admit I haven't thought about the performance cost of using regular expressions, but in my opinion it is not significant (systemd probably check a filename matching only when there is a change in /var/run/vmware folder, which happen only when a VM is started or stopped).

About services handling, I just follow what is generally made by maintainers which is to not start services by default (except for some core components). It's especially relevant here because these services are not required for VM execution and some users could want to let them disabled. As you said in a previous message: "It is a good practice under Linux to have the fewest permanent services running" :)