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

For multiple monitors feature with Awesome WM, see this workaround: https://github.com/awesomeWM/awesome/pull/2188

@jihem you're absolutely right. I thought headers was a requirement and didn't checked as I should. Thank you a lot.

Hi joelteixeira,

This package should work with Linux 4.15. If it's a fresh installation you have probably forgotten to install the linux-headers package.

Hi all, 4.15 had broke something? I was using normally on a 4.14 machine but on a fresh installed system I got:

Could not open /dev/vmmon: No such file or directory. Please make sure that the kernel module 'vmmon' is loaded.

And trying to load vmmon:

modprobe vmmon <br> modprobe: FATAL: Module vmmon not found in directory /lib/modules/4.15.1-2-ARCH

uname -a Linux hostname 4.15.1-2-ARCH #1 SMP Sun Feb 4 22:27:45 UTC 2018 x86_64 GNU/Linux

Are you guys facing something similar?

@ailick: I don't have any problem with this version on the kernel on Arch, I think it's more probably a problem with Manjaro.

I don't have time to investigate your problem and I don't really know Manjaro, but my idea is that the version of GCC used to compile the kernel is more recent than the version of GCC installed on your system which doesn't already include the patch retpoline. If I'm right (not sure at all), you have 2 solutions: downgrade your kernel on the previous version until a new version of GCC, or use a more recent version of GCC (for example from testing repo if there is a testing repo in Manjaro).

Edit: I just discovered a tip that can help you: after the startup, loading vmmon module with: modprobe --force-vermagic vmmon

Something is not going well on 'kernel 4.14.15'

[ 7.885870] vmmon: version magic '4.14.15-1-MANJARO SMP preempt mod_unload modversions retpoline ' should be '4.14.15-1-MANJARO SMP preempt mod_unload modversions '

[ 14.081850] vmmon: version magic '4.14.15-1-MANJARO SMP preempt mod_unload modversions retpoline ' should be '4.14.15-1-MANJARO SMP preempt mod_unload modversions '

Hey jihem, thanks for the work on this package!

For anyone who might get the following error... On a clean, minimal install of Arch, after installing this AUR package, modprobe -a vmmon came back with: WARNING: Module vmmon not found in directory /lib/modules/4.14.13-1-ARCH

pacman -S linux-headers solved this for me. It runs dkms install vmware-workstation/14.1.1_7528167 -k 4.14.13-1-ARCH and you should be able to run modprobe -a vmmon, afterward.

Hi all,

I finally changed my mind concerning VMware 12. It seems that a lot of people cannot upgrade to VMware 14 (because of the license or an incompatible processor) and VMware continue to provide security updates. Also, vmware-patch package is clearly not as convenient to use as this package.

That's why I created the package vmware-workstation12 and I will try to maintain it for the next kernel versions. It should not be a big work for me, but I will be able to make only very limited tests (my single machine already run VMware 14).

jihem i'll add this as well in case anyone had installed 12.5.x manually and upgraded to 14.x via AUR as I did and ran the uninstall and deleted all the previous files. Apparently I ended up with 2x /etc/vmware/config files and I had the "[AppLoader] Unable to lookup library directory" error as well but removing the older /etc/vmware/config file (by renaming, just in case) and copying the other config.pacnew file to just config did the trick. Thank you for making this work.

Thank you so much for updating to the latest version 12.5.8!!!

I tried using version 14 with the ' monitor.allowLegacyCPU = "true" ' command in the /etc/vmware/config file but to no avail.

Greetings Michael