Package Details: vmware-workstation 12.5.7_5813279-6

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: 25
Popularity: 3.609692
First Submitted: 2017-02-10 19:04
Last Updated: 2017-09-25 15:29

Required by (0)

Sources (25)

Latest Comments

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.

All comments