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

Would it be possible to add a systemctl command to enable the vmware-usbarbitrator service and to start it? I had to do this manually to enable access to my USB Camera and USB Drives via virtual machines.

@jihem Thank you so very much. I applied the previously mentioned
patches:
https://github.com/mkubecek/vmware-host-modules/commit/4232f780eb114f22498f3274eaeef81d8c63f2ab.patch
https://github.com/mkubecek/vmware-host-modules/commit/9a6a17fe0bc6d1ab9e0e0dfa8d587b12a21cd49e.patch
and it built and installed like magic:

# dkms install -m vmware-workstation -v 16.2.1_18811642 -k 5.16.0-rc1-archeract

Building module:
cleaning build area...
make -j2 KERNELRELEASE=5.16.0-rc1-archeract KVERSION=5.16.0-rc1-archeract SRCDIR=/usr/src/vmware-workstation-16.2.1_18811642......

Running the post_build script:
Signing module: ../5.16.0-rc1-archeract/x86_64/module/vmmon.ko.zst
Signing module: ../5.16.0-rc1-archeract/x86_64/module/vmnet.ko.zst
cleaning build area...

vmmon.ko.zst:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /usr/lib/modules/5.16.0-rc1-archeract/kernel/drivers/misc/

vmnet.ko.zst:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /usr/lib/modules/5.16.0-rc1-archeract/kernel/drivers/net/
depmod.............

@jihem The latest patches completely solved my dkms building errors on 5.15.2-zen, thanks!

@aritra1911 I tried to add the patches https://github.com/mkubecek/vmware-host-modules/commit/4232f780eb114f22498f3274eaeef81d8c63f2ab and https://github.com/mkubecek/vmware-host-modules/commit/9a6a17fe0bc6d1ab9e0e0dfa8d587b12a21cd49e in vmmon.patch and vmnet.patch but I still have an error during compilation (using this kernel: https://aur.archlinux.org/packages/linux-mainline) and I don't know how to fix it.

@k1f0 it compiles for me with 5.15.2.zen1-1. Can you provide the content of /var/lib/dkms/vmware-workstation/16.2.1_18811642/build/make.log?

dkms fails to build for kernel version 5.16.0-rc1

# cat /proc/version
Linux version 5.16.0-rc1-archeract (ray@archeract) (gcc (GCC) 11.1.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP Tue Nov 16 08:54:21 IST 2021

# dkms install --no-depmod -m vmware-workstation -v 16.2.1_18811642 -k 5.16.0-rc1-archeract

Building module:
cleaning build area...
make -j2 KERNELRELEASE=5.16.0-rc1-archeract KVERSION=5.16.0-rc1-archeract SRCDIR=/usr/src/vmware-workstation-16.2.1_18811642...(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.16.0-rc1-archeract (x86_64)
Consult /var/lib/dkms/vmware-workstation/16.2.1_18811642/build/make.log for more information.

Contents of make.log : https://paste.debian.net/plain/1219697
kernel's .config : https://gist.githubusercontent.com/aritra1911/52cffb8ff0c1aa0138d9342d1d7f98dd/raw/ccf14267c5df135c8fa40141f7e5dd09b1c2dfb4/gistfile1.txt

dkms install fails for me with latest 5.15 Kernel:

(3/3) Install DKMS modules
==> dkms install --no-depmod vmware-workstation/16.2.1_18811642 -k 5.15.2zen1-1-zen
Error! Bad return status for module build on kernel: 5.15.2-zen1-1-zen (x86_64)
Consult /var/lib/dkms/vmware-workstation/16.2.1_18811642/build/make.log for more information.
==> WARNING: `dkms install --no-depmod vmware-workstation/16.2.1_18811642 -k5.15.2-zen1-1-zen' exited 10

Hi! Could you include the patch mentioned here: https://superuser.com/a/1453932 Without this patch, the guest VM's network will continuously disconnected whenever DHCP lease is over.

-- vmnet-only/userif.c  2017-12-21 17:02:28.555820933 +0100
+++ vmnet-only.jjk/userif.c 2017-12-15 13:22:13.257724953 +0100
@@ -973,6 +973,9 @@
    userIf = (VNetUserIF *)port->jack.private;
    hubJack = port->jack.peer;

+   /* never send link down events */
+   if (!linkUp) return 0;
+
    if (port->jack.state == FALSE || hubJack == NULL) {
       return -EINVAL;
    }

If you get the error with vmmon just use the following command: sudo rmmod vmw_vmci vmmon; sudo modprobe -a vmw_vmci vmmon; sudo systemctl restart vmware-networks.service; sudo systemctl restart vmware-usbarbitrator.service;

If your vm has no internet access but got an ip address use this command: sudo pacman -S dhcpcd && sudo systemctl enable --now dhcpcd.service

This should work

Please, excuse me, I shared a wrong log in my first comment. It was failing for other reason.

The actual fail is this:

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.