Package Details: vmware-workstation12 12.5.9-18

Git Clone URL: (read-only, click to copy)
Package Base: vmware-workstation12
Description: The industry standard for running multiple operating systems as virtual machines on a single Linux PC.
Upstream URL:
Keywords: 12 dkms ovftool player vmplayer vmware workstation
Licenses: custom
Conflicts: vmware-modules-dkms, vmware-ovftool, vmware-patch, vmware-systemd-services, vmware-workstation
Provides: vmware-ovftool, vmware-workstation=12.5.9
Submitter: jihem
Maintainer: jihem
Last Packager: jihem
Votes: 9
Popularity: 0.000057
First Submitted: 2018-01-11 17:35
Last Updated: 2021-08-31 20:50

Required by (3)

Sources (24)

Pinned Comments

jihem commented on 2018-01-11 17:39

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:

  • vmware-networks.service: to have network access inside VMs

  • vmware-usbarbitrator.service: to connect USB devices inside VMs

  • vmware-hostd.service: to share VMs on the network

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

elppans commented on 2018-05-23 00:42

Version 14 does not work on my machine, it asks for support from something I do not remember now and my machine does not have it.

I realize, he's a lot heavier, at least for me.

Ps.: Sorry, I use a translator because I do not speak English

jihem commented on 2018-05-22 14:52

schlegel11: There is a big change in VMware 14 UI: the transition to gtk3. I think it needed a lot of changes in the code, so a lot of new bugs.

Moreover, they use a very old version of gtk3 (it seems to me this is gtk 3.14, while Arch uses gtk 3.22). This can explain some of the bugs (at least, it explains a bug with iBus and why VMware 14 doesn't use the theme defined by the user).

schlegel11 commented on 2018-05-20 14:19

I also want to say Thank You for this package. This version of vmware player is always running really well with new kernel versions (currently 4.16.9-1-ARCH).

Can someone perhaps explain to me why thats the case compared with the latest vmware player 14? In general the virtual machines are also running with version 14 and a new kernel but the vmware player 14 UI is always really clunky and crashes a lot.

Did vmware change the whole UI implementation of the player 14 or is it related to other dependencies and versions of it?

xanadu73 commented on 2018-04-25 10:35

Thanx for this useful app. Works well on kernel lts 414.

jihem commented on 2018-04-17 04:52

elppans: yes, and I've just tested again with 4.15.15 and 4.16.2: I have no error.

elppans commented on 2018-04-16 05:50

elfroggio, modprobe with the "force-vermagic" option, have you tried adding it to the /etc/rc.local file to see if it works and no longer needs to start the service at each startup?

jihem, Have you already tested the installation with Kernel 4.15 or later?

xanadu73 commented on 2018-03-08 18:25

I can confirm that following the instructions above, it works well with kernel 4.14. Drag & Drop features between the host and the guest can sometimes break, but this is not a big deal. Thanx for the great effort.

jihem commented on 2018-02-03 20:44

Thanks for the tip, I didn't know the force-vermagic parameter!

Just a thought, if you didn't already do that, maybe recompiling your kernel with the exact same version of GCC used to compile DKMS modules could help you.

elfroggio commented on 2018-02-03 18:44

  1. Thanks
  2. I was using 4.4 because I had problem with vmware with more recent kernels.
  3. I had a previous manual installation but everything was cleanup (actually scrubbed clean), nothing left related to vmware.

I have solved my problem with the following command:

modprobe --force-vermagic -a vmw_vmci vmmon

The force-vermagic allows the loading of vmmon. I guess it has to do with recent kernel updates for the Scepter...

It's not perfect since I have to do it on each boot. vmmon still fails to load on boot and reports a failure. But I'm OK with it, I've already spent a week fighting the retpoline.



jihem commented on 2018-02-03 08:38

I have just tested on Linux 4.4.114 (compiled from linux-lts44 AUR package). I have no error when loading modules and I can start a VM without problem.

If you installed VMware manually from bundle before using this package, check if there is remaining modules files and delete them (from /usr/lib/modules/4.4.113-1-lts44/misc, delete vmmon.ko, vmnet.ko, vmci.ko, vmblock.ko and vsock.ko when they exist). Then, reboot and test to load vmmon again.

If it still doesn't work, you can try to update to Linux 4.4.114 or a newer version (4.9 or 4.14) if you can (I don't know why you stay on an old kernel version).