Package Details: vmware-workstation 17.6.3-3

Git Clone URL: https://aur.archlinux.org/vmware-workstation.git (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: https://www.vmware.com/products/workstation-for-linux.html
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: JulianXhokaxhiu
Last Packager: JulianXhokaxhiu
Votes: 212
Popularity: 3.26
First Submitted: 2017-02-10 19:04 (UTC)
Last Updated: 2025-04-03 21:57 (UTC)

Sources (25)

Pinned Comments

jihem commented on 2020-02-10 17:29 (UTC) (edited on 2021-06-19 13:19 (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 (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

Latest Comments

« First ‹ Previous 1 .. 56 57 58 59 60 61 62 63 64 65 66 .. 71 Next › Last »

jihem commented on 2017-12-20 17:12 (UTC)

Don't follow the wiki, it is useless if you use this package. Kernel modules are automatically compiled with DKMS when you install the package, you don't have to do it manually (just verify that you installed linux-headers before).

Just read instructions in the pinned comment, this is all you have to do (and be careful that services names are slightly different than services names in the wiki).

avarx commented on 2017-12-20 16:51 (UTC) (edited on 2017-12-20 16:54 (UTC) by avarx)

Appreciate your feedback, jihem. I don't get it. If I follow the wiki I can't compile the machine monitor. If I use this repo I get: [AppLoader] Unable to lookup library directory.

What am I doing wrong?

jihem commented on 2017-12-19 20:39 (UTC)

@avarx: Yes. I maintain this package for linux, linux-zen and linux-lts kernels.

avarx commented on 2017-12-19 06:18 (UTC) (edited on 2017-12-19 06:29 (UTC) by avarx)

Hi guys. Anyone successfully running VMware Workstation 14.0.0. on 4.14.6-1?

Win8Error commented on 2017-12-17 10:58 (UTC)

Works perfectly :D Thank you very mutch!

xanadu73 commented on 2017-12-15 10:55 (UTC)

I can confirm the following: On ArchMerge kernel version 4.9.68-1-lts and workstation version 12.5.8 build-7098237 the patch works flawlessly. It asks mentions kernel 13x-14x during installation but it is no problem.

By the way, I'm not using Workstation version 14 because when running with a Windows Guest for some reason, the program automatically exits FulScreen Mode without any intervention or fault by the user (including Exclusive Mode). I haven't been able to identify the cause.

jnbrains commented on 2017-12-08 09:10 (UTC)

Thanks jihem.

jihem commented on 2017-12-05 13:35 (UTC)

@jnbrains: I know, the patch is already included in the package.

jnbrains commented on 2017-12-05 08:48 (UTC)

Linux Host: Kernel 4.14-rc1 Breaks vmmon... https://communities.vmware.com/thread/572148

jihem commented on 2017-12-04 23:40 (UTC)

@gbr: After reading your previous comment, I assume it always works on kernel 4.9. It's very strange, it seems you are the only one who have this problem. Try to investigate: does it work better if you disable graphics acceleration in your VMs? If you allow/disallow swap or increase reserved memory in VMware settings? If you disable systemd services related to VMware? If you start a new VM using a minimum of resources (without sound card, USB controller...)? If you have an Intel processor, have you installed intel-ucode package? Also, search some informations in the logs (located in /tmp/vmware-$USER/vmware*.log, read the logs with the number corresponding to the PID of VMware currently running). You can also try to reset all settings: uninstall the package, remove folders /etc/vmware and ~/.vmware and reinstall the package. And of course, verify if there is no regression with your hardware in recent kernel versions.