Package Details: vmware-workstation 16.1.0-1

Git Clone URL: (read-only, click to copy)
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: 143
Popularity: 6.06
First Submitted: 2017-02-10 19:04
Last Updated: 2020-11-21 10:25

Pinned Comments

jihem commented on 2020-02-10 17:29

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

Latest Comments

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

jihem commented on 2021-02-26 21:55

Laserentchen: I guess you talk about /etc/vmware/config because the program version doesn't match. It is not a problem, I generally update this file only for major upgrades because some settings can differ, but it doesn't matter if the version number is not exactly the same. I also avoid to update this file because it will bother people by creating .pacnew files.

Laserentchen commented on 2021-02-26 09:42

The config file seems to be outdated (vmware-workstation15 as well).

jihem commented on 2021-02-25 18:05

ArchieMeng: /etc/vmware/networking is not included in the package but created by vmware-networks-configuration.service when starting vmware-networks.service for the first time:

# LANG=C pacman -Qo /etc/vmware/networking
error: No package owns /etc/vmware/networking

If your configuration is broken you can safely remove this file and restart vmware-networks.service

ArchieMeng commented on 2021-02-25 09:06

The /etc/vmware/networking configuration is broken and not needed to be included in the package since it can be generated by vmware-networking from vmware-netowrks.service . Using package included networking configuration will make vmnet failed to create virtual network interfaces.

neuromante commented on 2021-02-25 07:24

@jihem Sorry my fault. I booted back to 5.11.1 and ran dkms. Modules compiled fine and it’s working as intended. Thank you

jihem commented on 2021-02-24 20:54

neuromante: I have no problem to compile vmmon and vmnet modules with kernel 5.11.1 (the default Arch Linux kernel). Are you sure you didn't make a mistake (a partial upgrade or something like that)? If you want some help, can you provide the pacman log with the error?

neuromante commented on 2021-02-24 10:53

Problems with kernel 5.11.1: vmmon module won't compile (and maybe some other modules)

injured commented on 2020-11-23 16:34

In version 16.1.0-1 my problem was solved with the USB controller.

sizzen commented on 2020-11-21 19:59

Has anyone had luck with using vmware workstation with KDE plasma with wayland instead of X? You cannot run gui applications as root under wayland which I understand the security behind but then how do I run it if it requires root ? Any help would be appreciated.

injured commented on 2020-11-21 10:01

When I create a new virtual machine under macOS, I have USB Controller set to USB Compatibility: 3.1. By launching the installation, the USB 3.1 option disappears and only 1.1 and 2.0 remain. I get the message: "Using USB devices with a USB 3.1 controller may require additional drivers to be installed in the guest." I know running macOS on vmware requires USB 3.1. Anyone have an idea why USB 3.1 is disappearing from my list?