Package Details: vmware-workstation12 12.5.9-23

Git Clone URL: https://aur.archlinux.org/vmware-workstation12.git (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: https://www.vmware.com/products/workstation-for-linux.html
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
Submitter: jihem
Maintainer: jihem
Last Packager: jihem
Votes: 9
Popularity: 0.000000
First Submitted: 2018-01-11 17:35 (UTC)
Last Updated: 2022-06-09 10:38 (UTC)

Required by (3)

Sources (24)

Pinned Comments

jihem commented on 2018-01-11 17:39 (UTC) (edited on 2020-02-10 17:25 (UTC) by jihem)

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

leopseft commented on 2020-09-06 18:16 (UTC)

Hello folks, when I try to open an Ntfs storage that I have my vms in I get the following error:

"Mount is denied because the NTFS volume is already exclusively opened. The volume may be already mounted, or another software may use it which could be identified for example by the help of the 'fuser' command."

I mount the storage with fstab with the following parameters /run/media/leopseft/storage/ ntfs auto,user,rw 0 0

With the newer vm versions i can open the storage normally but vms doesn't run due to system limitations (old core2duo 2010 laptop).

Does anyone have a work around for this issue? Thank you very much.

jihem commented on 2020-08-07 09:37 (UTC) (edited on 2020-09-06 16:51 (UTC) by jihem)

Please do not update to Linux 5.8 because the system will crash each time a VM is powering on. There is no workaround for the moment, and maybe it will never be possible to run this version of VMware on Linux≥5.8. More informations in this thread: https://communities.vmware.com/thread/638457

EDIT: now the package is compatible with Linux 5.8.

ZorinArch commented on 2020-07-07 09:50 (UTC) (edited on 2020-07-07 09:53 (UTC) by ZorinArch)

jihem: Thank you for reply. i install this package on a machine with old kernel and enter key > ask root password like normal and works fine. then i copy /etc/vmware from this machine with old kernel to the new install machine with linux 5.4.50-1-lts kernel and works fine without asking for root or anything and works fine now. error box not appear anymore. i think the problem was in root permissions or so.

jihem commented on 2020-07-06 18:48 (UTC)

ZorinArch: can you provide a screenshot and explain what did you do before this box appear (just starting the program for the first time or doing a specific action after the program is opened)?

ZorinArch commented on 2020-07-05 11:35 (UTC) (edited on 2020-07-05 11:37 (UTC) by ZorinArch)

when install this package in new arch install with linux 5.4.50-1-lts kernel got an error want root cred. without show box that can enter root password. Just an error box ask system administrator help.

elppans commented on 2019-11-23 01:36 (UTC)

Alright, I kind of automated it for myself with a very simple script: https://pastebin.com/raw/tH2mfs5t

jihem commented on 2019-11-21 17:12 (UTC)

@elppans I cannot use this solution, because the header package depends on kernel version: linux-headers for linux, linux-lts-headers for linux-lts, linux-zen-headers for linux-zen... I think using optdepends is the best solution. This is also the solution used by virtualbox-host-dkms package.

elppans commented on 2019-11-20 23:33 (UTC)

You could change the location of linux-headers to "depends" instead of "optdepends". Without linux-headers, vmw_vmci and vmmon modules are not created and so the virtual machine does not work, so it is a required package. By the way, this is the best version of VMWare, version 14 and up is boring bugs

jihem commented on 2019-03-30 15:21 (UTC) (edited on 2019-03-30 15:22 (UTC) by jihem)

When you update to version 12.5.9-8, you should see an error telling that some files already exist. This is normal, the reason is that some files previously included in this package are now provided by another package (vmware-keymaps) which is now a dependency.

One solution is to install vmware-keymaps with the option --overwrite usr/lib/vmware/xkeymap/\* before updating vmware-workstation. Another solution is to uninstall your current version of vmware-workstation, then build and install the new version (with vmware-keymaps dependency).

schlegel11 commented on 2018-05-25 17:19 (UTC)

@jihem Ah ok good to know. I also looked into the changelogs and you are right the gtk3 UI seem to be the problem. Hopefully it will be resolved with player/workstation version 15 or something like that. Anyway Im happy with version 12 ;)

elppans commented on 2018-05-23 00:42 (UTC)

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 (UTC)

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 (UTC) (edited on 2018-05-20 14:20 (UTC) by schlegel11)

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 (UTC)

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

jihem commented on 2018-04-17 04:52 (UTC)

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 (UTC)

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 (UTC) (edited on 2018-03-08 18:26 (UTC) by xanadu73)

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 (UTC)

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 (UTC)

  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.

Thanks

Syv

jihem commented on 2018-02-03 08:38 (UTC)

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).

elfroggio commented on 2018-02-02 22:07 (UTC)

Installed under 4.4.113 and it doesn't work. I get:

modprobe -a vmw_vmci vmmon

modprobe: ERROR: could not insert 'vmmon': Exec format error

I've been googling and not found a solution.

Thanks

Syv

teacher4711 commented on 2018-01-11 19:16 (UTC)

Awesome! Thank you so much for maintaining this package!

jihem commented on 2018-01-11 17:39 (UTC) (edited on 2020-02-10 17:25 (UTC) by jihem)

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