Package Details: vmware-workstation 14.0.0-2

Git Clone URL: https://aur.archlinux.org/vmware-workstation.git (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: https://www.vmware.com/products/workstation-for-linux.html
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: 30
Popularity: 3.270474
First Submitted: 2017-02-10 19:04
Last Updated: 2017-10-01 20:17

Required by (0)

Sources (25)

Pinned Comments

jihem commented on 2017-10-22 09:29

After the first installation, don't forget to:
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 in 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 12.5.7, use the following commands. This old version should be compatible with the next Linux LTS (4.14).
% git clone https://aur.archlinux.org/vmware-workstation.git
% cd vmware-workstation
% git checkout 2965e8782be11ce0049f32fafa96b2d60c0282c8
% makepkg -si

Latest Comments

jihem commented on 2017-10-22 09:38

@mirh: actually, instructions about the services you can enable are written on the terminal during the first installation of the package. But I've just added a pinned comment for people who didn't see this information.

jihem commented on 2017-10-22 09:29

After the first installation, don't forget to:
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 in 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 12.5.7, use the following commands. This old version should be compatible with the next Linux LTS (4.14).
% git clone https://aur.archlinux.org/vmware-workstation.git
% cd vmware-workstation
% git checkout 2965e8782be11ce0049f32fafa96b2d60c0282c8
% makepkg -si

mirh commented on 2017-10-20 17:40

> and yes, you need to manually activate the services you want

This should be a bit more prominent in the comments.

liberodark commented on 2017-10-07 08:23

For me not install Vmware 14

JiPRA commented on 2017-10-06 01:19

Sorry, my bad! You already had included all the fixes in your vmmon.patch file, so it's all good! :)

JiPRA commented on 2017-10-06 00:49

@jihem: Can you please include the latest commit from GitHub to the vmmon module? It fixes a serious memory allocation problem with kernel 4.13. The problem appears at least with Windoze VMs but it might affect Linux VMs too. Without the fix, the VM would randomly freeze and give the following error message, "The virtual machine is unable to reserve memory". If both keyboard and mouse are confined to the VM window when the freezing occurs, there's no way to release them and the only way out is to reset the host computer. That's a cruel farewell to all unsaved work and data. Here's a link to the fix:
https://github.com/mkubecek/vmware-host-modules/blob/b50848c985f1a6c0a341187346d77f0119d0a835/vmmon-only/linux/hostif.c

ksqsf commented on 2017-10-02 05:13

@jihem: Thanks! It's fixed for me. This is indeed hard to package and thanks again for the maintenance. :-)

jihem commented on 2017-10-01 20:37

The bug should be fixed now. I think it's a conflict with Archlinux libraries and VMware internal libraries (they use a different version of GTK3) which appear when iBus is installed. VMware try to read the file /usr/lib/gtk-3.0/3.0.0/immodules.cache but it failed for some reason. I just use a tweak to prevent it to read this file.
Tell me if the problem is not fixed for you.

Ishbir commented on 2017-10-01 15:47

I am running xfce with iBus installed. "VMWARE_USE_SHIPPED_LIBS=yes vmware" works for me as well.

$ pactree -r ibus
ibus
└─ibus-mozc

Output from the apploader log files (4 of them are created):
- https://pastebin.com/w600ZhLj
- https://pastebin.com/Hz8Xnv9J
- https://pastebin.com/xhbpyhZq
- https://pastebin.com/NhatsPg3

And yes, can confirm that UI appears but quickly disappears because of the undefined symbol.

jihem commented on 2017-10-01 15:33

Thanks! I have not still found a solution, but now I can reproduce the bug. It appears when using some keyboard layouts like chinese or japanese.
Until I find a proper solution, you can use the environment variable VMWARE_USE_SHIPPED_LIBS=yes or remove the file /usr/lib/gtk-3.0/3.0.0/immodules.cache (it is generated by a pacman hook, you will be able to create it again by reinstalling gtk3 package).

ksqsf commented on 2017-10-01 10:32

@jihem: It seems to create three apploader log files. They look the same despite the timestamp. I've uploaded one with the least PID: https://slexy.org/view/s2ZxY7F4fT . (more undefined symbols than I expected!)

$ pactree -r ibus
ibus
├─ibus-anthy
└─ibus-rime

PS: Something interesting: sometimes the UI appears but quickly disappears because of the undefined symbol. However, the VM is still running in the background, and sometimes the UI is still accessible (through the tray icon). I have no idea why.

jihem commented on 2017-10-01 09:22

@ksqsf: thanks for the precision. And you are two, so it's not an isolated bug. Strange that I don't have this bug whereas I'm testing in the same conditions.
Can you give me the content of the file /tmp/vmware-$USER/vmware-apploader-xxxx.log (where xxxx is a PID number) after starting vmware with the error? (If you have several files like that, just remove /tmp/vmware-$USER directory before restarting VMware.)

Edit: can you also give me the output of "pactree -r ibus"? I'm interested to know which package depends on it.

ksqsf commented on 2017-10-01 08:58

@jihem: I can reproduce this problem on GNOME 3.24 with iBus installed. The problem occurs on both Xorg and Wayland sessions.

"VMWARE_USE_SHIPPED_LIBS=yes vmware" works.

jihem commented on 2017-10-01 08:43

@lshbir: I am not able to reproduce your bug, I need more informations. Can you tell me which desktop environment do you use (Gnome, KDE, xfce...)? Does it work on Xorg or Wayland? Do you have the package ibus installed?
Can you also tell me if these workarounds work:
- start your session on Xorg instead of Wayland or the contrary (if your DE is compatible Wayland)
- start VMware with the command "VMWARE_USE_SHIPPED_LIBS=yes vmware"

Ishbir commented on 2017-10-01 05:18

I just upgraded to the latest version and when I run vmware from the terminal, this is what I get:

/usr/lib/vmware/bin/vmware: symbol lookup error: /usr/lib/gtk-3.0/3.0.0/immodules/im-ibus.so: undefined symbol: gdk_wayland_display_get_type

jihem commented on 2017-09-30 07:56

Hi guys,

I've just updated the package for the new major release of VMware. It seems to me all works well, but as it is a big update, it's possible I forgot to include some functionalities or something works wrong. If it's the case, and the problem is related to the package and not the program (see VMware forum before), please tell me.

Unfortunately for people who don't want to upgrade (because of license price or incompatible hardware), I won't maintain VMware 12 anymore. It's too complicated for me to maintain two versions at the same time.
Nevertheless, you can easily install the last version of this package for VMware 12.5 (see below for the how-to). This version should work well for a long time: I patched it to work with Linux 4.14, the next LTS version and, if you encounter problems of incompatible libraries in the future (the program crash at startup without writing anything in the terminal), you can solve it by uncomment the line in the file /etc/profile.d/vmware.sh.
Of course, if someone is motivated to maintain VMware 12, feel free to create a new package!

To install the last version of VMware 12:
git clone ssh://aur@aur.archlinux.org/vmware-workstation.git
cd vmware-workstation
git checkout 2965e8782be11ce0049f32fafa96b2d60c0282c8
makepkg -i

jihem commented on 2017-09-25 15:49

Thanks again! I thought that Exec lines work like systemd ExecStart lines but you are right, only the last line is executed (a more simple fix than yours would be to use modprobe with -a argument).
Anyway, I removed the hook. That was finally a bad idea because it's not standard and it does not work with your example (I didn't thought this case).
I also added the note in post_install as I did before adding this hook.

ngkaho1234 commented on 2017-09-25 11:29

@jihem: These changes look good. However, I found that in 90-vmware-load-modules.hook, only the vmmon module would be loaded due to the second occurrence of Exec= overriding the first one. Actually the fix is quite trivial: replacing all the occurrences of Exec= with a single Exec = /bin/sh -c '/usr/bin/modprobe a; /usr/bin/modprobe b' or whatever.

Not only that, in case when users install vmware-workstation.pkg.tar.xz right after doing a pacman system upgrade, the hook will fail due to missing module (since in Arch Linux, upgrading a kernel will remove the modules directory of its previous version). That failure doesn't indicate anything fatal, it just indicates that the hook doesn't do anything in such case (and users still need to reboot).

Thus, I suggest removing the hook in future, and printing some lines in post_install script to tell the users either reboot the machine or manually load the required kernel modules. By doing so, the procedures users need to take when dealing with vmware modules will be mostly the same as dealing with dkms/binary modules in official repo (nvidia/nvidia-lts/nvidia-dkms, wireguard-dkms, broadcom-wl-dkms, ...)

EDITED: Sentenses rewording...

jihem commented on 2017-09-24 10:21

@ngkaho1234: Thank you very much for your review! I decided to switch to vmw_vmci, because it works well and should avoid future incompatibilities and reduce compilation time with DKMS.
I also fixed vmci with your patch because I don't want to let an incorrect source code, even if probably nobody will use it.

ngkaho1234 commented on 2017-09-23 11:37

Hello, according to the implementation of pci_enable_msix_range(), since vmci_enable_msix() must return 0 on success, the changes that makes vmci/linux/driver.c able to compile is wrong. Here is the implementation of pcie_enable_msix() and pcie_enable_msix_range(): http://elixir.free-electrons.com/linux/v4.9.51/ident/__pci_enable_msix_range

Currently, I workaround the issue by applying my own changes to vmci module. Here is the changes i made to the affected part of the vmci module: https://ptpb.pw/oKZB

EDIT: We might also consider switching to vmw_vmci instead of vmci, which is similar to what we already did to vsock.

pshow commented on 2017-09-18 14:47

@Zafar: Hey, this may be because your tmp dir is tmpfs, mouted with noexec. You can run mount -o remount,exec /tmp as root and then would be able to install the bundle.

jihem commented on 2017-09-09 07:11

@jvybihal: Thanks for your report. But these files are needed and I have no idea for a workaround. For the moment, I can just advice you to continue using --force option or add a line in the PKGBUILD to remove these files (if you are sure to keep the other package installed, of course).

jvybihal commented on 2017-09-07 07:32

I already had workstation installed bz .budle package from vmware. I wanted to install vmware-workstation package, but pacman warned me about files already exist in filesystem (obviously). So I used --force (yeah!).

Now pacman warns me, that some files are owned by two packages:

error: file owned by 'vmware-horizon-virtual-printing' and 'vmware-workstation': 'etc/thnuclnt/.thnumod'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/be101'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/be104'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/chde101'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/chde104'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/chfr101'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/chfr104'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/de101'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/de104'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/dk101'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/dk104'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/es101'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/es104'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/fi101'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/fi104'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/fr101'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/fr104'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/gb101'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/gb104'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/is101'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/is104'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/it101'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/it104'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/jp106'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/jp109'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/no101'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/no104'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/pt101'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/pt104'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/se101'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/se104'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/us101'
error: file owned by 'vmware-horizon-client' and 'vmware-workstation': 'usr/lib/vmware/xkeymap/us104'



I am not having a problem, just reporting this, because there appears to be package conflict between vmware-horizon-* and vmware-workstation.

Synthead commented on 2017-08-21 17:51

@jihem: Ok, cool! Sounds like a solid plan! Cheers!

Zafar commented on 2017-08-19 02:04

Hello,
I keep receiving the following error when I attempt to install this pacakge:
Extracting VMware Installer...done.
/home/[username]/vmware-workstation/VMware-Workstation-Full-12.5.7-5813279.x86_64.bundle: line 302: /tmp/vmis.NauOUt/install/vmware-installer/vmware-installer: Permission denied
==> ERROR: A failure occurred in prepare().

I tried commenting out that line in the bundle, but then I run into other errors. How do I fix this?

jihem commented on 2017-08-15 13:42

Thanks Synthead! I will try to continue maintaining this package as long as possible, that was a great idea to create it.

I think I will keep the vmware.conf file because it's the behaviour that the most part of people want. And if you don't want that, you can simply create a void file in /etc/modules-load.d/vmware.conf.
In addition, virtualbox-host-dkms contains an equivalent file, so it's also the choice of Arch maintainers.

Synthead commented on 2017-08-14 21:42

I love seeing this package kept up to date! Thanks to all the hard work!

We probably shouldn't include /usr/lib/modules-load.d/vmware.conf into this package. If a user wants to configure their system to modprobe vmware modules at boot, it should be their choice to do so with whatever modules they want. As of now, the only way to disable probing the modules at boot would be to modify tracked files, which is a Bad Idea (tm).

jihem commented on 2017-08-14 12:20

@dummys: Sorry for the late answer. Unfortunetely I have no idea how to solve your problem. But you can test these workarounds:
- use command "VMWARE_USE_SHIPPED_LIBS=yes vmare"
- test on another kernel (for example linux-lts)
- stop all vmware services before start vmware (to verify if the problem comes from the program itself or the services)

dummys commented on 2017-08-08 15:01

Hi, when using your package I get an error when launching "vmware":

-> $ vmware
Loop on signal 11.
Seems to be a kernel panic, in /tmp/vmware-ui.logs:

2017-08-08T16:32:37+02:00[+0.013]| vmui| W115: Caught signal 11 -- tid 16859 (addr 1430)
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: SIGNAL: rip 0x1430 rsp 0x7ffdf7353b48 rbp 0x1
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: SIGNAL: rax 0x0 rbx 0x7f4f084cfdd0 rcx 0xcdf6c65740 rdx 0xcdf6c65740 rsi 0x7ffdf7354ae8 rdi 0x1
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: r8 0xcdf787dc50 r9 0x2f r10 0xcdf7876cd0 r11 0x206 r12 0x7ffdf7354ae8 r13 0xcdf6c65740 r14 0x7f4f084cfdd8 r15 0x0
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: SIGNAL: stack 7FFDF7353B48 : 0x00007f4f1853d37a 0x000000000000000b
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: SIGNAL: stack 7FFDF7353B58 : 0x0000000000000001 0x00007ffdf7354ae8
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: SIGNAL: stack 7FFDF7353B68 : 0x000000cdf6c65740 0x000000cdf7876cd0
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: SIGNAL: stack 7FFDF7353B78 : 0x00007f4f1853d486 0x00007f4f1871bea0
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: SIGNAL: stack 7FFDF7353B88 : 0x0000000000000006 0x00007ffdf7353c60
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: SIGNAL: stack 7FFDF7353B98 : 0x000000000000001d 0x0000000000000001
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: SIGNAL: stack 7FFDF7353BA8 : 0x000000cdf7876cd0 0x000000000000001d
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: SIGNAL: stack 7FFDF7353BB8 : 0x00007f4f1854193e 0x000000cdf7876cd0
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace:
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[0] 00007ffdf73532b0 rip=00007f4f1051d8fe rbx=00007f4f1051d6d0 rbp=0000000000000000 r12=00007f4f18719b00 r13=00007ffdf7353bc8 r14=00007ffdf73535c0 r15=0000000000000000
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[1] 00007ffdf73532e0 rip=00007f4f1048de68 rbx=00007ffdf7353bc8 rbp=000000000000000b r12=00007f4f18719b00 r13=00007ffdf7353bc8 r14=00007ffdf73535c0 r15=0000000000000000
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[2] 00007ffdf7353570 rip=00007f4f1048e19d rbx=000000000000000b rbp=0000000000000004 r12=00007f4f18719b00 r13=00007ffdf73536f0 r14=00007ffdf73535c0 r15=0000000000000000
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[3] 00007ffdf73535c0 rip=00007f4f1811d7e0 rbx=00007f4f084cfdd0 rbp=0000000000000001 r12=00007ffdf7354ae8 r13=000000cdf6c65740 r14=00007f4f084cfdd8 r15=0000000000000000
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: PANIC: Loop on signal 11.
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace:
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[0] 00007ffdf7352160 rip=00007f4f1051d8fe rbx=00007f4f1051d6d0 rbp=0000000000000000 r12=00007ffdf73525c0 r13=00007ffdf7352ab0 r14=00007ffdf7352980 r15=0000000000000000
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[1] 00007ffdf7352190 rip=00007f4f10261e9a rbx=00007ffdf7352980 rbp=00007f4f17ef0660 r12=00007ffdf73525c0 r13=00007ffdf7352ab0 r14=00007ffdf7352980 r15=0000000000000000
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[2] 00007ffdf73525c0 rip=00007f4f1026204d rbx=00007ffdf7352980 rbp=000000000000000b r12=00007f4f18719b00 r13=00007ffdf7352ab0 r14=00007ffdf7352980 r15=0000000000000000
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[3] 00007ffdf73526a0 rip=00007f4f1048dd60 rbx=00007ffdf7352980 rbp=000000000000000b r12=00007f4f18719b00 r13=00007ffdf7352ab0 r14=00007ffdf7352980 r15=0000000000000000
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[4] 00007ffdf7352930 rip=00007f4f1048e19d rbx=000000000000000b rbp=0000000000000004 r12=00007f4f18719b00 r13=00007ffdf7352ab0 r14=00007ffdf7352980 r15=0000000000000000
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[5] 00007ffdf7352980 rip=00007f4f1811d7e0 rbx=0000000000000000 rbp=00007ffdf7353250 r12=00007ffdf73530a0 r13=00007ffdf7352fb0 r14=0000000000000000 r15=00007f4f1051db00
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[6] 00007ffdf7352f40 rip=00007f4f17f03e07 rbx=0000000000000000 rbp=00007ffdf7353250 r12=00007ffdf73530a0 r13=00007ffdf7352fb0 r14=0000000000000000 r15=00007f4f1051db00
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[7] 00007ffdf7352fb0 rip=00007f4f17f059b8 rbx=0000000000000000 rbp=00007ffdf7353250 r12=00007ffdf7352fb0 r13=00007ffdf73530a0 r14=00007ffdf7353260 r15=00007f4f1051db00
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[8] 00007ffdf7353260 rip=00007f4f1051d86e rbx=00007f4f1051d6d0 rbp=00007ffdf73532ac r12=00007f4f18719b00 r13=0000000000000000 r14=00007ffdf73535c0 r15=0000000000000000
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[9] 00007ffdf73532b0 rip=00007f4f1051d8fe rbx=00007f4f1051d6d0 rbp=0000000000000000 r12=00007f4f18719b00 r13=00007ffdf7353bc8 r14=00007ffdf73535c0 r15=0000000000000000
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[10] 00007ffdf73532e0 rip=00007f4f1048de68 rbx=00007ffdf7353bc8 rbp=000000000000000b r12=00007f4f18719b00 r13=00007ffdf7353bc8 r14=00007ffdf73535c0 r15=0000000000000000
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[11] 00007ffdf7353570 rip=00007f4f1048e19d rbx=000000000000000b rbp=0000000000000004 r12=00007f4f18719b00 r13=00007ffdf73536f0 r14=00007ffdf73535c0 r15=0000000000000000
2017-08-08T16:32:37+02:00[+0.013]| vmui| I125: Backtrace[12] 00007ffdf73535c0 rip=00007f4f1811d7e0 rbx=00007f4f084cfdd0 rbp=0000000000000001 r12=00007ffdf7354ae8 r13=000000cdf6c65740 r14=00007f4f084cfdd8 r15=0000000000000000

eduardolucioac commented on 2017-08-02 19:08

To solve the following problem...

"
Could not open /dev/vmmon: No such file or directory.
Please make sure that the kernel module `vmmon' is loaded.
"

... restart your machine or try the following...

Create the file...

"
/etc/systemd/system/vmware.service
"

... with the following content...

"
[Unit]
Description=VMware daemon
Requires=vmware-usbarbitrator.service
Before=vmware-usbarbitrator.service
After=network.target

[Service]
ExecStart=/etc/init.d/vmware start
ExecStop=/etc/init.d/vmware stop
PIDFile=/var/lock/subsys/vmware
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target
"

Create the file...

"
/etc/systemd/system/vmware-usbarbitrator.service
"

... with the following content...

"
[Unit]
Description=VMware USB Arbitrator
Requires=vmware.service
After=vmware.service

[Service]
ExecStart=/usr/bin/vmware-usbarbitrator
ExecStop=/usr/bin/vmware-usbarbitrator --kill
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target
"

Add the following service as well, if you want to connect to your VMware Workstation installation from another Workstation Server Console...

Create the file...

"
/etc/systemd/system/vmware-workstation-server.service
"

... with the following content...

"
[Unit]
Description=VMware Workstation Server
Requires=vmware.service
After=vmware.service

[Service]
ExecStart=/etc/init.d/vmware-workstation-server start
ExecStop=/etc/init.d/vmware-workstation-server stop
PIDFile=/var/lock/subsys/vmware-workstation-server

[Install]
WantedBy=multi-user.target
"

Start and enable the services...

"
sudo systemctl start vmware.service
sudo systemctl enable vmware.service
sudo systemctl start vmware-usbarbitrator.service
sudo systemctl enable vmware-usbarbitrator.service
sudo systemctl start vmware-workstation-server.service
sudo systemctl enable vmware-workstation-server.service
"

Restart your machine!

That's all folks! =D

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 https://wiki.archlinux.org/index.php/Arch_User_Repository#Installing_packages)
- change the directory used by yaourt to create packages (variable TMPDIR in /etc/yaourtrc)
- prevent /tmp to be used in RAM (https://wiki.archlinux.org/index.php/tmpfs#Disable_automatic_mount)

jmboris commented on 2017-06-18 16:30

Hello

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().
Cancelando…
==> 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):
http://rglinuxtech.com/?p=1932

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 (https://kb.vmware.com/selfservice/microsites/microsite.do?cmd=displayKC&docType=kc&externalId=2073803) and are the maintainers of the official repo (https://github.com/vmware/open-vm-tools).

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: https://wiki.archlinux.org/index.php/Pacman/Pacnew_and_Pacsave).
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

Hi...

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 -
-icon=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

Hi,

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

Enjoy!

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 package...so 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?
https://bbs.archlinux.org/viewtopic.php?id=224667

pelo99 commented on 2017-04-13 06:30

Alternate solution to this.
Just download the latest Installation package from vmware.com 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 :)
https://download3.vmware.com/software/wkst/file/VMware-Workstation-Full-12.5.5-5234757.x86_64.bundle

Awesome_Donkey commented on 2017-03-14 12:48

12.5.4 is out too.

https://download3.vmware.com/software/wkst/file/VMware-Workstation-Full-12.5.4-5192485.x86_64.bundle

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

Described in the comments here: https://aur.archlinux.org/packages/vmware-patch/

And posted here: https://communities.vmware.com/thread/558694

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

Hi,

Thanks for fancy package!

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

https://download3.vmware.com/software/wkst/file/VMware-Workstation-Full-12.5.3-5115892.x86_64.bundle

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

Hi,

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" \
"$pkgdir/etc/vmware"

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

+ 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" \
"$pkgdir/usr/lib/vmware/lib"/{wrapper-gtk24.sh,libgksu2.so.0/gksu-run-helper}

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!