Package Details: vmware-workstation 12.5.7_5813279-2

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 hostd installer networks ovftool patch player server service systemd usbarbitrator vix vmplayer vmrun vmware vmx 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: 21
Popularity: 5.924927
First Submitted: 2017-02-10 19:04
Last Updated: 2017-07-13 18:36

Required by (0)

Sources (24)

Latest Comments

Plexcon commented on 2017-07-13 09:12

Después de instalado, no se actualizan los complementos

jihem commented on 2017-07-11 15:03

Hi Steven,
Unfortunately, vmware-installer is not available with this package for two reasons:
- it is really complicated to implement in the PKGBUILD and need a lot of tests (I tried to implement it but I abandoned)
- it will add/remove/change package files which is not a good idea (in the future, you might have pacman errors or remaining files after uninstallation)
Besides, you should not have this error: the package contains all vmware tools in their last version. Do you have the directory /etc/vmware-installer/components? If yes, remove it.
A workaround for your problem is to manually install guest tools: insert the ISO file (in /usr/lib/vmware/isoimages/, select windows.iso, winPre2k.iso or winPreVista.iso depending your Windows version) in the virtual CD/DVD player.

StevenTheEVIL commented on 2017-07-10 23:11

How do I use vmware-installer in this package? I need to use the workaround for vmware-tools for a windows guest that's described on the wiki page for VMWare.

jihem commented on 2017-07-03 19:02

@justmeagain: Probably stupid question, but did you think to start vmware-networks service? If yes, do you have some errors? (systemctl status -l vmware-networks.service)
You can start vmware-netcfg program to manage network interfaces (and, for example, remove and recreate vmnet1, maybe it will fix your problem).
You can also reset all interfaces with the command "rm -r /etc/vmware/{networking,vmnet*} && systemctl restart vmware-networks-configuration.service"

justmeagain commented on 2017-07-03 07:49

"Could not connect 'Ethernet0' to virtual network 'dev/vmnet1'".

This is the warning message I get when launching a virtual machine.
Everything else works flawless, but I cannot connect guests to any network because vmnet adapters does not exists.

Seems that installation process did not created the virtual network interfaces needed by vmware

frail commented on 2017-06-26 20:45

@jihem: oh man. I just put my dunce cap on. You're absolutely right. I forgot to load gksu on this clean install. :(

jihem commented on 2017-06-24 11:24

@frail: I cannot reproduce your bug. Actually, I think this bug is not related to this package.
To verify that, install gksu package and start a graphical program with gksu (for example: "gksu nautilus"). If you have the same error, so your bug is not related to this package and is probably a bad configuration of your system. Search a solution on Google.
If gksu works, the problem probably comes from this package, but I have no idea how to solve it. Try to uninstall the package, remove /etc/vmware and /etc/vmware-installer directories if they still exist and reinstall the package.

frail commented on 2017-06-23 18:52

I'm not sure if it's intentional although I'm unable to enter in my license key. Clicking the button opens a prompt:
"Failed to run '/usr/lib/vmware/bin/vmware-enter-serial' -n 'VMware Workstation' -v '12.0' as user root.

Unable to copy the user's Xauthorization file."

Anyone run up against this?

jmboris commented on 2017-06-19 20:49

@jihem Thank you very much !!! I installed the package manually following the first link, thank you !

jihem commented on 2017-06-19 08:56

@jmboris: This is because yaourt creates packages in RAM (/tmp directory is by default in RAM for performance reasons) and the creation of this package needs a lot of memory. Several solutions:
- manually install this package outside /tmp (without yaourt, see
- change the directory used by yaourt to create packages (variable TMPDIR in /etc/yaourtrc)
- prevent /tmp to be used in RAM (

jmboris commented on 2017-06-18 16:30


I have the following error , Can someone help me ?

==> Iniciando package()…
install: error al escribir en '/tmp/yaourt-tmp-juan/aur-vmware-workstation/pkg/vmware-workstation/usr/lib/vmware/isoimages/windows.iso': No queda espacio en el dispositivo
==> ERROR: Se produjo un fallo en package().
==> ERROR: Makepkg no ha podido compilar vmware-workstation.

zelluz commented on 2017-06-07 11:16

@jihem Of course I did not try to reinstall the software, doh!
After a reinstall(I did a complete uninstall of Workstation first), everything is working again.

Thank you!

(I am running the 4.11.3-1 kernel)

Sarithis commented on 2017-06-07 06:52

@jihem yeah, I was having problems with compiling vmware modules from the official vmware workstation bundle. I thought, that this problem also affects this version of the vmware package. I'm glad that it doesn't.

jihem commented on 2017-06-07 06:10

@zelluz: Which kernel do you use? If you reinstall the package, do you have some errors on DKMS compilation?

zelluz commented on 2017-06-06 07:21

Having issues compiling modules after upgradering to the latest version.

"Unable to start services.

See log file /tmp/vmware-root/vmware-11569.log for details"

Output in terminal:

Starting VMware services:
Virtual machine monitor failed
Virtual machine communication interface done
VM communication interface socket family done
Blocking file system done
Virtual ethernet failed
VMware Authentication Daemon done

In log file /tmp/vmware-root/vmware-11569.log the error is: "Hunk #12 FAILED at 1167.
1 out of 57 hunks FAILED -- saving rejects to file vmmon/linux/hostif.c.rej"

Thank you in advance.

jihem commented on 2017-06-05 18:49

@Sarithis: these patches are not useful anymore, the last version of VMware already contains corrections for Linux 4.11. Do you have some errors on compilation?

@zaephyr: thanks for the information!

Sarithis commented on 2017-06-05 17:13

These patches need to be applied before rebuilding vmware modules if you're using the newest kernel (4.11.3-1-ARCH):

zaephyr commented on 2017-06-02 19:03

@dann1 @jihem: As a note, open-vm-tools is what VMware recommends everyone use. They officially support it ( and are the maintainers of the official repo (

jihem commented on 2017-05-27 20:18

@dann1: do you talk about the "official" VMware tools, opposed to the open-vm-tools? I will thinking about that, but probably not. open-vm-tools works great, and it seems to me that now VMware tools does not provide more functionalities.

dann1 commented on 2017-05-27 19:03

Thanks a lot for this package. Is there the possiblity of you packaging vmware-tools? It would be really nice.

jihem commented on 2017-05-27 05:52

/usr/lib/systemd/system is the right place to put service files in a package and yes, you need to manually activate the services you want (using systemctl start/systemctl enable).
And thanks for your second comment! I also hope I will be able to maintain this package for a long time. :)

hogar1977 commented on 2017-05-26 21:33

NVM, figured it out on my own. Thanks for the helpful comment. This is by far the most useful package on my machine :-) Pls don't ever stop maintaining it :-)))

hogar1977 commented on 2017-05-26 21:24

It did!

My vmplayer starts now, but I also noticed that the services you mention (the .service files) are only in usr/lib/systemd directory... should I start them from there or there is some procedure to be done to move them or add them to the /etc/systemd? and make them start automatically on every restart...

jihem commented on 2017-05-26 19:29

Hi hogar1977,
Your error is in the /etc/vmware/config file. You probably have a file /etc/vmware/config.pacnew which appeared after the installation of this package (more information about that kind of files here:
You should merge the /etc/vmware/config and config.pacnew files (using pacdiff) to import the line "libdir = ..." in the config file. Or, more simple, erase the /etc/vmware/config file with the config.pacnew (but you could lose some specific preferences about memory management in VMware, if you changed them).
If, for any reason, you don't have the config.pacnew file, just add the following file at the end of /etc/vmware/config:
libdir = "/usr/lib/vmware"
About services, they were rewritten to not need the scripts in /etc/init.d contrary to vmware-patch and vmware-systemd-services, and theses packages are automatically removed to avoid conflicts with incompatibles services. This package doesn't require to start any service to use vmplayer, but it is highly recommended to start vmware-networks and vmware-usbarbitrator services to have all features available. vmware-hostd is specific to the Workstation version and allow to use VMs at distance. vmware.service doesn't exist here.
Hope this post will help you!

hogar1977 commented on 2017-05-26 16:37


I was using vmplayer 12.5.5 installed via bundle before. After I upgraded the kernel to the latest iteration I was not able to compile modules due to some gcc version issues.

I uninstalled the vmplayer bundle and installed your package, but now neither vmplayer nor workstation are starting up.

2017-05-26T10:57:46.325-05:00| appLoader| I125: Log for appLoader pid=2913 version=12.5.6 build=build-5528349 option=Release
2017-05-26T10:57:46.325-05:00| appLoader| I125: The process is 64-bit.
2017-05-26T10:57:46.325-05:00| appLoader| I125: Host codepage=UTF-8 encoding=UTF-8
2017-05-26T10:57:46.325-05:00| appLoader| I125: Host is unknown
2017-05-26T10:57:46.327-05:00| appLoader| W115: HostinfoReadDistroFile: Cannot work with empty file.
2017-05-26T10:57:46.327-05:00| appLoader| W115: HostinfoOSData: Error: no distro file found
2017-05-26T10:57:46.328-05:00| appLoader| I125: Invocation: "/usr/lib/vmware/bin/vmware-modconfig --launcher=/usr/bin/vmware-modconfig --appname=VMware Playe
r --icon=vmware-player"
2017-05-26T10:57:46.328-05:00| appLoader| I125: Calling: "/usr/lib/vmware/bin/vmware-modconfig --launcher=/usr/bin/vmware-modconfig --appname=VMware Player -
2017-05-26T10:57:46.328-05:00| appLoader| I125: VMDEVEL not set.
2017-05-26T10:57:46.328-05:00| appLoader| I125: VMWARE_SHIPPED_LIBS_LIST is not set.
2017-05-26T10:57:46.328-05:00| appLoader| I125: VMWARE_SYSTEM_LIBS_LIST is not set.
2017-05-26T10:57:46.328-05:00| appLoader| I125: VMWARE_USE_SHIPPED_LIBS is not set.
2017-05-26T10:57:46.328-05:00| appLoader| I125: VMWARE_USE_SYSTEM_LIBS is not set.
2017-05-26T10:57:46.328-05:00| appLoader| I125: Using configuration file /etc/vmware/config.
2017-05-26T10:57:46.328-05:00| appLoader| I125: libdir entry was not present in /etc/vmware/config.
2017-05-26T10:57:46.328-05:00| appLoader| W115: Unable to lookup library directory.

This is my log when I try to start vmplayer. I tried to use the export command to declare VMWARE_USE_SHIPPED_LIBS='yes' but no change.

I added the vmware.service and vmware-usbarbitrator.service files but I notice that the /etc/init.d/vmware file does not exist at all so the service cannot be started at all.

What happened here? Any ideas? Shouldn't this service get installed by your package? vmware-patch and vmware-systemd-services are automatically removed if your package is installed, but as far as I know without starting the vmware service the vmplayer cannot really run, no?

Synthead commented on 2017-05-25 22:19

Ah yay, thanks! I'm really glad you like it! I'm pleased to see it being kept up!

yetAnotherZero commented on 2017-05-25 21:25

Best. Package. Ever.

Love the dkms hook that rebuilds when upgrading the kernel

jihem commented on 2017-05-25 14:37

@budkin: the package provides two softwares: VMware Workstation, which cost money and VMware Player, which contains less features but is free for non-commercial use.

budkin commented on 2017-05-25 14:07

does this thing cost money?

jihem commented on 2017-05-25 14:01

Hi tidereis13, strange bug. Did you install VMware manually before using this package? Maybe it's a partial uninstallation of VMware configuration files which conflicts with this package.
You can try to remove /etc/vmware/vmnet* directories and launch the command "systemctl restart vmware-networks-configuration.service". This should reset network configuration and recreate missing files.

tidereis13 commented on 2017-05-25 00:20

I'm having problems with the network configuration. It keeping crashing asking for the file or folder /etc/vmware/networking and I can't start the Network editor.

Any of the vmnets interfaces came up too. trying to figure out what can be, so far no success

gbr commented on 2017-05-22 12:27

Working just fine for me on linux-lts-4.9.29. Thank you very much.

jihem commented on 2017-05-21 12:04

@fitu996: Are you using the last version of the package? There was a bug on the previous version but it should be fixed now. I've just tested again and I don't have any problem to use a trial license.

fitu996 commented on 2017-05-21 02:47

I start vmware after install, choose 30days trial. Then it says lisense key is invalid.
I used to folow ArchWiki installation guide, vmware workstation works fine.
What should I do?

jihem commented on 2017-05-10 10:44


Firstly, thanks Synthead for your great work!
I updated the package to 12.5.5 and solved some minor bugs.
Now, the package also contains VMware Player and a patch for people who want to use macOS guests (this patch is disabled by default, if you want it you have to edit a line in the PKGBUILD).


F1nny commented on 2017-05-08 23:39

Ahh bummer, thanks for orphan'ing hopefully someone snags, I understand the patch method and sure, it's just easier to have those upgrades happen automatically via aur without having to go log into vmware, download, install, then update the patch, etc etc. Not sure why more don't use this route:) The popularity is far higher than the patch it seems

quenyen commented on 2017-05-08 19:06

I have disowned it because I really haven't had time to get to it. I also lost interest because I have never used the repository....instead of using as peolo99 said...vmware-patch after running the standard vmware install (never had a problem going that way myself). It makes me wonder whether this package is even needed...and is possibly a distraction for those trying to use vmware. In any case...I have never needed this my interest level is lower than I'd hoped.

F1nny commented on 2017-05-02 21:34

quenyen - are you no longer maintaining this package? Multiple patches have released in the past couple months that have some important fixes :[ If not going to maintain can orphan so someone else hopefully picks it up.

Hey guys PS - so DKMS doesn't work so everytime update kernel have to re-install from the AUR, saw it mentions needing LTS headers to use DKMS, is that right? I mean it does dkmsinstall correctly on my current kernel just updates it fails?

F1nny commented on 2017-04-16 20:32

Hey guys, any idea why it crashes immediately on start? First time install

vmware-modconfi[26289]: segfault at 3680 ip 0000000000003680 sp 00007ffd7c2a8fd8 error 14 in appLoader[55cb95e38000+ad000]

/edit looks to be libpng breaks it, likely fixed in newer VMware pkg, I saw maintainer left as didn't have anymore and someone else took over - quenyen any plans to update the package? 12.5.2 pretty old at this point, or is there a reason? Anyone know if updating pkgbuild just for the new install package works or are some of those patches unnecessary?

pelo99 commented on 2017-04-13 06:30

Alternate solution to this.
Just download the latest Installation package from and install it. Install "vmware-patch" from AUR. Enable "vmware.service" to autoload kernel modules. For every kernel version change, boot into the new kernel and run "vmware-patch" to compile and reload kernel modules for the new kernel. Check and install any App updates from the preferences section.

3KyNoX commented on 2017-04-09 17:10

Hey, we can use mine from my school to maintain the repo. As you wish.

Synthead commented on 2017-03-31 19:56

Hey guys, I'm in a position where I won't have a VMware license anymore, so I won't be able to fully maintain this package. I'm marking it as an orphan, so please feel free to snag it! Thanks so much for all the great feedback, and I'm really glad to see this package being used!

spaceback commented on 2017-03-31 17:34

12.5.5 is out now :)

Awesome_Donkey commented on 2017-03-14 12:48

12.5.4 is out too.

Also keep in mind the issue with both 12.5.3 and 12.5.4.

Described in the comments here:

And posted here:

Synthead commented on 2017-03-13 21:49

@kisacamel, thanks for the feedback! I tried the PKGBUILD with the new version and vmmon.patch doesn't apply (hunk #12 fails at line 1167). I'll get this updated, but I can't spend time on it today, unfortunately. I have marked this package out-of-date for now.

If anyone's able to get vmmon.patch to apply, let me know what you did and I'll toss the changes in the package. Also, give me a contributor name and email and I'll give you a shout out in the PKGBUILD, too ;)

Synthead commented on 2017-03-13 20:39

Whoops, looks like I accidentally excluded '/var/lib/vmware/Shared VMs' from the PKGBUILD on release 12 with commit 05fa339c37ade19c11339b0f35207153512dc012! Shared VMs weren't affected, though, as pacman doesn't remove any files it doesn't own. This is an empty directory, however, so if nothing was in it, it would've been removed in release 12, which would cause the problems mentioned with the vmware-hostd service.

Just pushed release 14 to revert this issue and make everything happy again. Thanks for the feedback, @monotykamary!

kisacamel commented on 2017-03-13 19:17


Thanks for fancy package!

maybe vmware-workstation update as well while fixing it ? :)

Synthead commented on 2017-03-13 18:48

@monotykamary, thanks for the feedback! I just updated vmblock.ko to use vfs_readlink and it works like a charm.

I'm looking into the vmware-hostd service issue right now as well.

monotykamary commented on 2017-03-13 00:39

Current package DKMS modules do not build correctly due to make error on vmblock.ko for linux>=4.10.

However in testing swordfeng's comment in vmware-modules-dkms, changing `generic_readlink` to `vfs_readlink` in vmblock.patch lets DKMS install the modules as intended.

Service vmware-networks works without a problem. Service vmware-hostd modprobes vmmon and vmci correctly, but exits on status=255 with a backtrace log in systemctl.

Synthead commented on 2017-02-25 02:05

Hi x-drum! Thanks for the feedback!

I have added ovftool in release 12. Enjoy!

x-drum commented on 2017-02-24 15:33


currently is not possible to import VMs or template via OVA/OVF due to the missing component "vmware-ovftool", the process fails with:
spawn_async failed: Failed to execute child process "/usr/lib/vmware/../vmware-ovftool/ovftool" (No such file or directory)

I was able to fix the PKGBUILD and include "vmware-ovftool", please consider the following patch:
--- PKGBUILD.orig 2017-02-24 15:39:34.520016182 +0100
+++ PKGBUILD 2017-02-24 15:54:08.040027530 +0100
@@ -82,6 +82,7 @@
"$pkgdir/run/vmware" \
"$pkgdir/var/lib/vmware/Shared VMs" \
"$pkgdir/usr/lib/vmware-vix" \
+ "$pkgdir/usr/lib/vmware-ovftool" \

cd "$srcdir/extracted"
@@ -125,6 +126,10 @@
vmware-vix-core/vixwrapper-config.txt \

+ cp -r \
+ vmware-ovftool/* \
+ "$pkgdir/usr/lib/vmware-ovftool"
for isoimage in \
freebsd \
linux \
@@ -165,6 +170,8 @@
"$pkgdir/usr/bin"/* \
"$pkgdir/usr/lib/vmware/bin"/* \
"$pkgdir/usr/lib/vmware/setup/vmware-config" \
+ "$pkgdir/usr/lib/vmware-ovftool/ovftool" \
+ "$pkgdir/usr/lib/vmware-ovftool/ovftool.bin" \

Synthead commented on 2017-02-16 21:47

Included the "Virtual Network Editor" GUI tool and vmware-netcfg CLI tool.

Also set wmware-networks.service to restart vmware-networks when it is killed. The "Virtual Network Editor" tool kills vmware-networks when settings are saved, so this is a quick and seamless fix that makes the network come back up with the new settings.

Synthead commented on 2017-02-14 17:29

Updated vmware-hostd and vmware-networks services to probe the appropriate kernel modules when they start.

@Pival81, this should take care of the issue you were seeing, and you don't need to run modprobe or configure modules-load.d before starting the services now.

Synthead commented on 2017-02-14 16:40

Renamed vmware-workstation-server service to vmware-hostd. vmware-hostd does not start the vmware-usbarbitrator or vmware-networks services by itself anymore. This lets the user decide what specific VMware daemons to run instead of it being hard-coded as dependent services.

Synthead commented on 2017-02-14 16:18

Added systemd service files for vmware-networks.

Synthead commented on 2017-02-12 19:37

modprobe vmmon ;)

Seems like there should be a modules-load.d or something

Pival81 commented on 2017-02-12 18:45

when I start up my vm I get this error:

Could not open /dev/vmmon: File o directory non esistente.
Please make sure that the kernel module `vmmon' is loaded.

I'm on kernel 4.9.8 vanilla

Synthead commented on 2017-02-10 19:55

Added support for VMware's USB Arbitrator.

Synthead commented on 2017-02-10 19:15

Whew! That was an absolute pain to package. I needed this software for work and found that one didn't exist, so I did my gosh darndest to treat the community right and share my work. Installing blobs as root is bad, so here's a badly-needed package for this suite.

The goal of this effort was to get VMware workstation running with Packer. I likely overlooked other bits and pieces, so if this package doesn't work for you for whatever reason, gimme a shout and I'll work with you to update things.

Included are some hand-crafted, locally-sourced .service files for generating self-signed certs (the way VMware's System V init script does) and starting the VMware Workstation Server. This split-brain approach is the same way our OpenSSH .service file handles generating host keys.

In addition, this package leverages the excellent patches from the vmware-modules-dkms package to give you everything needed to handle compiling VMware's kernel modules via DKMS directly. Holy crap, I would have sunk way more time than I should have if it wasn't for these guys. Major props!