Package Details: vmware-workstation 15.0.4-1

Git Clone URL: (read-only)
Package Base: vmware-workstation
Description: The industry standard for running multiple operating systems as virtual machines on a single Linux PC.
Upstream URL:
Keywords: dkms ovftool player vmplayer vmware workstation
Licenses: custom
Conflicts: vmware-modules-dkms, vmware-ovftool, vmware-patch, vmware-systemd-services
Provides: vmware-ovftool
Submitter: Synthead
Maintainer: jihem
Last Packager: jihem
Votes: 85
Popularity: 4.188540
First Submitted: 2017-02-10 19:04
Last Updated: 2019-03-30 15:19

Required by (2)

Sources (25)

Pinned Comments

jihem commented on 2019-03-10 18:37

When you update to version 15.0.2-4, 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).

jihem commented on 2017-10-22 09:29

After the first installation, please:

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

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

For people who would stay on VMware 14, you can switch to vmware-workstation14 package.

Latest Comments

1 2 3 4 5 6 ... Next › Last »

wrexthor commented on 2019-04-13 16:46

EDIT In case someone else have the same problem, disable firejail with sudo firecfg --clean Install and then re-enable firejail, solved it for me.

I get an error when trying to install. Been looking for an answer all over but not managed to find any solution yet, any ideas?

==> Patching vmmon module for DKMS ERROR: object '' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. /usr/bin/patch: **** Can't change to directory /var/tmp/pamac-build-boss/vmware-workstation/pkg/vmware-workstation/usr/src/vmware-workstation-15.0.4_12990004/vmmon-only : No such file or directory ==> ERROR: A failure occurred in package(). Aborting...

GiRa commented on 2019-03-28 10:29

jihem: thanks for the reply. I understand your situation.

I can patch the .SRCINFO and PKGBUILD files at the update. No big deal. Thanks again for explaining.

buzo commented on 2019-03-27 17:00

jihem: I have just installed/updated vmware-keymaps and vmware-workstation with a single pacman command – without any special command line options. You will only get problems if you are trying to do that using two steps.

zangoku commented on 2019-03-18 01:15

@jhem thank you that worked!

jihem commented on 2019-03-17 08:24

zangoku: try to add a backslash before the character *

zangoku commented on 2019-03-17 07:25

@jhem, I must use the slash or else I get:

zsh: no matches found: usr/lib/vmware/xkeymap/*

jihem commented on 2019-03-16 10:00

zangoku: just remove the first slash on the keymap filenames.

GiRa: Since I am the maintainer of this package, I had some complaints of people who use vmware-workstation and vmware-horizon-client packages because these packages have common files and on each update, they need to use --force/--overwrite option to install the updated package. With the vmware-horizon-client maintainer and vmware-keymaps author, we had a discussion by mail and the better solution we found is to put the common files in a new package.

I understand your point of view but I don't want to come back to this decision. But, just to reassure you, these keymap files haven't been changed since at least VMware Workstation 11, so this package should be updated rarely or never. Also, you could suggest to vmware-keymaps maintainer to change the PKGBUILD to extract keymap files from an official VMware bundle, instead of taking them from a private repository.

GiRa commented on 2019-03-15 14:05

I may say that adding an external repository for they keymaps makes updating more complex.

I always review what changed at each new release of an AUR package. Basically it's a full code review at the first installation and then incremental ones which usually take less than a minute.

Having an external, non-official, third-party repo makes the updates more complex. A conscious user is forced to clone the external repo manually and review it at every update.

Was it a big amount of work to maintain the keymaps? You already do a lot, so I am not pretending to change your ways. I simply want to understand :)

EDIT: I see in the gitlog that this is needed for compatibility with vmware-horizon. Is there any other feasible alternative?

zangoku commented on 2019-03-14 21:47


I am getting these errors when trying to install keymaps:

error: could not open file /usr/lib/vmware/xkeymap/be104: Unrecognized archive format error: '/usr/lib/vmware/xkeymap/be104': cannot open package file

jihem commented on 2019-03-13 10:50

zangoku: build the package vmware-keymaps as usual, but without the -i option of makepkg. Then, install it with the following line:

pacman -U --asdeps --overwrite usr/lib/vmware/xkeymap/* vmware-keymaps-1.0-1-any.pkg.tar.xz

Then, update vmware-workstation.