Package Details: vmware-workstation 16.2.3-2

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: jihem
Last Packager: jihem
Votes: 167
Popularity: 3.37
First Submitted: 2017-02-10 19:04 (UTC)
Last Updated: 2022-04-09 13:39 (UTC)

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

jihem commented on 2022-05-11 17:46 (UTC)

@Aleksana This error happens when the gcc version used to build the linux*-header package is different than the gcc version installed on your system. It should not happen if you use an official linux package (linux, linux-lts, linux-zen) but if you build a kernel from AUR, you need to recompile it with the updated gcc.

Asuranceturix commented on 2022-05-11 14:20 (UTC)

@PC2022: I had a similar experience. In my case all those freezes matched with very high CPU activity on the host from kcompactd0. Disabling transparent hugepages as suggested in the Arch Wiki did not solve the issue, but apparently kcompactd0 can be disabled and did solve my issue: https://communities.vmware.com/t5/VMware-Workstation-Pro/VMWare-workstation-in-a-fistfight-with-Linux-Memory-Compactor/td-p/2876992

Aleksana commented on 2022-05-11 12:30 (UTC)

Recently archlinux official changed gcc build version of linux kernel,leading to Error:incompatible gcc/plugin versions

PC2022 commented on 2022-04-28 22:57 (UTC)

Using the MS-Edge Win10 VM image, as supplied by MS.

Performance using vmware-worksation (16.2.3-2) seems to be horrible. It's responsive for a few seconds, then stalls for 10 seconds, rinse and repeat. Task manager shows Win10 is not CPU bound or RAM starved, so it's not clear what's causing the unresponsiveness

VMWare tools is installed, nVidia GeForce RTX 3080 Ti, AMD Ryzen 9 5900X, should be more than capable. Anyone else seeing similar issues?

heimodl commented on 2022-04-21 06:08 (UTC)

@jihem Thanks for your advice.I change "export VMWARE_USE_SHIPPED_LIBS=yes" then reboot my system, and problem fixed.

jihem commented on 2022-04-20 16:45 (UTC)

@heimodl The export to ovf works for me (at least with VMware Workstation, not tested with VMware Player). Maybe this is a problem with dependencies. Can you try to decomment the line export VMWARE_USE_SHIPPED_LIBS=yes in /etc/conf.d/vmware, restart VMware and retry to export your virtual machine, and tell me if that works?

heimodl commented on 2022-04-19 14:56 (UTC) (edited on 2022-04-19 15:15 (UTC) by heimodl)

Hey guys, I just find that exprort vm to ovf failed in the latest versionn(16.2.3-2) Here the error message:


        Export failed: Unknown error, please try again. If the problem 
        persists, please contact VMware Technical Support and provide 
        /tmp/vmware-darklord/ovftool.log

BUT /tmp/vmware-darklord/ovftool.log is null. So i had to change the version to vmware-workstation15 15.5.7-8, then the error disappeared....

Does anybody know the solution? Thanks

sxe commented on 2022-04-08 17:00 (UTC)

ok thx. Btw, I tried v16.2.1 as well and get the same journal spam. Sadly that's the last version I can try. All the older ones won't allow me to build the kernel modules.

ajgringo619 commented on 2022-04-08 15:26 (UTC)

@swx - here it is: https://communities.vmware.com/t5/VMware-Workstation-Pro/Strange-journal-messages-on-working-system/m-p/2903073#M175091

sxe commented on 2022-04-08 14:13 (UTC)

@ajgringo619 Good to know I am not alone. Could you please link to your post, so I can keep an eye on it? Thx

sxe commented on 2022-04-07 11:52 (UTC) (edited on 2022-04-07 11:54 (UTC) by sxe)

I just noticed, as soon as I enable networking

$ sudo systemctl start vmware-networks.service

my journal gets spammed with these messages, non stop and as far as I can tell it never ends spamming.

Apr 07 13:31:57 main kernel: userif-10: sent link up event.

Apr 07 13:31:58 main vmnet-natd[1736]: RTM_NEWADDR: index:2, addr:192.168.0.15

Couldn't find anything searching for it. Does anyone experience something similar or can give me a pointer how to fix it?

Thanks

yurikoles commented on 2022-04-04 03:26 (UTC) (edited on 2022-04-04 03:27 (UTC) by yurikoles)

@jihem

I accepted uefitool and in latest update made binary artifacts names lower-case in accordance to other uefitool-* packages. So please update line 412 of this PKGBUILD accordingly.

Kodehawa commented on 2022-04-02 21:59 (UTC) (edited on 2022-04-02 21:59 (UTC) by Kodehawa)

/var/lib/dkms/vmware-workstation/16.2.3_19376536/build/vmnet-only/bridge.c:956:36: error: passing 'const unsigned char *' to parameter of type 'uint8 *' (aka 'unsigned char *') discards qualifiers [-Werror,-Wincompatible-pointer-types-discards-qualifiers]
         SMAC_SetMac(bridge->smac, bridge->dev->dev_addr);
                                   ^~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/vmware-workstation/16.2.3_19376536/build/vmnet-only/./smac.h:75:45: note: passing argument to parameter 'mac' here
SMAC_SetMac(struct SMACState *state, uint8 *mac); // IN: state, and host MAC
                                            ^
1 error generated.

Anyone knows how to fix this error on DKMS compilation?

jihem commented on 2022-03-18 08:05 (UTC)

@LevitatingRein This is normal, because contrary to the official VMware installer, this package does not place any file in /etc/init.d. Daemons are installed as systemd units. And there is no equivalent systemd service for /etc/init.d/vmware; see https://wiki.archlinux.org/title/VMware#Package_build_for_x86_64 to know which services can be enabled.

LevitatingRein commented on 2022-03-17 20:54 (UTC)

I just did a system upgrade and /etc/init.d disappeared.

I reinstalled this package but the /etc/init.d/vmware file is not coming back.

ZEBofx commented on 2022-03-06 07:54 (UTC) (edited on 2022-03-06 12:42 (UTC) by ZEBofx)

Hello,

On the last 16.2.1-4 version, if you enable "_enable_macOS_guests=y" in PKGBUILD, you have the following error :

-> Téléchargement de unlocker-3.0.7.py…

...

curl: (22) The requested URL returned error: 404

==> ERREUR : Erreur lors du téléchargement de https://raw.githubusercontent.com/DrDonk/unlocker/v3.0.7/unlocker.py

Unlocker has now new versions (not python anymore, it seems ?), and 3.0.7 does not seem to be there anymore.

Thank you.

Best regards,

ZEBofx

buzzra commented on 2022-03-05 21:28 (UTC)

I'm using Manjaro Upgraded using Pamac GUI. It noted the Libcrypt-compat dependency and installed it. Everything works fine.

jihem commented on 2022-02-27 14:23 (UTC) (edited on 2022-02-27 14:24 (UTC) by jihem)

For people using Manjaro, the best solution is probably to not update this package for the moment (stay on 16.2.1-3). libxcrypt-compat dependency is useless for you, it seems that your glibc package already contains the required library. Just be careful during the next system upgrades: when glibc package will be updated, you will probably be able to update this package.

josete commented on 2022-02-27 09:17 (UTC) (edited on 2022-02-27 09:23 (UTC) by josete)

Greetings! My system is Manjaro KDE.

Same issue:

Could not find all required packages:
libxcrypt-compat (Wanted by: vmware-workstation)

I've downloaded libxcrypt-compat-4.4.28-2-x86_64.pkg.tar.zst
I've tried: sudo pacman -U --asdeps libxcrypt-compat-4.4.28-2-x86_64.pkg.tar.zst
The system's answer is:

error: failed to commit transaction (conflicting files)
libxcrypt-compat: /usr/lib/libcrypt.so.1 exists in filesystem (owned by glibc)
Errors occurred, no packages were upgraded.

No idea what to do next.

jihem commented on 2022-02-26 06:39 (UTC) (edited on 2022-02-26 06:43 (UTC) by jihem)

libxcrypt-compat is a new Arch package, if you use Manjaro it could explain why this package does not exist in your repository for the moment.

To complete @yurikoles solution, to install libxcrypt-compat as a dependency (which will be removed when not necessary anymore), you should type sudo pacman -U --asdeps <path/to/>libxcrypt-compat-4.4.28-2-x86_64.pkg.tar.zst

@ajgringo619 the only difference is the addition of libxcrypt-compat dependency, it is very unlikely this is the reason of your problem.

yurikoles commented on 2022-02-26 05:33 (UTC)

@Captn138 @xavierbaez

I also faced the same issue, but the package is still there and available to manual download, which can be installed via sudo pacman -U <path/to/>libxcrypt-compat-4.4.28-2-x86_64.pkg.tar.zst

xavierbaez commented on 2022-02-26 02:51 (UTC)

-> Could not find all required packages: libxcrypt-compat (Wanted by: vmware-workstation)

Captn138 commented on 2022-02-26 00:26 (UTC)

Since 2022/02/25 update (16.2.1-4), the package requires libxcrypt-compat, which is not available to download anymore.

Does someone have a quick'n'dirty fix or can this be corrected somehow?

teka27 commented on 2022-02-24 10:01 (UTC) (edited on 2022-02-24 13:23 (UTC) by teka27)

Hi, my ovftool not working:

ovftool

/usr/lib/vmware-ovftool/ovftool.bin: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory

Edit:

Solved by cp libcrypt.so.1 founded in steam to /usr/lib/vmware-ovftool

jihem commented on 2021-12-27 08:49 (UTC)

@AveryFreeman The file /etc/vmware/networking is created by the service vmware-networks-configuration.service, which is automatically called by the service vmware-networks.service. You should only need to start/enable vmware-networks.service to see all the /dev/vmnet* devices appear.

All of the systemd units are stored in /usr/lib/systemd/system.

AveryFreeman commented on 2021-12-27 05:32 (UTC) (edited on 2021-12-27 05:36 (UTC) by AveryFreeman)

re: Sticky, where are unit files installed? I re-installed using the .bundle before I saw this because I was missing /dev/vmnet{0,1,8}

should I assume /lib/systemd/system, /etc/systemd/user?

arcman commented on 2021-12-20 19:42 (UTC)

not everyone wants to have services they don't use/need to be enabled by default.

cryptodan commented on 2021-12-20 18:13 (UTC)

@jihem, I was under the impression that the service was already started due to the fact that my usb smartcard reader was able yo ne read and passed onto all my vms. The issue was that it wasn't because flashdrives and my integrated camera weren't seen. That's when I determined the arbitrator service wasn't running or enabled at all. I have started and enabled it. I was merely making a feature request in future updates.

jihem commented on 2021-12-20 18:06 (UTC)

@cryptodan Just use the command systemctl enable --now vmware-usbarbitrator.service and the service will be automatically started after each reboot.

cryptodan commented on 2021-12-20 14:21 (UTC)

Would it be possible to add a systemctl command to enable the vmware-usbarbitrator service and to start it? I had to do this manually to enable access to my USB Camera and USB Drives via virtual machines.

aritra1911 commented on 2021-11-17 03:36 (UTC) (edited on 2021-11-17 03:41 (UTC) by aritra1911)

@jihem Thank you so very much. I applied the previously mentioned
patches:
https://github.com/mkubecek/vmware-host-modules/commit/4232f780eb114f22498f3274eaeef81d8c63f2ab.patch
https://github.com/mkubecek/vmware-host-modules/commit/9a6a17fe0bc6d1ab9e0e0dfa8d587b12a21cd49e.patch
and it built and installed like magic:

# dkms install -m vmware-workstation -v 16.2.1_18811642 -k 5.16.0-rc1-archeract

Building module:
cleaning build area...
make -j2 KERNELRELEASE=5.16.0-rc1-archeract KVERSION=5.16.0-rc1-archeract SRCDIR=/usr/src/vmware-workstation-16.2.1_18811642......

Running the post_build script:
Signing module: ../5.16.0-rc1-archeract/x86_64/module/vmmon.ko.zst
Signing module: ../5.16.0-rc1-archeract/x86_64/module/vmnet.ko.zst
cleaning build area...

vmmon.ko.zst:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /usr/lib/modules/5.16.0-rc1-archeract/kernel/drivers/misc/

vmnet.ko.zst:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /usr/lib/modules/5.16.0-rc1-archeract/kernel/drivers/net/
depmod.............

k1f0 commented on 2021-11-16 22:26 (UTC)

@jihem The latest patches completely solved my dkms building errors on 5.15.2-zen, thanks!

jihem commented on 2021-11-16 20:08 (UTC) (edited on 2021-11-16 20:08 (UTC) by jihem)

@aritra1911 I tried to add the patches https://github.com/mkubecek/vmware-host-modules/commit/4232f780eb114f22498f3274eaeef81d8c63f2ab and https://github.com/mkubecek/vmware-host-modules/commit/9a6a17fe0bc6d1ab9e0e0dfa8d587b12a21cd49e in vmmon.patch and vmnet.patch but I still have an error during compilation (using this kernel: https://aur.archlinux.org/packages/linux-mainline) and I don't know how to fix it.

jihem commented on 2021-11-16 17:38 (UTC)

@k1f0 it compiles for me with 5.15.2.zen1-1. Can you provide the content of /var/lib/dkms/vmware-workstation/16.2.1_18811642/build/make.log?

aritra1911 commented on 2021-11-16 09:49 (UTC) (edited on 2021-11-16 10:03 (UTC) by aritra1911)

dkms fails to build for kernel version 5.16.0-rc1

# cat /proc/version
Linux version 5.16.0-rc1-archeract (ray@archeract) (gcc (GCC) 11.1.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP Tue Nov 16 08:54:21 IST 2021

# dkms install --no-depmod -m vmware-workstation -v 16.2.1_18811642 -k 5.16.0-rc1-archeract

Building module:
cleaning build area...
make -j2 KERNELRELEASE=5.16.0-rc1-archeract KVERSION=5.16.0-rc1-archeract SRCDIR=/usr/src/vmware-workstation-16.2.1_18811642...(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.16.0-rc1-archeract (x86_64)
Consult /var/lib/dkms/vmware-workstation/16.2.1_18811642/build/make.log for more information.

Contents of make.log : https://paste.debian.net/plain/1219697
kernel's .config : https://gist.githubusercontent.com/aritra1911/52cffb8ff0c1aa0138d9342d1d7f98dd/raw/ccf14267c5df135c8fa40141f7e5dd09b1c2dfb4/gistfile1.txt

k1f0 commented on 2021-11-15 22:44 (UTC)

dkms install fails for me with latest 5.15 Kernel:

(3/3) Install DKMS modules
==> dkms install --no-depmod vmware-workstation/16.2.1_18811642 -k 5.15.2zen1-1-zen
Error! Bad return status for module build on kernel: 5.15.2-zen1-1-zen (x86_64)
Consult /var/lib/dkms/vmware-workstation/16.2.1_18811642/build/make.log for more information.
==> WARNING: `dkms install --no-depmod vmware-workstation/16.2.1_18811642 -k5.15.2-zen1-1-zen' exited 10

trustin commented on 2021-11-15 06:12 (UTC)

Hi! Could you include the patch mentioned here: https://superuser.com/a/1453932 Without this patch, the guest VM's network will continuously disconnected whenever DHCP lease is over.

-- vmnet-only/userif.c  2017-12-21 17:02:28.555820933 +0100
+++ vmnet-only.jjk/userif.c 2017-12-15 13:22:13.257724953 +0100
@@ -973,6 +973,9 @@
    userIf = (VNetUserIF *)port->jack.private;
    hubJack = port->jack.peer;

+   /* never send link down events */
+   if (!linkUp) return 0;
+
    if (port->jack.state == FALSE || hubJack == NULL) {
       return -EINVAL;
    }

xXPerditorXx commented on 2021-11-06 17:13 (UTC) (edited on 2021-11-06 17:15 (UTC) by xXPerditorXx)

If you get the error with vmmon just use the following command: sudo rmmod vmw_vmci vmmon; sudo modprobe -a vmw_vmci vmmon; sudo systemctl restart vmware-networks.service; sudo systemctl restart vmware-usbarbitrator.service;

If your vm has no internet access but got an ip address use this command: sudo pacman -S dhcpcd && sudo systemctl enable --now dhcpcd.service

This should work

Erz3 commented on 2021-10-28 19:02 (UTC) (edited on 2021-10-28 19:05 (UTC) by Erz3)

Please, excuse me, I shared a wrong log in my first comment. It was failing for other reason.

The actual fail is this:

oct 28 19:48:25 sedentario systemd[1]: Starting VMware Networks...
░░ Subject: A start job for unit vmware-networks.service has begun execution
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit vmware-networks.service has begun execution.
░░ 
░░ The job identifier is 2942.
oct 28 19:48:25 sedentario vmnetBridge[14673]: Bridge process created.
oct 28 19:48:25 sedentario vmnetBridge[14673]: RTM_NEWLINK: name:enp6s0 index:2 flags:0x00011043
oct 28 19:48:25 sedentario vmnetBridge[14673]: Adding interface enp6s0 index:2
oct 28 19:48:25 sedentario vmnetBridge[14673]: Started bridge enp6s0 to virtual network 0.
oct 28 19:48:25 sedentario vmnetBridge[14673]: RTM_NEWROUTE: index:2
oct 28 19:48:26 sedentario vmware-networks[14655]: Failed to start DHCP service on vmnet1
oct 28 19:48:26 sedentario vmware-networks[14655]: Failed to start NAT service on vmnet8
oct 28 19:48:26 sedentario vmware-networks[14655]: Failed to start DHCP service on vmnet8
oct 28 19:48:26 sedentario vmware-networks[14655]: Failed to start some/all services
oct 28 19:48:26 sedentario vmware-networks[14655]: Started Bridge networking on vmnet0
oct 28 19:48:26 sedentario vmware-networks[14655]: Enabled hostonly virtual adapter on vmnet1
oct 28 19:48:26 sedentario vmware-networks[14655]: Enabled hostonly virtual adapter on vmnet8
oct 28 19:48:26 sedentario systemd[1]: vmware-networks.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ An ExecStart= process belonging to unit vmware-networks.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
oct 28 19:48:26 sedentario vmnetBridge[14673]: Stopped bridge enp6s0 to virtual network 0.
oct 28 19:48:26 sedentario vmnetBridge[14673]: Bridge process exiting.
oct 28 19:48:26 sedentario systemd[1]: vmware-networks.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ The unit vmware-networks.service has entered the 'failed' state with result 'exit-code'.
oct 28 19:48:26 sedentario systemd[1]: Failed to start VMware Networks.
░░ Subject: A start job for unit vmware-networks.service has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit vmware-networks.service has finished with a failure.
░░ 
░░ The job identifier is 2942 and the job result is failed.

strayArch commented on 2021-10-28 17:03 (UTC) (edited on 2021-10-28 17:03 (UTC) by strayArch)

16.2.0-1 worked without a hitch for me without reboot, after running

sudo rmmod vmw_vmci vmmon; sudo modprobe -a vmw_vmci vmmon; sudo systemctl restart vmware-networks.service; sudo systemctl restart vmware-usbarbitrator.service;

Erz3 commented on 2021-10-27 20:02 (UTC)

@class101

Nope, I rebooted my system and fail again.

I have sent you by email the output of mkinitcpio -P

class101 commented on 2021-10-27 17:44 (UTC)

@Erz3

I would check the output of mkinitcpio -P. It is supposed to run automatically but something probably wrong happened at this step, or you simply forgot to reboot your system.

Erz3 commented on 2021-10-27 17:14 (UTC) (edited on 2021-10-27 17:27 (UTC) by Erz3)

Hi,

Could someone help me with this issue? I have installed vmware-workstation 16.2.0-1 on my Manjaro with kernel version 5.10.70-1 (LTS), after that linux-headers and finally I have loaded modules. However when I try to start vmware-networks.service it fail with code error "status 1".

journalctl result:

journalctl -xeu vmware-networks.service
oct 26 21:36:54 sedentario vmnetBridge[2385]: RTM_NEWLINK: name:enp6s0 index:>
oct 26 21:36:54 sedentario vmnetBridge[2385]: Adding interface enp6s0 index:2
oct 26 21:36:54 sedentario vmnetBridge[2385]: Can't open vmnet device /dev/vm>
oct 26 21:36:54 sedentario vmnetBridge[2385]: RTM_NEWROUTE: index:2
oct 26 21:36:54 sedentario vmnetBridge[2385]: Can't open vmnet device /dev/vm>
oct 26 21:36:55 sedentario vmware-networks[2367]: Failed to enable hostonly v>
oct 26 21:36:55 sedentario vmware-networks[2367]: Failed to start DHCP servic>
oct 26 21:36:55 sedentario vmware-networks[2367]: Failed to start NAT service>
oct 26 21:36:55 sedentario vmware-networks[2367]: Failed to enable hostonly v>
oct 26 21:36:55 sedentario vmware-networks[2367]: Failed to start DHCP servic>
oct 26 21:36:55 sedentario vmware-networks[2367]: Failed to start some/all se>
oct 26 21:36:55 sedentario vmware-networks[2367]: Started Bridge networking o>
oct 26 21:36:55 sedentario systemd[1]: vmware-networks.service: Control proce>
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ An ExecStart= process belonging to unit vmware-networks.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
oct 26 21:36:55 sedentario vmnetBridge[2385]: Bridge process exiting.
oct 26 21:36:55 sedentario systemd[1]: vmware-networks.service: Failed with r>
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ The unit vmware-networks.service has entered the 'failed' state with resul>
oct 26 21:36:55 sedentario systemd[1]: Failed to start VMware Networks.
░░ Subject: A start job for unit vmware-networks.service has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit vmware-networks.service has finished with a failure.
░░ 
░░ The job identifier is 1824 and the job result is failed.
lines 58-92/92 (END)
oct 26 21:36:53 sedentario modprobe[2366]: modprobe: FATAL: Module vmnet not found in directory /lib/modules/5.10.70-1-MANJARO
oct 26 21:36:54 sedentario vmnetBridge[2385]: Bridge process created.
-- Journal begins at Fri 2021-04-09 00:35:32 WEST, ends at Tue 2021-10-26 21:36:59 WEST. --
oct 26 21:27:55 sedentario systemd[1]: Starting VMware Networks...
░░ Subject: A start job for unit vmware-networks.service has begun execution
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit vmware-networks.service has begun execution.
░░ 
░░ The job identifier is 1941.
oct 26 21:27:55 sedentario modprobe[21018]: modprobe: FATAL: Module vmnet not found in directory /lib/modules/5.10.70-1-MANJARO
oct 26 21:27:55 sedentario vmnetBridge[21037]: Bridge process created.
oct 26 21:27:55 sedentario vmnetBridge[21037]: RTM_NEWLINK: name:enp6s0 index:2 flags:0x00011043
oct 26 21:27:55 sedentario vmnetBridge[21037]: Adding interface enp6s0 index:2
oct 26 21:27:55 sedentario vmnetBridge[21037]: Can't open vmnet device /dev/vmnet0 (No such device or address).
oct 26 21:27:55 sedentario vmnetBridge[21037]: RTM_NEWROUTE: index:2
oct 26 21:27:55 sedentario vmnetBridge[21037]: Can't open vmnet device /dev/vmnet0 (No such device or address).
oct 26 21:27:56 sedentario vmware-networks[21019]: Failed to enable hostonly virtual adapter on vmnet1
oct 26 21:27:56 sedentario vmware-networks[21019]: Failed to start DHCP service on vmnet1
oct 26 21:27:56 sedentario vmware-networks[21019]: Failed to start NAT service on vmnet8
oct 26 21:27:56 sedentario vmware-networks[21019]: Failed to enable hostonly virtual adapter on vmnet8
oct 26 21:27:56 sedentario vmware-networks[21019]: Failed to start DHCP service on vmnet8
oct 26 21:27:56 sedentario vmware-networks[21019]: Failed to start some/all services
oct 26 21:27:56 sedentario vmware-networks[21019]: Started Bridge networking on vmnet0
oct 26 21:27:56 sedentario systemd[1]: vmware-networks.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ An ExecStart= process belonging to unit vmware-networks.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
oct 26 21:27:56 sedentario vmnetBridge[21037]: Bridge process exiting.
oct 26 21:27:56 sedentario systemd[1]: vmware-networks.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ The unit vmware-networks.service has entered the 'failed' state with result 'exit-code'.
oct 26 21:27:56 sedentario systemd[1]: Failed to start VMware Networks.
░░ Subject: A start job for unit vmware-networks.service has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit vmware-networks.service has finished with a failure.
░░ 
░░ The job identifier is 1941 and the job result is failed.
-- Boot c4f64563ead94a39b68b470658f9a5d8 --
oct 26 21:36:53 sedentario systemd[1]: Starting VMware Networks...
░░ Subject: A start job for unit vmware-networks.service has begun execution
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit vmware-networks.service has begun execution.
░░ 
░░ The job identifier is 1824.
oct 26 21:36:53 sedentario modprobe[2366]: modprobe: FATAL: Module vmnet not found in directory /lib/modules/5.10.70-1-MANJARO
oct 26 21:36:54 sedentario vmnetBridge[2385]: Bridge process created.
oct 26 21:36:54 sedentario vmnetBridge[2385]: RTM_NEWLINK: name:enp6s0 index:2 flags:0x00011043
oct 26 21:36:54 sedentario vmnetBridge[2385]: Adding interface enp6s0 index:2
oct 26 21:36:54 sedentario vmnetBridge[2385]: Can't open vmnet device /dev/vmnet0 (No such device or address).
oct 26 21:36:54 sedentario vmnetBridge[2385]: RTM_NEWROUTE: index:2
oct 26 21:36:54 sedentario vmnetBridge[2385]: Can't open vmnet device /dev/vmnet0 (No such device or address).
oct 26 21:36:55 sedentario vmware-networks[2367]: Failed to enable hostonly virtual adapter on vmnet1
oct 26 21:36:55 sedentario vmware-networks[2367]: Failed to start DHCP service on vmnet1
oct 26 21:36:55 sedentario vmware-networks[2367]: Failed to start NAT service on vmnet8
oct 26 21:36:55 sedentario vmware-networks[2367]: Failed to enable hostonly virtual adapter on vmnet8
oct 26 21:36:55 sedentario vmware-networks[2367]: Failed to start DHCP service on vmnet8
oct 26 21:36:55 sedentario vmware-networks[2367]: Failed to start some/all services
oct 26 21:36:55 sedentario vmware-networks[2367]: Started Bridge networking on vmnet0
oct 26 21:36:55 sedentario systemd[1]: vmware-networks.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ An ExecStart= process belonging to unit vmware-networks.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.

sh1sh1n11 commented on 2021-08-13 16:50 (UTC)

@jihem, thank you very much for your to the point and prompt reply! You're awesome! :)

So I did as you said. I first ran the "vmware-netcfg" command, to make sure that the "Use local DHCP service to distribute IP addresses to VMs" option was checked.

I then proceeded with the rest of your instructions. I brought the "vmware-networks.service" down by running "sudo systemctl stop vmware-networks.service", then I got rid of the aforementioned files and folders using "sudo rm -r /etc/vmware/{networking,netmap.conf,vmnet*}". Finally I brought the "vmware-networks.service" back up again using "sudo systemctl start vmware-networks.service".

That fixed all the issues. I noticed that all the deleted files and folders were created anew, and the vmnet* subnets had also changed. The VMs are now able to pick up the IPs upon boot. Thank you so much jihem!

jihem commented on 2021-08-13 15:33 (UTC)

sh1sh1n11: Firstly, check if your virtual network has DHCP enabled. For that, start vmware-netcfg and check if, in the network interface used by your VM, the option "Use local DHCP service to distribute IP addresses to VMs" is activated.

If it is not the problem, you can try to reinitialize network settings. Stop all running VMs and run the following commands:

systemctl stop vmware-networks.service
rm -r /etc/vmware/{networking,netmap.conf,vmnet*}
systemctl start vmware-networks.service

sh1sh1n11 commented on 2021-08-13 12:54 (UTC)

Hi,

Thank you for this package! I've run into an issue where none of my VM's are getting an IP address issued. I am currently on Manjaro Linux Kernel 5.10.56-1-MANJARO (I know. But since it is an Arch Linux derivative, here I am.).

Interestingly, when I edit the "/etc/vmware/vmnet8/dhcpd/dhcpd.leases" file manually, and assign an IP to my VM, then it is able to assign that IP to itself upon boot.

I could only get as far as understanding that Manjaro Linux (and maybe even Arch for that matter) does not have dhcpd service, and instead it has the dhcpcd service. where as the "vmware-networks.service" seems to be running "/usr/bin/vmnet-dhcpd". How can I make it so that I don't have to manually add IPs to the dhcpd.leases file, and the VMs get IPs on boot automatically. Any help in the matter would be awesome! Thank you all.

farwayer commented on 2021-07-22 17:47 (UTC)

I got an error while installing: error: could not extract /usr/lib/vmware/isoimages/VirtualPrinter-Windows.iso (Truncated zstd input)

What can be wrong?

jihem commented on 2021-06-24 20:36 (UTC) (edited on 2021-06-24 20:40 (UTC) by jihem)

No idea why gorgiaxx didn't have the libdir variable set, but I can confirm that AUR packages are generating .pacnew files; actually AUR packages work exactly like official packages, the only difference is that they are not built and distributed by official maintainers.

@class101 To explain my choices, I finally didn't use the PathModified variable because it triggers not only file creation, but also file deletion and modification. During some tests, on one moment I wanted to "reset" my environment by stopping VMware services and removing /run/vmware directory; I realized that removing this directory restarted VMware services, which was clearly not the expected behavior. I know it's not a big deal because probably nobody will touch this directory in real conditions, but I find the PathExistsGlob solution more adapted: when a directory of this pattern is created, I am sure that it correspond to the start of a VM. Also, if a VMware service is stopped whereas at least one VM is still running, the corresponding directory still exists so the service is restarted immediately.

I admit I haven't thought about the performance cost of using regular expressions, but in my opinion it is not significant (systemd probably check a filename matching only when there is a change in /var/run/vmware folder, which happen only when a VM is started or stopped).

About services handling, I just follow what is generally made by maintainers which is to not start services by default (except for some core components). It's especially relevant here because these services are not required for VM execution and some users could want to let them disabled. As you said in a previous message: "It is a good practice under Linux to have the fewest permanent services running" :)

class101 commented on 2021-06-24 12:34 (UTC) (edited on 2021-06-24 12:42 (UTC) by class101)

@gorgiaxx

If you look at the sources, this is already the case https://aur.archlinux.org/cgit/aur.git/tree/config?h=vmware-workstation

I think you have old configuration in /etc/vmware/config and/or maybe a configuration update waiting in /etc/vmware/config.pacnew (not sure if AUR packages are generating .pacnew files, but but these files are good to watch every now and then as they may contain important updates)

@jihem Ty for sharing this idea with others, cool from you ;)

But I haven't used your implementation yet, I doubt that PathExistsGlob= is necessary over PathModified=. The *Glob variable has its own variable name because it make uses of regular expressions, and they have a performance cost over regular methods.

If it was up to me I would have not used PathExistsGlob if there is no specific reasons to use over the regular method.

But that's just different way of thinking anyway, not a big deal, I see you prefer to let the user to handle all the servicing stuff, while for me this is to the package responsability to install and remove the necessary files, I would hate to uninstall a systemd package that would leave behind a whole bunch of installed service, same rule for vmware, Arch Way :s

gorgiaxx commented on 2021-06-24 06:34 (UTC) (edited on 2021-06-24 06:34 (UTC) by gorgiaxx)

VMware workstation 16 start failed after install.

2021-06-24T14:28:00.148+08:00| appLoader| I005: Log for appLoader pid=10417 version=16.1.2 build=build-17966106 option=Release
2021-06-24T14:28:00.148+08:00| appLoader| I005: The host is 64-bit.
2021-06-24T14:28:00.148+08:00| appLoader| I005: Host codepage=UTF-8 encoding=UTF-8
2021-06-24T14:28:00.148+08:00| appLoader| I005: Host is Linux 5.12.12-arch1-1 Arch Linux
2021-06-24T14:28:00.177+08:00| appLoader| I005: Invocation: "/usr/lib/vmware/bin/vmware
2021-06-24T14:28:00.177+08:00| appLoader| I005: "
2021-06-24T14:28:00.177+08:00| appLoader| I005: Calling: "/usr/lib/vmware/bin/vmware
2021-06-24T14:28:00.177+08:00| appLoader| I005: "
2021-06-24T14:28:00.177+08:00| appLoader| I005: VMDEVEL not set.
2021-06-24T14:28:00.177+08:00| appLoader| I005: Using configuration file: /etc/vmware/config
2021-06-24T14:28:00.178+08:00| appLoader| E002: The "libdir" entry was not present in configuration file.
2021-06-24T14:28:00.178+08:00| appLoader| I005: Use library directory: (null)

Append this line to the vmware configuration file.

echo 'libdir = "/usr/lib/vmware"' >> /etc/vmware/config

arcman commented on 2021-06-20 09:38 (UTC)

Thank you jihem.

jihem commented on 2021-06-20 04:51 (UTC) (edited on 2021-06-20 04:51 (UTC) by jihem)

You simply need to do systemctl disable --now vmware-networks.service && systemctl enable --now vmware-networks.path. After that the service will be launched only when a VM is started. Unfortunately it is not a perfect solution because the service won't be stopped when the VM is shutdown.

arcman commented on 2021-06-20 00:30 (UTC) (edited on 2021-06-20 00:31 (UTC) by arcman)

would someone care to explain how do i implement this new .path units solution? when i first installed vmware,i ran systemctl enable vmware-networks.service and now i can see i have vmnet processes running even though Vmware is closed. so how can i have them start only when a vm is launched?

jihem commented on 2021-06-19 13:27 (UTC) (edited on 2021-06-19 13:27 (UTC) by jihem)

@idanyadgar I've tested with the official VMware installer on Fedora 34, same problem (with similar logs). Probably a new library version that break something. I won't investigate more time because it's not a packaging problem, but if you find a workaround I can try to implement it.

jihem commented on 2021-06-19 13:20 (UTC)

@class101 Thanks, it's implemented, juste a little bit differently.

I still let the possibility to launch services at boot time (and of course, to keep them completely disabled, because I totally agree with crdx).

Det commented on 2021-06-15 12:27 (UTC)

@class101, Great response.

idanyadgar commented on 2021-06-12 21:03 (UTC) (edited on 2021-06-12 21:28 (UTC) by idanyadgar)

Power management endpoints in the REST API don't work.

vmrest -d

curl 'http://127.0.0.1:8697/api/vms/C3Q6N31L9CCLTL82I1VJ0DAL9PVL89L6/power' -X GET --header 'Accept: application/vnd.vmware.vmw.rest-v1+json' --header 'Authorization: Basic ENTER_TOKEN_HERE'

And I get: { "power_state": "poweredOff" }

(And the machine is powered on)

Changing the VM power state (to on or suspended) also does not work (I believe it is because the VM is considered off although it isn't).

This API works under other distros.

Thread in VMWare's forums: https://communities.vmware.com/t5/VMware-Workstation-Pro/REST-API-power-management-machines-are-always-off/m-p/2852406

class101 commented on 2021-06-10 12:48 (UTC) (edited on 2021-06-10 12:54 (UTC) by class101)

@crdx

Not every changes in my patch are to consider, I guess you mean about the changes I have added into the .install file, they are much for me here because I prefer to have the thing setup the way I want without much tinkering needed after installing the package, when installing a package from Arch Linux, I exxpect the package to do all the necessary things for the package to work properly, if the package tell me, do X to enable X, do Y to enable Y, I don't think it is either the Arch Way.

The improvment proposal is much about replacing the procedure that is to ask the user to enable .service, you could instead ask the user to enable .path files, that way, the service will only start on-demand when they are needed, instead of providing the only solution which is actually to startup the service permanently and forget about it.

crdx commented on 2021-06-09 20:43 (UTC) (edited on 2021-06-09 20:50 (UTC) by crdx)

Isn't it the arch way never to start services automatically on install, and leave it up to the user to decide if they want to start them or not?

class101 commented on 2021-06-09 09:56 (UTC) (edited on 2021-06-09 10:38 (UTC) by class101)

Security vulnerability ? Doubt it, systemd is a robust core component of Linux and services are root started, not user started.

As you see here[1] there are 11 type of unit files and each can be used to implement on-demand starting of services, as well as parallelized starting of services.[2]

I think the correct type of unit for vmware workstation is .path[3], socket is not suitable in here because the application must be aware of the socket to connect to to trigger the on-demand load.

It does a few days I'm testing this and it works flawlessy, I made a patch so you can experiment the complete suite quickly, basically after applying the patch and rebuilding the package, the vmware-networks and vmware-usbarbitrator services will only start after hitting play on a virtual machine.

https://gist.github.com/class101/8ecb2c6dc8ebb7428a01eb56b2c5f9c5

I don't think it is necessary to implement the stop, it seems outside the scope of the unit files, maybe there is something possible to do with the PathChanged= statement as it seem to trigger on file closed, well I've not tested this yet, I'm just doing a bash alias as the following one in /etc/bash.bashrc, but if someone find a proper way to implement the stop, feel free to share :)

alias vmware-stop='systemctl stop vmware-usbarbitrator.service vmware-networks.service'

Let me know if you have any more questions, you are welcome :)

[1] https://www.freedesktop.org/software/systemd/man/systemd.html
[2] https://www.freedesktop.org/software/systemd/man/systemd.socket.html
[3] https://www.freedesktop.org/software/systemd/man/systemd.path.html

jihem commented on 2021-06-07 16:41 (UTC)

@class101 That is an interesting idea. I'm not familiar with .socket files and I don't know if it is possible, but it seems to be complicated because it requires that a program started with an unprivileged user starts a root service. We also need to be careful that it may be seen as a security vulnerability.

I'm not motivated enough to search a solution myself, but if someone suggests an elegant solution I could implement it.

class101 commented on 2021-06-07 13:59 (UTC) (edited on 2021-06-07 14:13 (UTC) by class101)

@jihem

What would have been awesome, but not sure how is it technically possible, is that instead of asking to enable service files, you could provide .socket files so that the socket will be reponsible of starting the services files when vmware is started, and stopped when vmware is stopped.

It is a good practice under Linux to have the fewest permanent services running, there should be a good reason for a service to run permanently, there is no reason for vmware, and I'm definitely not going to leave them enabled when I don't need them, I will instead start them just before starting up vmware and next boot they won't start automatically.

Like the cups and printers services, logrotate, fstrim, they all use .timer or .socket to work around the need of having services running Permanently, we are on Linux not Windows, Windows is what Windows is today, a big dung that gets slow over time, because of such bad practice :D

strayArch commented on 2021-05-21 23:29 (UTC)

16.1.2 builds, installs, and starts on testing... Thanks!

Morta commented on 2021-05-19 19:45 (UTC)

[quote] GNU nano 5.7 /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/make.log
cc1: Fehler: incompatible gcc/plugin versions cc1: Fehler: Plugin ./scripts/gcc-plugins/structleak_plugin.so kann nicht initialisiert werden make[3]: [scripts/Makefile.build:271: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmmon-only/linux/hostif.o] Fehler 1 make[3]: [scripts/Makefile.build:271: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmmon-only/common/apic.o] Fehler 1 cc1: Fehler: incompatible gcc/plugin versions cc1: Fehler: Plugin ./scripts/gcc-plugins/structleak_plugin.so kann nicht initialisiert werden make[3]: [scripts/Makefile.build:271: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmmon-only/common/comport.o] Fehler 1 cc1: Fehler: incompatible gcc/plugin versions cc1: Fehler: Plugin ./scripts/gcc-plugins/structleak_plugin.so kann nicht initialisiert werden make[3]: [scripts/Makefile.build:271: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmmon-only/common/crosspage.o] Fehler 1 cc1: Fehler: incompatible gcc/plugin versions cc1: Fehler: Plugin ./scripts/gcc-plugins/structleak_plugin.so kann nicht initialisiert werden make[3]: [scripts/Makefile.build:271: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmmon-only/common/cpuid.o] Fehler 1 make[2]: [Makefile:1851: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmmon-only] Fehler 2 make[2]: Verzeichnis „/usr/lib/modules/5.12.3-arch1-1/build“ wird verlassen make[1]: [Makefile:121: vmmon.ko] Fehler 2 make[1]: Verzeichnis „/var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmmon-only“ wird verlassen make: [Makefile:10: vmmon.ko] Fehler 2 make: Es wird auf noch nicht beendete Prozesse gewartet.... CC [M] /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/driver.o CC [M] /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/hub.o CC [M] /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/userif.o CC [M] /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/netif.o CC [M] /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/bridge.o CC [M] /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/procfs.o CC [M] /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/smac_compat.o CC [M] /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/smac.o cc1: Fehler: incompatible gcc/plugin versions cc1: Fehler: Plugin ./scripts/gcc-plugins/structleak_plugin.so kann nicht initialisiert werden cc1: Fehler: incompatible gcc/plugin versions cc1: Fehler: Plugin ./scripts/gcc-plugins/structleak_plugin.so kann nicht initialisiert werden cc1: Fehler: incompatible gcc/plugin versions cc1: Fehler: Plugin ./scripts/gcc-plugins/structleak_plugin.so kann nicht initialisiert werden make[3]: [scripts/Makefile.build:271: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/driver.o] Fehler 1 make[3]: Es wird auf noch nicht beendete Prozesse gewartet.... make[3]: [scripts/Makefile.build:271: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/hub.o] Fehler 1 make[3]: [scripts/Makefile.build:271: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/userif.o] Fehler 1 cc1: Fehler: incompatible gcc/plugin versions cc1: Fehler: Plugin ./scripts/gcc-plugins/structleak_plugin.so kann nicht initialisiert werden cc1: Fehler: incompatible gcc/plugin versions cc1: Fehler: Plugin ./scripts/gcc-plugins/structleak_plugin.so kann nicht initialisiert werden make[3]: [scripts/Makefile.build:271: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/netif.o] Fehler 1 make[3]: [scripts/Makefile.build:271: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/bridge.o] Fehler 1 cc1: Fehler: incompatible gcc/plugin versions cc1: Fehler: Plugin ./scripts/gcc-plugins/structleak_plugin.so kann nicht initialisiert werden cc1: Fehler: incompatible gcc/plugin versions cc1: Fehler: Plugin ./scripts/gcc-plugins/structleak_plugin.so kann nicht initialisiert werden make[3]: [scripts/Makefile.build:271: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/procfs.o] Fehler 1 make[3]: [scripts/Makefile.build:271: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/smac_compat.o] Fehler 1 cc1: Fehler: incompatible gcc/plugin versions cc1: Fehler: Plugin ./scripts/gcc-plugins/structleak_plugin.so kann nicht initialisiert werden make[3]: [scripts/Makefile.build:271: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/smac.o] Fehler 1 make[2]: [Makefile:1851: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only] Fehler 2 make[2]: Verzeichnis „/usr/lib/modules/5.12.3-arch1-1/build“ wird verlassen make[1]: [Makefile:121: vmnet.ko] Fehler 2 make[1]: Verzeichnis „/var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only“ wird verlassen make: *** [Makefile:10: vmnet.ko] Fehler 2 [/quote]

jihem commented on 2021-04-25 16:45 (UTC)

@malacology it's not possible when using this package. It would be necessary to create another package that only includes the files needed by VMware Player. If the goal is to save disk space, it's probably useless: almost all files are libraries and other data (guest tools, ...) that are needed for both Player and Workstation programs.

malacology commented on 2021-04-25 11:27 (UTC)

How to only leave player and uninstall pro version?

PenWNName commented on 2021-03-31 17:27 (UTC) (edited on 2021-04-01 15:18 (UTC) by PenWNName)

While following this guide: https://wiki.manjaro.org/index.php?title=VMware&mobileaction=toggle_view_mobile

to install on manjaro I ran into an issue where the instillation hung once it reached the line: "Extracting VMware Installer...done."

I looked into the process on htop and found it was simply sitting here doing nothing. Any advice on logs or things I could peek at to see what is going on?

--Edit

It finished building the package but I timed out as a sudoer and had to install i with pacman -U. Still unsure of why it seemed to hang for so long.

Cervox commented on 2021-03-15 09:55 (UTC)

Just saying that this has been working great for me and I'm thankful this exists.

jihem commented on 2021-02-26 21:55 (UTC)

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 (UTC)

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

jihem commented on 2021-02-25 18:05 (UTC)

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 (UTC)

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 (UTC)

@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 (UTC)

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 (UTC)

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

injured commented on 2020-11-23 16:34 (UTC)

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

sizzen commented on 2020-11-21 19:59 (UTC)

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 (UTC) (edited on 2020-11-21 10:45 (UTC) by injured)

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?

brandimarte commented on 2020-11-19 13:33 (UTC)

I found a solution that worked for me here. The idea is to install polkit-gnome, then run:

$ /usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1 &
$ vmplayer

This will prompt a window for the sudo password and after that wmplayer runs normally. Apparently it's only needed in the first run. I've removed the installation of polkit-gnome and I can still run vmware without root privileges.

brandimarte commented on 2020-11-19 11:08 (UTC)

I'm trying to use wmplayer, but then it prompts a welcome window where I choose "Use WMware Player 16 for free for non-commercial use" and when I click "Finish" the following error appears in the terminal:

==== AUTHENTICATING FOR org.freedesktop.policykit.exec ====
Authentication is needed to run `/usr/lib/vmware/bin/vmware-setup-helper' as the super user
Authenticating as: xxxx@yyyy,,,, (xxxx)
Password: 
polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
==== AUTHENTICATION FAILED ====
Error executing command as another user: Not authorized

This incident has been reported.

where xxxx is my login name and yyyy is the hostname. I can only execute wmplayer as sudo. Anyone here had a similar issue and could recommend a solution? Thanks!

obelix1502 commented on 2020-11-18 22:30 (UTC)

Anyway, kernel 58 is out of date, so for vmware and vmmon 58 it doesn't matter anymore. I didn't make any modification and it works perfectly under the LTS 59 kernel.

injured commented on 2020-11-18 18:14 (UTC)

Installing macOS 11.0.1. Kernel 58, then 59. Loop during installation on both kernels. Anyone had such a condition?

jihem commented on 2020-11-11 18:34 (UTC)

Ok. Clearly I don't understand how Manjaro handles kernels, but in the future you should always check that you use the same version of linuxXX and linuxXX-headers to avoid this problem. Also, I don't know why you had a reference to 5.8.10 version on your first message, maybe you installed linux58-headers, in that case you can probably remove it now.

mkono87 commented on 2020-11-11 17:38 (UTC) (edited on 2020-11-11 17:53 (UTC) by mkono87)

@jihem uname - r results in 5.9.3-1-MANJARO

I then installed the linux59-headers

pacman -Qi linux-headers results in Name : linux54-headers Version : 5.4.74-1 Description : Header files and scripts for building modules for Linux54 kernel Architecture : x86_64 URL : http://www.kernel.org/ Licenses : GPL2 Groups : None Provides : linux-headers=5.4.74 Depends On : None Optional Deps : None Required By : linux-lts-headers Optional For : dkms vmware-workstation Conflicts With : None Replaces : None Installed Size : 46.92 MiB Packager : Manjaro Build Server <build@manjaro.org> Build Date : Sun 01 Nov 2020 08:42:10 AM Install Date : Wed 11 Nov 2020 10:18:02 AM Install Reason : Explicitly installed Install Script : No Validated By : Signature

Yes im running Manjaro. In kernels its says im running 5.9

EDIT: by running modprobe vmmon again it seems to be working. Well except for networking but im working on that.

jihem commented on 2020-11-11 17:10 (UTC)

My first idea is that your linux and linux-headers packages are not on the same version but I need more informations on your installation to be sure. You use Manjaro, right? What is the result of the command "uname -r"? What are the versions of your packages linux and linux-headers? You can have this information using the commands "pacman -Qi linux" and "pacman -Qi linux-headers". If you use Manjaro, these packages can have a slightly different name, like linux59, linux59-headers, linux58-headers...

mkono87 commented on 2020-11-11 15:30 (UTC)

@jihem modprobe: FATAL: Module vmmon not found in directory /lib/modules/5.9.3-1-MANJARO

Your kernel headers for kernel 5.8.10.arch1-1 cannot be found at /usr/lib/modules/5.8.10.arch1-1/build or /usr/lib/modules/5.8.10.arch1-1/source. You can use the --kernelsourcedir option to tell DKMS where it's located. Im on kernel 5.9 atm and I only see an option for 5.8.14.

jihem commented on 2020-11-09 18:01 (UTC) (edited on 2020-11-09 18:04 (UTC) by jihem)

@haomingbai this message also appears when using the official installation. The proxy.xml file was used on previous VMware versions for shared VMs functionnality. I think it is totally useless now, the fact this message appears is probably a bug.

@mkono87 some verifications to do:

  • do you have linux-headers package installed?
  • if yes, can you check if both linux and linux-headers packages are on the same version, and if this version is 5.8.10.arch1-1?
  • if yes, can you manually load the module vmmon with the command "modprobe vmmon" (launched with root privileges)?
  • if no, do you have the file /usr/lib/modules/5.8.10.arch1-1/kernel/drivers/misc/vmmon.ko on your filesystem?
  • if no, what is the result of the command (with root privileges) "dkms install -m vmware-workstation -v 16.0.0_16894299 -k 5.8.10.arch1-1"?

haomingbai commented on 2020-11-09 10:47 (UTC)

I/O warning : failed to load external entity "/etc/vmware/hostd/proxy.xml" cannot connect to network

mkono87 commented on 2020-11-08 17:51 (UTC)

Iv tried everything but im also getting the modprobe: WARNING: Module vmmon not found in directory /lib/modules/5.8.10-arch1-1

can some help me out. I just cant seem to figure it out after reading the comments on here.

jihem commented on 2020-10-18 12:37 (UTC)

Sffred: it seems something is incoherent in your system, you have two references to the kernel: one in version 5.9.1 (which compiles successfully) and the over in version 5.8.8. Maybe the package linux-headers is in version 5.9.1 and the package linux is still in version 5.8.8, or you boot on a wrong vmlinuz-linux file. But the problem doesn't come from vmware-workstation package.

ericx commented on 2020-10-13 21:50 (UTC)

Solved the "hung at license" problem. It needs to be able to write the license in /etc/vmware/license-ws-160-e4-202001; so run it once as root or make /etc/vmware writable by whomever (at least until the license is written).

ericx commented on 2020-10-13 20:59 (UTC)

After upgrading, workstation 16 opens to request a license key (I provided one), but then the "Finish" button does nothing but dim when clicked and the dialog stays open. kernel modules are loaded, vmware-networks and vmware-usbarbitrator are both running (vmware-authd is not). There are no errors in any log files I can see, permissions are clear for write to ~/.vmware. /etc/vmware/config already says "VMware Player"

zangoku commented on 2020-09-27 02:03 (UTC)

can't bridge anything since the upgrade to 16 The network bridge on device '/dev/vmnet0' is not running.

Cervox commented on 2020-09-20 08:51 (UTC) (edited on 2020-09-20 08:54 (UTC) by Cervox)

Nevermind, didn't know that I needed to go out of my way to build the DKMS packages. Did that by reinstalling the linux package, no errors or stuff like that now. It's all working! Thank you so much for making this!

Cervox commented on 2020-09-20 08:43 (UTC)

Getting an error where vmmon is not found when running the modprobe command.

"modprobe: WARNING: Module vmmon not found in directory /lib/modules/5.8.10-arch1-1"

I'm also unable to start the vmware-networks.service. What am I doing wrong here? https://paste.ubuntu.com/p/VdDqbVrbdF/

hecsa commented on 2020-09-20 04:14 (UTC)

Worked like a charm! Thanks a lot! Best regards, HeCSa.

jihem commented on 2020-09-19 10:03 (UTC) (edited on 2020-09-19 10:04 (UTC) by jihem)

The package is now updated to VMware Workstation 16!

Please note that in this release, VMware has removed shared VMs functionnality. If you need it, you have to stay to VMware Workstation 15 (you can switch to the vmware-workstation15 package).

For people using VMware Player, if you have the message proposing you to get a trial license, edit the file /etc/vmware/config to configure the field product.name to "VMware Player", then restart vmplayer.

jihem commented on 2020-09-16 17:26 (UTC)

Hi guys, I know the new version of VMware is released but I probably won't update the package before the end of the week. Major upgrades often have small changes in the installation procedure so I have to check if all files are correctly installed and if no functionnality is broken, which is longer than just changing a number in the PKGBUILD. Please be patient! :)

alcomatt commented on 2020-09-16 16:57 (UTC)

Version 16 is out. Just a heads up.

jihem commented on 2020-09-13 08:47 (UTC)

@hecsa The file vmware-workstation.install was probably removed by error (by you or your AUR helper). Remove the directory containing the PKGBUILD and restart the building procedure.

hecsa commented on 2020-09-13 02:20 (UTC)

Hi!
When updating the package I ran into this:

Building vmware-workstation...
==> ERROR: install file (vmware-workstation.install) does not exist or is not a regular file.

Any ideas?
Thanks in advance and best regards,
HeCSa.

hoschi commented on 2020-09-10 08:46 (UTC) (edited on 2020-09-10 08:47 (UTC) by hoschi)

Hello!
When I reboot my virtual Windows 10 withing VMWare it causes a complete freeze of the host system. This seems to happen only with Wayland, when I switch to use X11 it seems to work fine. Anyone else?

PS: I'm using GNOME.

abruegmann commented on 2020-09-07 21:28 (UTC)

@jihem, @peeweep - thank you so much. Great job!

jihem commented on 2020-09-06 16:48 (UTC)

@peeweep: Now the package is compatible with Linux 5.9. I've updated with two patches from https://github.com/mkubecek/vmware-host-modules/commits/workstation-15.5.6. One of the patches is equivalent to yours.

peeweep commented on 2020-09-05 22:13 (UTC)

jihemel, would you like to add the kernel 5.9 support? I email you a patch.

--- a/vmmon-only/linux/hostif.c
+++ b/vmmon-only/linux/hostif.c
@@ -1739,7 +1739,9 @@
    lockedPages += global_page_state(NR_PAGETABLE);
 #endif
    /* NR_SLAB_* moved from zone to node in 4.13. */
-#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 13, 0)
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(5, 9, 0)
+   lockedPages += global_node_page_state_pages(NR_SLAB_RECLAIMABLE_B);
+#elif LINUX_VERSION_CODE >= KERNEL_VERSION(4, 13, 0)
    lockedPages += global_node_page_state(NR_SLAB_UNRECLAIMABLE);
 #else
    lockedPages += global_page_state(NR_SLAB_UNRECLAIMABLE);

jihem commented on 2020-09-05 19:12 (UTC)

@gbr Thanks, these patches work well, no crash detected for the moment with Linux 5.8. I've updated the package with them.

gbr commented on 2020-09-05 00:51 (UTC)

Hi, can you take a look at this patch for 5.8 and maybe add it to your package? Thanks!

jihem commented on 2020-09-01 16:40 (UTC)

@sphere101 yes, I prevent the module vmmon to be compiled with Linux 5.8 because it is not compatible (see the pinned comment). For the moment you should stay on an LTS kernel version if you want to use VMware.

sphere101 commented on 2020-09-01 13:01 (UTC)

It appears that the latest linux kernel was not able to build the vmmon module.

Linux thor 5.8.5-arch1-1 #1 SMP PREEMPT Thu, 27 Aug 2020 18:53:02 +0000 x86_64 GNU/Linux

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

Does anyone have a workaround??

Thank you

obelix1502 commented on 2020-08-28 20:06 (UTC)

@jihem

This is my Manjaro-kernel : uname -a Linux obelix-kde 5.7.19-1-MANJARO #1 SMP PREEMPT Thu Aug 27 15:41:46 UTC 2020 x86_64 GNU/Linux

And now, no more problem with vmware: I don't know what happened.

jihem commented on 2020-08-28 08:42 (UTC)

@obelix1502 I've made a Manjaro installation with kernel 5.7.15-1-MANJARO (I don't know where you found a 5.7.17 kernel on Manjaro repositories). No problem to build and install vmmon module. I've also started a VM with Fedora live CD on it, no problem to share folders. I can't help you with no more informations. Maybe the operating system of your VM does not support folder sharing, or you didn't install guest additions correctly. For the vmmon problem, be sure to install the linux-headers corresponding to your kernel (in Manjaro, it seems there is a package linux54-headers for linux 5.4 and linux57-headers for linux 5.7).

obelix1502 commented on 2020-08-26 17:04 (UTC)

@jihem, I can't answer you for the moment, I logged on to kernel 5.4. On this one, VmWare launches without problem. Except that my shared folders do not mount in the guest machine. The problem of the launching of VmWare arises only with the 5.7 kernel. I cannot give you the return of commands now because I absolutely cannot, for the moment, disconnect myself from my session to switch to 5.7. But if you could already advise me on my folder sharing problem... This is very important for my job. Thank you for your help.

jihem commented on 2020-08-26 16:33 (UTC)

@obelix1502: does the file /usr/lib/modules/$(uname -r)/kernel/drivers/misc/vmmon.ko exists? If not, what's the output of the command dkms install -m vmware-workstation -v 15.5.6_16341506 -k $(uname -r)?

obelix1502 commented on 2020-08-26 14:40 (UTC)

@jihem, yes linux-headers are installed.

jihem commented on 2020-08-25 14:29 (UTC)

@obelix1502: do you have the package linux-headers installed?

obelix1502 commented on 2020-08-25 14:12 (UTC)

I receive this error :

sudo modprobe -a vmw_vmci vmmon [sudo] Mot de passe de obelix : modprobe: WARNING: Module vmmon not found in directory /lib/modules/5.7.17-2-MANJARO

Wennadocta commented on 2020-08-24 14:30 (UTC) (edited on 2020-08-24 14:32 (UTC) by Wennadocta)

@shamhunter No, you can't. DKMS module will not compile on 5.8. But you can switch to LTS kernel and it will work with no problems

sunerpy commented on 2020-08-24 07:16 (UTC) (edited on 2020-08-24 07:17 (UTC) by sunerpy)

Anyone can run it with kernel 5.8?

Wennadocta commented on 2020-08-22 12:20 (UTC)

It works fine on LTS kernel :)

jihem commented on 2020-08-08 12:13 (UTC)

Be careful: Linux 5.8 breaks compatibility with VMware Workstation. If you try to start a VM, your system will crash and probably reboot.

For the moment, the only solution is to wait a new version of VMware before updating Linux kernel. The problem is serious and it seems there is no workaround I can use. For those interested, you can find some informations in this thread: https://communities.vmware.com/thread/638457.

Please do not mark this package out of date until a new VMware version is released.

jihem commented on 2020-08-04 16:30 (UTC)

huyizheng: thanks to point this issue, I can confirm the reboot in my case. I pin your comment.

huyz commented on 2020-08-04 12:28 (UTC)

Please note that until now, vmware cannot run with linux kernel 5.8. On linux kernel 5.8, the system will freeze or reboot when guest VM is powering on.

http://rglinuxtech.com/?p=2779

yurikoles commented on 2020-07-28 08:04 (UTC)

Please checkout my package vmware-workstation-tech-preview, which has support of DirectX 11 on Windows Guest.

@jihem I had added you as co-maintainer

jihem commented on 2020-07-25 05:57 (UTC)

@dvb I think the more simple way is to open vmware with root (sudo vmware) and ask a trial license.

dvb commented on 2020-07-24 23:17 (UTC)

Anyone knows how I am supposed to workaround that "entering the serial as root" by doing sudo /usr/lib/vmware/bin/vmware-enter-serial for getting rid of as non-root user ==== AUTHENTICATING FOR org.freedesktop.policykit.exec ==== Authentication is needed to run `/usr/lib/vmware/bin/vmware-setup-helper' as the super user if I don't have any serial because I just want to use VMWare Player which is free to use?

Jeffprod commented on 2020-06-29 09:31 (UTC)

@aizomul I had the same issue :

==== AUTHENTICATING FOR org.freedesktop.policykit.exec ====
Authentication is needed to run `/usr/lib/vmware/bin/vmware-setup-helper' as the super user

This was because i was entering a licence number, and for any reason this must be done as root. So the solution is to make it once :

sudo /usr/lib/vmware/bin/vmware-enter-serial

Then you can start vmware as normal user.

fosskers commented on 2020-06-11 17:28 (UTC)

To Aura users trying to install this package and having issues: upgrade Aura to 3.1.3 (or later) and the issue will be solved.

Apologies to @jihem for the spam this caused him.

jihem commented on 2020-05-30 10:33 (UTC)

CaskAle13c: I already started to create a package for this version, but I didn't spend time to test it. You could be able to build the package by applying the following patch on the current PKGBUILD version: https://pastebin.com/Uri4Y2ej

CaskAle13c commented on 2020-05-28 21:19 (UTC)

@jihem, Have you, by any chance, tried out your package build on the Workstation Pro 20H2 Tech Preview?

https://communities.vmware.com/community/vmtn/beta/workstation-pro

jihem commented on 2020-05-09 10:02 (UTC)

sizzen: After the first installation of this package, you should never have to manually load the vmmon module because it is already loaded at startup (see /usr/lib/modules-load.d/vmware.conf). So, after a kernel update and before reboot, the module compiled for the running kernel is already loaded (no need to load it again) and during the reboot the module compiled for the new kernel version is loaded (no need to load it too).

sizzen commented on 2020-05-08 07:15 (UTC)

5.6.11-arch1-1 modprobe: WARNING: Module vmmon not found in directory /lib/modules/5.6.11-arch1-1

When I load the kernel modules after a system update vmnom does exist. Do I need to install the new package everytime there is a kernel update or is there another way around this?

xanadu73 commented on 2020-05-03 13:15 (UTC)

jihem: I'll look into that, thank you.

jihem commented on 2020-05-03 10:18 (UTC)

xanadu73: I never add this problem, on this package or any other using DKMS. I think something is broken in your installation. Do you use a package (like kernel-modules-hook) that change the behaviour of DKMS or kernel modules management? It could be the reason. Or maybe some previous modules was not uninstalled correctly. Check with dkms status if you only have the modules related to your current kernels installed.

xanadu73 commented on 2020-05-02 14:41 (UTC)

Sometimes things get confused and for some reason DKMS fails to complie modules after kernel update. A workaround is to remove vmware-workstation (without touching anything else related to it) reboot and install it again. Your settings won't be lost.

Tx3hc78 commented on 2020-03-20 14:21 (UTC)

@jihem: my mistake, I didn't reboot before loading modules.

majed17 commented on 2020-03-19 06:06 (UTC)

Peace, so would you say, if the day were 39 hours, then you would have enough time to help? the answer is: i just do not desire to spend that much time ...

jihem commented on 2020-03-18 17:57 (UTC)

For people with the DKMS problem: I don't have any idea what can explain this problem. It seems that your PATH is removed somewhere during the installation. Can you try to install another package using DKMS (for example virtualbox-host-dkms) to see if the problem still exists? If yes you should ask some help on Arch forum, else tell me and I will try to investigate why this problem appears only on my package.

@Tx3hc78: did you install the linux-headers package (version 5.5.9.arch1-2)? If yes, do you have the DKMS problem talked in the previous comments?

@dmshimself: as someone said in a previous comment, you can start workstation a first time and ask a trial license. After that when you start vmplayer it won't ask you for a license key, even after the trial time expires. (Note: I didn't test that trick myself.)

@aizomul: I think sudo is only needed to activate a license key. If you use the trick explained in the previous paragraph (and use sudo when you start workstation for asking a trial), you shouldn't need to use sudo when starting vmplayer after that.

@nguyenl95: no problem for me. Maybe you have a different network configuration between Chrome and curl (for example the use of a proxy).

For everybody: sorry for the late answers, but I really don't have a lot of time to help you.

dmshimself commented on 2020-03-18 02:20 (UTC)

I've run up vmplayer and I'm asked for a licnese key for workstation. I've run vmplayer directly and it does the same. Is there a way to just use vmplayer as I don't need the ful features of workstation?

Tx3hc78 commented on 2020-03-17 12:17 (UTC)

When I run: sudo modprobe -a vmw_vmci vmmon

I get this error: modprobe: WARNING: Module vmmon not found in directory /lib/modules/5.5.9-arch1-2

Help?

nguyenl95 commented on 2020-03-16 07:21 (UTC)

curl: (22) The requested URL returned error: 416 ==> ERROR: Failure while downloading https://download3.vmware.com/software/wkst/file/VMware-Workstation-Full-15.5.2-15785246.x86_64.bundle Aborting... Failed to build vmware-workstation

Anyone in this situation? Weird, Chrome works fine with the link.

Alvo commented on 2020-03-08 02:00 (UTC)

I ran into the same issue fosskers had. I was able to fix it by running dkms commands in the shell.

aizomul commented on 2020-03-06 18:11 (UTC)

@fosskers still can't tried setting groups and all but I'm unable to use vmplayer without sudo....

fosskers commented on 2020-03-05 15:04 (UTC)

@aizomul I noticed that I too had to run sudo vmware, but only the first time in order to get through that initial permissions issue. Afterward, vmware works just fine.

aizomul commented on 2020-03-05 12:05 (UTC) (edited on 2020-03-05 12:07 (UTC) by aizomul)

@CaskAle13c

When I run vmplayer, it runs okay until the part where I have to select the try 15 day trial.

The moment I click next, it prompts me.


==== AUTHENTICATING FOR org.freedesktop.policykit.exec ====
Authentication is needed to run `/usr/lib/vmware/bin/vmware-setup-helper' as the super user

The permissions of the files are all set to 755.

I have to sudo vmplayer in order for it to run smoothly.

CaskAle13c commented on 2020-03-05 11:54 (UTC)

@fosskers I have never needed sudo to use vmplayer. I did nothing special to make this happen. So, what happens when you try to run without sudo? I am wondering if you do not have proper permission/ownership on your vm files?

aizomul commented on 2020-03-05 07:26 (UTC)

Have you any idea how to use vmplayer without sudo?

fosskers commented on 2020-03-03 21:48 (UTC) (edited on 2020-03-04 17:30 (UTC) by fosskers)

If I force the absolute paths for cp, it progresses a bit:

DKMS make.log for vmware-workstation-15.5.1_15018445 for kernel 5.5.7-arch1-1 (x86_64)
Tue Mar  3 13:47:29 PST 2020
/usr/bin/cp -r /usr/src/vmware-workstation-15.5.1_15018445/vmmon-only vmmon-only
/usr/bin/cp -r /usr/src/vmware-workstation-15.5.1_15018445/vmnet-only vmnet-only
make KVERSION=5.5.7-arch1-1 VM_KBUILD=yes -C vmnet-only
make: make: No such file or directory
make: *** [Makefile:13: vmnet.ko] Error 127
make: *** Waiting for unfinished jobs....

make can't find itself? Hahaha


If I do the same thing for make it gets further, but...

make[2]: Entering directory '/usr/lib/modules/5.5.7-arch1-1/build'
make[2]: Entering directory '/usr/lib/modules/5.5.7-arch1-1/build'
make[2]: uname: No such file or directory
make[2]: uname: No such file or directory
make[2]: gcc: No such file or directory
make[2]: gcc: No such file or directory
  CC [M]  /var/lib/dkms/vmware-workstation/15.5.1_15018445/build/vmmon-only/linux/driver.o
gcc: fatal error: cannot execute 'cc1': execvp: No such file or directory
compilation terminated.
...

Something seems not right with how the environment is set up. Perhaps the PATH var is somehow bad?


Yes PATH seems to be completely unset within the build environment.


This diff finally made it succeed:

diff --git a/Makefile b/Makefile
index 4b58992..edc4a0a 100644
--- a/Makefile
+++ b/Makefile
@@ -10,15 +10,15 @@ MODULES = \
 all: $(foreach m, $(MODULES), $m.ko)

 %.ko: %
-       $(MAKE) KVERSION=$(KVERSION) VM_KBUILD=yes -C $*-only
+       /usr/bin/env PATH=/bin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/usr/bin/core_perl /usr/bin/make KVERSION=$(KVERSION) VM_KBUILD=yes -C $*-only

 $(MODULES): %:
-       cp -r $(SRCDIR)/$*-only $*-only
+       /usr/bin/env PATH=/bin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/usr/bin/core_perl /usr/bin/cp -r $(SRCDIR)/$*-only $*-only

 vsock.ko: vmci.ko

 clean:
-       rm -rf $(MODULES)
-       rm -rf $(foreach m, $(MODULES), $m-only)
-       rm -f  $(foreach m, $(MODULES), $m.ko)
-       rm -f  $(foreach m, $(MODULES), $m.o)
+       /usr/bin/rm -rf $(MODULES)
+       /usr/bin/rm -rf $(foreach m, $(MODULES), $m-only)
+       /usr/bin/rm -f  $(foreach m, $(MODULES), $m.ko)
+       /usr/bin/rm -f  $(foreach m, $(MODULES), $m.o)

fosskers commented on 2020-03-01 16:10 (UTC)

@jihem: Thanks for getting back to me.

Ah, you're right, this is failing to find cp here, not cp failing to find the file. Notice the difference in error messages:

cp -r /usr/src/vmware-workstation-15.5.1_15018445/vmmon-only vmmon-only
make: cp: No such file or directory

vs

colin@yumi ~> cp FOO ~/code/
cp: cannot stat 'FOO': No such file or directory

But cp is a standard command... how could it not find it? And:

colin@yumi ~> which cp
/bin/cp

jihem commented on 2020-03-01 10:09 (UTC)

@fosskers: Sorry the the late answer, I'm currently very busy. Your problem seems to be not related to my package. dkms cannot find /usr/bin/cp binary, so something is broken in your installation. You can try to investigate by manually running dkms (command "dkms build vmware-workstation/15.5.1_15018445 -k 5.5.6-arch1-1"), checking if you can use cp command in your shell...

fosskers commented on 2020-02-26 21:49 (UTC) (edited on 2020-02-26 21:51 (UTC) by fosskers)

I'm getting this issue, which seems related to recent comments:

colin@yumi ~> sudo modprobe -a vmw_vmci vmmon
modprobe: WARNING: Module vmmon not found in directory /lib/modules/5.5.6-arch1-1

Note also that dkms has an error in the post-transaction hooks stage:

colin@yumi ~> cat /var/lib/dkms/vmware-workstation/15.5.1_15018445/build/make.log
DKMS make.log for vmware-workstation-15.5.1_15018445 for kernel 5.5.6-arch1-1 (x86_64)
Wed Feb 26 13:44:01 PST 2020
cp -r /usr/src/vmware-workstation-15.5.1_15018445/vmmon-only vmmon-only
make: cp: No such file or directory
make: *** [Makefile:16: vmmon] Error 127

I had linux-headers installed already before I attempted this build. Does this ring a bell?

jihem commented on 2020-02-10 17:36 (UTC)

@grunix: I added the step of installing headers package in the pinned comment.

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

grunix commented on 2020-02-09 18:41 (UTC)

@friday: what's about a warning if the headers of to the running kernel are not installed to the system? (Or at least a sticky comment here) This will save every new user >=10 minutes...

friday commented on 2020-01-26 03:06 (UTC)

@grunix That's not possible. linux-headers are just for people running linux. For alt kernels such as linux-lts and linux-zen it's linux-lts-headers, linux-zen-headers (and more variants). You can have multiple kernels and kernel headers on the same system, so dependencies can't catch this.

@trumee: Pick the "try" option, then only use VMWare Player (not Workstation). It won't expire.

grunix commented on 2020-01-25 14:51 (UTC)

please add linux-headers at least to the build dependencies. Missing vmmon module was caused by missing linux-headers packet on my system.

trumee commented on 2020-01-25 06:45 (UTC)

I want to use the non-commerical player. When i run /usr/bin/vmplayer, i get an window to trial vmware for 15 to 30 days. How can i get rid of this screen?

jihem commented on 2020-01-03 16:03 (UTC)

I generally build and test the package with macOS support, that's why .SCRINFO contains the dependencies for macOS support. It's the problem for PKGBUILDs with options: the .SCRINFO can match with only one configuration. I think I should always build the .SRCINFO for default configuration (without macOS support) in the future.

I don't know why pkgbuilder installs dependencies from .SCRINFO but makepkg ignores this file and only use the PKGBUILD.

GiRa commented on 2020-01-03 11:32 (UTC)

jihem, you are right. It seems I just found a bug in pkgbuilder then. It pulls in it as a build dependency anyway, so I patched .SRCINFO and PKGBUILD and run makepkg manually.

I noticed that makepkg does not complain about missing uefitool-git when running manually. Thanks for your patience :)

jihem commented on 2020-01-03 11:24 (UTC)

GiRa: I agree with you. But it's already the case, if you read the PKGBUILD you will see this dependency is only added when the variable _enable_macOS_guests is set.

GiRa commented on 2020-01-03 10:14 (UTC)

I think that uefitool-git should not be required by default. It's needed only for people who want to run MacOS.

jihem commented on 2019-12-21 18:05 (UTC)

@jrbaldridge Thanks for your suggestion. I applied your patch.

I also changed the URL for macOS unlocker.

friday commented on 2019-12-21 04:36 (UTC)

_enable_macOS_guests=y doesn't work any more :( The repository is deleted.

jrbaldridge commented on 2019-12-19 22:28 (UTC)

It looks like vmware-networks-configuration.service is currently triggered by any of the following files missing:

/etc/vmware/networking /etc/vmware/vmnet1/dhcpd/dhcpd.conf /etc/vmware/vmnet1/dhcpd/dhcpd.leases /etc/vmware/vmnet8/dhcpd/dhcpd.conf /etc/vmware/vmnet8/dhcpd/dhcpd.leases /etc/vmware/vmnet8/nat/nat.conf

Unfortunately this means if you remove vmnet1 or vmnet8, vmware-networks-configuration.service will be triggered and reconfigure all your networks. It looks like /etc/vmware/networking alone should provide a sufficient trigger, as it only exists post-network configuration, and will exist for any defined network configuration.

Here's a patch to only trigger vmware-networks-configuration.service if /etc/vmware/networking does not exist.

From f922f5a5051b87adcfed39588138b11903fdc98f Mon Sep 17 00:00:00 2001
From: Jared Baldridge <jrbaldridge@lbl.gov>
Date: Thu, 19 Dec 2019 14:09:27 -0800
Subject: [PATCH] adjust vmware-networks-configuraiton.service conditions

---
 vmware-networks-configuration.service | 7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

diff --git a/vmware-networks-configuration.service b/vmware-networks-configuration.service
index 779b01a..0d86867 100644
--- a/vmware-networks-configuration.service
+++ b/vmware-networks-configuration.service
@@ -1,11 +1,6 @@
 [Unit]
 Description=VMware Networks Configuration Generation
-ConditionPathExists=|!/etc/vmware/networking
-ConditionPathExists=|!/etc/vmware/vmnet1/dhcpd/dhcpd.conf
-ConditionPathExists=|!/etc/vmware/vmnet1/dhcpd/dhcpd.leases
-ConditionPathExists=|!/etc/vmware/vmnet8/dhcpd/dhcpd.conf
-ConditionPathExists=|!/etc/vmware/vmnet8/dhcpd/dhcpd.leases
-ConditionPathExists=|!/etc/vmware/vmnet8/nat/nat.conf
+ConditionPathExists=!/etc/vmware/networking

 [Service]
 UMask=0077
-- 
2.24.1

tech101usa commented on 2019-12-11 06:33 (UTC)

Thank you so much for your efforts to maintain this package. Having VMware Workstation on Arch and its derivatives via the AUR is so extremely helpful.

I'm actually on Manjaro and recently ran a system-wide upgrade that included a Kernel update from 5.3 to 5.4. As expected, this broke my Workstation 15 install. However, removing and reinstalling following the direction provided solved the issue with one exception. When I reinstalled, I didn't realize I still had only the Linux53 headers installed and not the Linux54 headers. The vmmon module wasn't built during the install as a result.

Uninstalling Workstation 15, removing the Linux53 headers (I'm not expecting to revert to the 5.3 kernel anytime soon), installing the Linux54 headers, and then reinstalling Workstation 15 from the AUR solved the issues.

Very grateful for your work in making this available.

THANK YOU!!!

jihem commented on 2019-11-16 20:38 (UTC)

@redsolja: I've fixed the PKGBUILD.

@majed17: I don't have this kind of problem. Maybe this is a bug with the Cinnamon screen locker. You should try with another desktop environment or another screen locker before trying another distribution.

redsolja commented on 2019-11-15 21:28 (UTC)

Hello, after the latest update to VMware-Workstation-Full-15.5.1-15018445.x86_64.bundle, vmware was silently failing.

Logs under /tmp showed that there was a GLIB error complaining about two EULA files:

2019-11-16T23:13:10.971+02:00| vmui| W115: Unhandled Glib exception: class 'N4Glib9FileErrorE', details 'Failed to open file “/usr/share/doc/vmware-workstation/EULA”: No such file or directory'

and

2019-11-16T23:21:31.815+02:00| vmui| W115: Unhandled Glib exception: class 'N4Glib9FileErrorE', details 'Failed to open file “/usr/lib/vmware-ovftool/vmware.eula”: No such file or directory'

I fixed this with:

cd /usr/share/doc/
mkdir vmware-workstation
cd vwmare-workstation
cp /home/USERNAME/aur/vmware-workstation/pkg/vmware-workstation/usr/share/licenses/vmware-workstation/VMware\ Workstation\ -\ EULA.txt EULA

cd /usr/lib/vmware-ovftool/
cp /usr/share/licenses/vmware-workstation/VMware\ OVF\ Tool\ -\ EULA.txt vmware.eula

majed17 commented on 2019-11-15 11:02 (UTC)

does anybody have win 10 virtual machines on the new workstation version? on linux mint it keeps crashing when i lock the screen! does that happen on arch?

jihem commented on 2019-11-14 21:50 (UTC)

Thanks for your feedback! Yes, this solution exists but is not perfect because I'm afraid that Player refuses to start after 30 days. I'm interested if someone could tell me what happen after this delay.

However, even if Player refuses to start, it's probably possible to ask a new trial after removing the file /etc/vmware/license-ws-150-e1-201804

josete commented on 2019-11-14 19:43 (UTC) (edited on 2019-11-14 19:44 (UTC) by josete)

I can confirm the solution. You only have to run vmware just one time, instead of vmplayer. After that, you won't see again the prompt.

GitSquared commented on 2019-11-14 19:38 (UTC) (edited on 2019-11-14 19:42 (UTC) by GitSquared)

@jihem I "solved" this problem by launching VMware Workstation (the paid version) and selecting a 30-day trial. This made the license prompt disappear from VMware Player and everything works as before.

I haven't done this more than 30 days ago, though, so perhaps once the trial is over the prompts will reappear. I hope not!..

Edit: It seems this has already been talked about down below. However, I don't see any license countdown in Player.

jihem commented on 2019-11-14 19:25 (UTC)

I've updated the package. Unfortunately the problem with VMware Player license is still present. It seems this update mostly includes security fixes.

strayArch commented on 2019-11-14 17:53 (UTC)

I created a PKGBUILD for 15.5.1 available at https://stro.nz/public/vmware-workstation-PKGBUILD.txt

the git diff of the PKGBUILD

diff --git a/PKGBUILD b/PKGBUILD
index 8dc52ec..7275600 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -21,10 +21,10 @@

 #PKGEXT=.pkg.tar
 pkgname=vmware-workstation
-pkgver=15.5.0
-_buildver=14665864
+pkgver=15.5.1
+_buildver=15018445
 _pkgver=${pkgver}_${_buildver}
-pkgrel=2
+pkgrel=1
 pkgdesc='The industry standard for running multiple operating systems as virtual machines on a single Linux PC.'
 arch=(x86_64)
 url='https://www.vmware.com/products/workstation-for-linux.html'
@@ -98,34 +98,28 @@ source=(
   'vmmon.patch'
   'vmnet.patch'
 )
-sha256sums=(
-  'b557b4dcebefb51466da5b33dc51549537b0d381864b6155c3a48a66801a8597'
-
-  '12e7b16abf8d7e858532edabb8868919c678063c566a6535855b194aac72d55e'
-  'da1698bf4e73ae466c1c7fc93891eba4b9c4581856649635e6532275dbfea141'
-  'ce3b1a82d9ed023b7591168bd49b218040ef70d1752a07792b0af6ac15a68453'
-  'd50aa0a3fe94025178965d988e18d41eb60aa1ce2b28ee6e3ca15edeabfa2ca7'
-  '8e4d08668a66be79a900521792b39c16a026cc90659241edee80b64e701bfbcd'
-  'b94959a11b28e51b541321be0588190eb10825e9ff55cbd16eb01483a839a69f'
-
-  'ce1fd2916c7dde0ed0fa3158c0e3055bbc84f6c397464e3a10776aeb35d9828f'
-  '434cd4aa440d36b75ee20e0b588aaad874bb0d796173990bc4046667c66f5099'
-  'cceaec1837fce1e03fa76cf0bf39eb01b19f4ffa45eb986d62221282682deb82'
-  '3c802523606184a5e8ebbe931d9c6c70d83ff8c6833b9f48aa264f0bd5a18a88'
-  'ad522a8cbc6103134ce5e677a01b503cd21875cbceb37bd13fd870ebd9ad0e6d'
-
-  'f9440479f3ae5ad0a39bba3150276627878bf83d6879444fb327c53a1dbb5a4d'
-  '42594b60085d0bbef01ab07b9f8b0d18640001107ce61cc0ddf02d0ab415140f'
-  'e4c2e97acf07c52de570dd4333d67acfb593db719937a563c6075ab773dcce33'
-  'e3812b78158672c7d96b6a58877681462f3fbdfe99a948b32c80c755c8682450'
-  'c0a5aea785db06921fb350d36d5e0fd9a14f5eee0c835686ec6fea1af8c92245'
-  'd7a9fbf39a0345ae2f14f7f389f30b1110f605d187e0c241e99bbb18993c250d'
-
-  '05e26d8b21d190ebabb7f693998114d9d5991d9dfb71acb4d990293a65b6b487'
-  '6ce902b1dab8fc69be253abd8e79017011985eca850ff7acc7282f9ab668e35d'
-  '1060b5d45caeda5119b220fab4e1ece398af34d75131139a5dc6f74ee06672c3'
-  '22d1f23c272dd2f7d4644dfffe051503cf62311886f67d57de3b7502615ceec1'
-)
+sha256sums=('490f8fe8d874c27601c155c1b2c0055ad0d4f14feb32fa9f18643659a147d3c6'
+            '12e7b16abf8d7e858532edabb8868919c678063c566a6535855b194aac72d55e'
+            'da1698bf4e73ae466c1c7fc93891eba4b9c4581856649635e6532275dbfea141'
+            'ce3b1a82d9ed023b7591168bd49b218040ef70d1752a07792b0af6ac15a68453'
+            'd50aa0a3fe94025178965d988e18d41eb60aa1ce2b28ee6e3ca15edeabfa2ca7'
+            '8e4d08668a66be79a900521792b39c16a026cc90659241edee80b64e701bfbcd'
+            'b94959a11b28e51b541321be0588190eb10825e9ff55cbd16eb01483a839a69f'
+            'ce1fd2916c7dde0ed0fa3158c0e3055bbc84f6c397464e3a10776aeb35d9828f'
+            '434cd4aa440d36b75ee20e0b588aaad874bb0d796173990bc4046667c66f5099'
+            'cceaec1837fce1e03fa76cf0bf39eb01b19f4ffa45eb986d62221282682deb82'
+            '3c802523606184a5e8ebbe931d9c6c70d83ff8c6833b9f48aa264f0bd5a18a88'
+            'ad522a8cbc6103134ce5e677a01b503cd21875cbceb37bd13fd870ebd9ad0e6d'
+            'f9440479f3ae5ad0a39bba3150276627878bf83d6879444fb327c53a1dbb5a4d'
+            '42594b60085d0bbef01ab07b9f8b0d18640001107ce61cc0ddf02d0ab415140f'
+            'e4c2e97acf07c52de570dd4333d67acfb593db719937a563c6075ab773dcce33'
+            'e3812b78158672c7d96b6a58877681462f3fbdfe99a948b32c80c755c8682450'
+            'c0a5aea785db06921fb350d36d5e0fd9a14f5eee0c835686ec6fea1af8c92245'
+            'd7a9fbf39a0345ae2f14f7f389f30b1110f605d187e0c241e99bbb18993c250d'
+            '05e26d8b21d190ebabb7f693998114d9d5991d9dfb71acb4d990293a65b6b487'
+            '6ce902b1dab8fc69be253abd8e79017011985eca850ff7acc7282f9ab668e35d'
+            '1060b5d45caeda5119b220fab4e1ece398af34d75131139a5dc6f74ee06672c3'
+            '22d1f23c272dd2f7d4644dfffe051503cf62311886f67d57de3b7502615ceec1')
 options=(!strip emptydirs)

 if [ -z "$_remove_vmware_keymaps_dependency" ]; then

pepper-jk commented on 2019-10-25 23:21 (UTC) (edited on 2019-10-28 11:33 (UTC) by pepper-jk)

I'm having the same issue, @dani.

Anyone got a solution yet?

EDIT:

Well I tried to downgraded using the older versions und build numbers for vmware workstations and fusions, as well as the sha256 hashes, from this commit without modifying the pkgbuild any further.

This should prevent the 5.4 patch from being reverted.

However this did not work and I made a full downgrade. :/

GitSquared commented on 2019-10-09 13:09 (UTC)

You shouldn't have the 30-day trial license unless you ask it after starting Workstation. Remove the file /etc/vmware/license-ws-150-e1-201804 and restart sudo vmplayer. The 30-day message should disappear.

This file does not exist on my system. This bug doesn't prevent vmplayer from starting correctly, but having to go through the licensing dialog each time is a pain in the ***.

dani commented on 2019-10-08 09:25 (UTC)

How to switch tty for host?

I have tried the "Ctrl+Alt+Space, Ctrl+Alt+Fx" trick, which does not work for me.

hogar1977 commented on 2019-10-07 22:42 (UTC)

@jihem

I'm getting validity check error on VMware-Workstation-Full-15.5.0-14665864.x86_64.bundle with the latest update.

Does anyone get the same?

jihem commented on 2019-09-30 17:55 (UTC) (edited on 2019-09-30 17:58 (UTC) by jihem)

@dani:

  • I have installed Vmware Player on Windows: Player starts without asking a license.
  • I have installed VMware Player (with the official method) on Arch, Fedora and Debian (the two last distros are officially supported): Player ask a license.

I think there is a bug in the Linux version. I'm searching a workaround but I don't have any idea.

You shouldn't have the 30-day trial license unless you ask it after starting Workstation. Remove the file /etc/vmware/license-ws-150-e1-201804 and restart sudo vmplayer. The 30-day message should disappear.

In the worst case, you can downgrade to 15.1.0. It should work at least until Linux 5.4 release. I hope VMware will release a fix before.

dani commented on 2019-09-30 07:11 (UTC) (edited on 2019-09-30 07:17 (UTC) by dani)

@jihem

Polkit was installed and the service was running.

I tried sudo vmplayer to bypass the polkit problem and it works.

Now I am in the 30-day trial. Even in Player, there is a count-down of the evaluation license.

I am afraid I won't even be able to use Player when it expires.

According to VMware website, Player is still free of charge for personal users. Do you think this is a bug?

sizzen commented on 2019-09-28 03:23 (UTC) (edited on 2019-09-28 04:26 (UTC) by sizzen)

I am on kernel 5.3.1 and getting the error "Could not open /dev/vmmon: No such file or directory. Please make sure that the kernel module `vmmon' is loaded."

I attempted to reload the kernel modules but get this error "modprobe: WARNING: Module vmmon not found in directory /lib/modules/5.3.1-arch1-1-ARCH"

Is this kernel not currently supported?

Any help would be greatly appreciated.

Edit: I was on workstation 15.0.1 upgraded to most recent version and it worked.

AK4EVA commented on 2019-09-25 18:11 (UTC) (edited on 2019-09-25 18:12 (UTC) by AK4EVA)

If VMWare fails to load after installing 15.5.0 try editing /etc/vmware/config and append this at the end (use sudo/root):

acceptOVFEULA = "yes"

acceptEULA = "yes"

After this save, and reboot, works flawlessly! Thank you @jihem & @strayarch

jihem commented on 2019-09-25 18:04 (UTC)

@dani: maybe you don't have polkit service enabled on startup? In that case you should install polkit package and enable polkit.service. But I'm not sure it is sufficient, I don't really know how polkit works.

I'm surprised that no one talk about this problem on VMware community forum.

strayArch commented on 2019-09-24 14:52 (UTC)

Installed 15.5.0, followed @jihem instructions for /etc/vmware/config, rebooted, and starts flawlessly.

dani commented on 2019-09-24 11:22 (UTC) (edited on 2019-09-24 11:43 (UTC) by dani)

@jihem, thank you for replying. But it still does not really work for me.

"I want to try VMware Workstation 15 for 30 days." --> "Finish" --> (no response)

Meanwhile in the console I was prompted to enter the root password.

==== AUTHENTICATING FOR org.freedesktop.policykit.exec ====
Authentication is needed to run `/usr/lib/vmware/bin/vmware-setup-helper' as the super user
Authenticating as: root
Password: 

After password entered, it responded as follows.

polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
==== AUTHENTICATION FAILED ====
Error executing command as another user: Not authorized

This incident has been reported.

jihem commented on 2019-09-23 19:33 (UTC)

@dani: I have the same problem if I remove my Workstation license file. Same behaviour with a manual installation on Arch Linux or Fedora. I think it's a bug, you can use VMware Player freely if you select "I want to try VMware Workstation 15 for 30 days." on each startup.

jihem commented on 2019-09-23 16:56 (UTC) (edited on 2019-09-23 16:57 (UTC) by jihem)

Sorry guys for the problems!

Firstly, for people who want to temporarily downgrade:

git clone https://aur.archlinux.org/vmware-workstation.git && cd vmware-workstation && git checkout 82bfe4ee4a7f4f37998069af9694a8013964885a && makepkg -si

Secondly, if vmware or vmplayer crashes, add the following lines at the end of the /etc/vmware/config file:

acceptOVFEULA = "yes"
acceptEULA = "yes"

NekoBuster commented on 2019-09-23 13:57 (UTC) (edited on 2019-09-23 14:00 (UTC) by NekoBuster)

15.5.0 vmware workstation crashes with no output

vmplayer crashes with signal 6

TheSaint commented on 2019-09-23 06:38 (UTC) (edited on 2019-09-23 14:49 (UTC) by TheSaint)

Upgrade to 15.5.0 creates a problem

vmplayer| I125+ Unexpected signal: 6. And it crash. which I can't identify the correct cause. Perhaps the /etc/vmware.config is not yet updated. I don't know what I should keep from the old one.

How to downgrade to the previous version ?

SOLVED!!!! removed all files/references related to vmware and reinstall the new package.

dani commented on 2019-09-23 03:55 (UTC) (edited on 2019-09-23 04:07 (UTC) by dani)

I was prompted to enter a license key when trying to run vmplayer after upgrading to 15.5. But VMware Player is supposed to be free of charge, right?

jihem commented on 2019-09-22 22:10 (UTC)

I did nothing, but it seems that VMware improved a lot the startup time for this upgrade.

CaskAle13c commented on 2019-09-22 20:44 (UTC)

Wow, not sure what you did, but my startup time for workstation has gone from 10 seconds to 2 seconds on my laptop. AWESOME!!!

NekoBuster commented on 2019-09-22 13:19 (UTC)

Can you add StartupWMClass to the desktop app so we don't need to mannually add it every time after update?

NekoBuster commented on 2019-08-27 08:04 (UTC) (edited on 2019-08-28 01:13 (UTC) by NekoBuster)

I deleted everything related to vmnet1 and vmnet8 in the config file and then it works.

In the previous situation:

systemctl restart service - settings are not reset

reboot machine - settings get reset

use your provided command to regenerate the config - the situation persists

jihem commented on 2019-08-26 19:23 (UTC)

Atilir and NekoBuster: I don't have this problem on my computer. Maybe it only appears with a specific configuration. Can you show me your /etc/vmware/networking file?

If you restart the service (systemctl restart vmware-networks.service), do you have a reset of your configuration?

If you manually reset your configuration with the command "vmware-networks --stop; vmware-networks --postinstall vmware-player,0,1; vmware-networks --start" and reconfigure it, do you still have the problem when you reboot your computer?

NekoBuster commented on 2019-08-26 09:51 (UTC)

@Atilir: same here, thinking it may be a problem introduced in the most recent update, any solutions?

Atilir commented on 2019-08-14 06:58 (UTC)

When I reboot, my virtual network editor configuration reset (if I add a vmnet, after a reboot of my computer the vmnet is gone) and my file /etc/vmware/networking goes to default again even if I enter those parameters by hand.

jihem commented on 2019-08-13 20:41 (UTC)

@buzo : if you can build/install the package and start the program, I think you can ignore this warning.

buzo commented on 2019-08-13 17:09 (UTC)

I get the following warning when building in a clean chroot. Is there a dependency missing, or should I just ignore that?

==> Starting prepare()...
Extracting VMware Installer...done.
[AppLoader] Use shipped Linux kernel AIO access library.
An up-to-date "libaio" or "libaio1" package from your system is preferred.

jihem commented on 2019-08-13 16:15 (UTC)

@dvzrv: thanks for your suggestion. I've updated the package.

dvzrv commented on 2019-08-13 13:11 (UTC)

@jihem: The optional sources are not unique. Please include the version to ensure their uniqueness, as they otherwise don't get updated on version increment!

cyrinux commented on 2019-05-17 08:32 (UTC)

Hi,

Macosx part seems broken :)

com.vmware.fusion.tools.darwinPre15.zip.tar ... FAILED com.vmware.fusion.tools.darwin.zip.tar ... FAILED

strayArch commented on 2019-05-16 17:47 (UTC) (edited on 2019-05-16 19:17 (UTC) by strayArch)

15.1.0 requires the patches to be updated (version increment and updpkgsums does not build). Not 100% my patch is correct http://stro.nz/public/PKGBUILD.patch http://stro.nz/public/modules.patch But, build, rmmod vmw_vmci vmmon && modprobe -a vmw_vmci vmmon, start vmware. Worked for me. Hope that helps.

douggle commented on 2019-05-16 00:33 (UTC)

as of May 14th, this package is out of date, the new version is 15.1.0 which I assume has fixes for the updated 5.1.2 kernel.

lawndoc commented on 2019-05-08 05:04 (UTC) (edited on 2019-05-08 05:04 (UTC) by lawndoc)

I get an error when trying to start workstation (installation was successful):

Segmentation fault (core dumped)

I am unable to start workstation through gui (silent failure) nor cli (via 'vmware' command). I believe it's stemming from vmware-modconfig which also gives the segfault error.

FirstAirBender commented on 2019-05-07 20:04 (UTC)

Remember to install linux-headers so that the kernel modules can be compiled against it. It is listed as an optional dependency and therefore is not required to be installed

wrexthor commented on 2019-04-13 16:46 (UTC) (edited on 2019-04-13 17:15 (UTC) by wrexthor)

EDIT In case someone else have the same problem, disable firejail with sudo firecfg --clean Install and then re-enable firejail, solved it for me.

I get an error when trying to install. Been looking for an answer all over but not managed to find any solution yet, any ideas?

==> Patching vmmon module for DKMS ERROR: ld.so: object 'libfakeroot.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. /usr/bin/patch: **** Can't change to directory /var/tmp/pamac-build-boss/vmware-workstation/pkg/vmware-workstation/usr/src/vmware-workstation-15.0.4_12990004/vmmon-only : No such file or directory ==> ERROR: A failure occurred in package(). Aborting...

GiRa commented on 2019-03-28 10:29 (UTC)

jihem: thanks for the reply. I understand your situation.

I can patch the .SRCINFO and PKGBUILD files at the update. No big deal. Thanks again for explaining.

buzo commented on 2019-03-27 17:00 (UTC)

jihem: I have just installed/updated vmware-keymaps and vmware-workstation with a single pacman command – without any special command line options. You will only get problems if you are trying to do that using two steps.

zangoku commented on 2019-03-18 01:15 (UTC)

@jhem thank you that worked!

jihem commented on 2019-03-17 08:24 (UTC) (edited on 2019-03-17 08:25 (UTC) by jihem)

zangoku: try to add a backslash before the character *

zangoku commented on 2019-03-17 07:25 (UTC)

@jhem, I must use the slash or else I get:

zsh: no matches found: usr/lib/vmware/xkeymap/*

jihem commented on 2019-03-16 10:00 (UTC)

zangoku: just remove the first slash on the keymap filenames.

GiRa: Since I am the maintainer of this package, I had some complaints of people who use vmware-workstation and vmware-horizon-client packages because these packages have common files and on each update, they need to use --force/--overwrite option to install the updated package. With the vmware-horizon-client maintainer and vmware-keymaps author, we had a discussion by mail and the better solution we found is to put the common files in a new package.

I understand your point of view but I don't want to come back to this decision. But, just to reassure you, these keymap files haven't been changed since at least VMware Workstation 11, so this package should be updated rarely or never. Also, you could suggest to vmware-keymaps maintainer to change the PKGBUILD to extract keymap files from an official VMware bundle, instead of taking them from a private repository.

GiRa commented on 2019-03-15 14:05 (UTC) (edited on 2019-03-15 14:07 (UTC) by GiRa)

I may say that adding an external repository for they keymaps makes updating more complex.

I always review what changed at each new release of an AUR package. Basically it's a full code review at the first installation and then incremental ones which usually take less than a minute.

Having an external, non-official, third-party repo makes the updates more complex. A conscious user is forced to clone the external repo manually and review it at every update.

Was it a big amount of work to maintain the keymaps? You already do a lot, so I am not pretending to change your ways. I simply want to understand :)

EDIT: I see in the gitlog that this is needed for compatibility with vmware-horizon. Is there any other feasible alternative?

zangoku commented on 2019-03-14 21:47 (UTC)

@jhem

I am getting these errors when trying to install keymaps:

error: could not open file /usr/lib/vmware/xkeymap/be104: Unrecognized archive format error: '/usr/lib/vmware/xkeymap/be104': cannot open package file

jihem commented on 2019-03-13 10:50 (UTC)

zangoku: build the package vmware-keymaps as usual, but without the -i option of makepkg. Then, install it with the following line:

pacman -U --asdeps --overwrite usr/lib/vmware/xkeymap/* vmware-keymaps-1.0-1-any.pkg.tar.xz

Then, update vmware-workstation.

mpei commented on 2019-03-13 03:41 (UTC)

@jihem: I just tried again at current state of arch, loaded the kernel modules and it works perfectly. Thank you!

zangoku commented on 2019-03-13 02:39 (UTC)

How can I use the overwrite option when install a package from the AUR ? I usually use git clone then makepkg.

mpei commented on 2019-03-13 02:27 (UTC)

@jihem: env VMWARE_USE_SHIPPED_LIBS=1 vmware is what I had tried tooo but it did not make a difference. I rolled back one week and run kernel 4.20 and installed vmware with the graphical installer and that works. I will try again in a few days to update to current state and then will try again to use the package.

jihem commented on 2019-03-12 20:25 (UTC)

mpei: it's probably a conflict between some libraries. Can you try to start VMware with the following command line:

env VMWARE_USE_SHIPPED_LIBS=1 vmware

viljeml: of course, you can also use the new --overwrite option. I updated my comment.

viljeml commented on 2019-03-12 10:42 (UTC)

solution to install vmware-keymaps with --force option is not possible because --force is deprecated

mpei commented on 2019-03-11 21:51 (UTC)

After installing with latest updates every vmware binary segfaults, e.g.:

Running: vmware Results in: 11286 segmentation fault (core dumped) vmware

BackTrace: coredumpctl info 11286
PID: 11286 (vmware) UID: 1000 (mpe) GID: 1000 (mpe) Signal: 11 (SEGV) Timestamp: Mon 2019-03-11 17:49:36 EDT (40s ago) Command Line: /usr/lib/vmware/bin/vmware Executable: /usr/lib/vmware/bin/appLoader Control Group: /user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service Unit: user@1000.service User Unit: gnome-terminal-server.service Slice: user-1000.slice Owner UID: 1000 (mpe) Boot ID: 5db5997e4a644fb8aa4330565c445902 Machine ID: 4b9ed5b3330f4af5b84e139a66a893d4 Hostname: qlmpexps Storage: /var/lib/systemd/coredump/core.vmware.1000.5db5997e4a644fb8aa4330565c445902.11286.1552340976000000.lz4 Message: Process 11286 (vmware) of user 1000 dumped core.

            Stack trace of thread 11286:
            #0  0x00007fba2f9b4715 __strlen_avx2 (libc.so.6)
            #1  0x000055dab40acb92 n/a (appLoader)
            #2  0x000055dab40af1b7 n/a (appLoader)
            #3  0x000055dab40aba5a main (appLoader)
            #4  0x00007fba2f879223 __libc_start_main (libc.so.6)
            #5  0x000055dab40ac311 n/a (appLoader)

Any ideas?

solatis commented on 2019-03-10 19:20 (UTC)

Thanks @jihem, that worked like a charm!

jihem commented on 2019-03-10 18:37 (UTC) (edited on 2019-03-17 11:58 (UTC) by jihem)

When you update to version 15.0.2-4, you should see an error telling that some files already exist. This is normal, the reason is that some files previously included in this package are now provided by another package (vmware-keymaps) which is now a dependency.

One solution is to install vmware-keymaps with the option --overwrite usr/lib/vmware/xkeymap/\* before updating vmware-workstation. Another solution is to uninstall your current version of vmware-workstation, then build and install the new version (with vmware-keymaps dependency).

sizzen commented on 2019-03-07 18:30 (UTC)

jihem: That worked! Thank you so much for everyones help!

sizzen commented on 2019-03-07 18:12 (UTC)

jihem: I do not believe I am! Installing now. Out of curiosity how did you see that commit? I am fairly new to Arch from MacOS. About 3 months now on my laptop and I love it more than any other OS but Im still working out some kinks here and there. I really appreciate the community support.

jihem commented on 2019-03-07 18:01 (UTC)

sizzen: Are you sure you use the latest version of this package: 15.0.2-3? The commit d17bd2c83158 includes some patches (taken from the repo you quote in your previous post) that make the package compatible with Linux 5.0.

If you are sure you use the latest version, can you show me the make.log file generated by DKMS?

sizzen commented on 2019-03-07 17:50 (UTC)

majed17: When I run that I get this error modprobe: WARNING: Module vmmon not found in directory /lib/modules/5.0.0-arch1-1-ARCH.

Also more background, when install linux-headers via pacman I get this error dkms install vmware-workstation/15.0.2_10952284 -k 5.0.0-arch1-1-ARCH Error! Bad return status for module build on kernel: 5.0.0-arch1-1-ARCH (x86_64) Consult /var/lib/dkms/vmware-workstation/15.0.2_10952284/build/make.log for more information.

So I'm not really sure whats going on.

I have also tried going to this git repo https://github.com/mkubecek/vmware-host-modules and downloading the modules for workstation 15.0.2 but I get an error saying that vmmon doesnt exist which is odd. Specifically there error listed below

make -C vmmon-only make[1]: vmmon-only: No such file or directory. Stop. make: [Makefile:21: vmmon-only] Error 2

majed17 commented on 2019-03-07 11:22 (UTC)

you need to run modprobe -a vmw_vmci vmmon and magic, it will work :)

sizzen commented on 2019-03-07 03:43 (UTC) (edited on 2019-03-07 03:47 (UTC) by sizzen)

I recently upgraded to Linux Kernel 5.0.0. Does the latest package have support for this kernel? I mistakenly updated and now my virtual machines are not starting with the error Could not open /dev/vmmon: No such file or directory. I do not see the module in the kernel modules either. Any help would be greatly appreciated.

level39 commented on 2019-02-14 10:06 (UTC) (edited on 2019-02-14 14:31 (UTC) by level39)

--EDIT--

Fixed after a system upgrade: pacman -Syu

I get the following error during installation:

Unable to install module vmware-workstation/15.0.2_10952284 for kernel 4.20.7-arch1-1-ARCH: Missing kernel modules tree.

I have 4.20.7-arch1-1-ARCH under /usr/lib/modules and have created a symbolic link to it in /usr/src.

Inside /usr/lib/modules/4.20.7-arch1-1-ARCH there's only build directory which I'm pretty sure means I have to build it but if I run make inside /build, it returns with:

Do not try to update included dependency files

scripts/Makefile.build:42: arch/x86/entry/syscalls/Makefile: No such file or directory make[1]: No rule to make target 'arch/x86/entry/syscalls/Makefile'. Stop. make: [arch/x86/Makefile:233: archheaders] Error 2

Any help would be appreciated. Thanks

gbr commented on 2019-02-03 17:14 (UTC)

Is anyone else having issues with USB 3.0 compatibility on Windows 10? I've been having this really annoying mouse cursor lag and beeping on my freshly installed Windows 10 guest, so I googled the symptoms and found this old reddit thread:

https://www.reddit.com/r/Windows10/comments/48pae4/random_mouse_lagging_and_beeping/

The symptoms are similar (but not the exact same), but that bug was fixed a long time ago, and I'm on build 1803 already. Then I tried setting the USB compatibility to 2.0 in the VM's settings, and these annoying issues were gone.

I don't know what causes this, some people were saying it's because of a slow CPU, but mine isn't slow, it's an i5 3570k. I just wonder if it's just me who's experiencing it. Can someone with a Windows 10 guest try to reproduce it? Thanks

jihem commented on 2019-02-02 22:55 (UTC)

fredweb: yes, it is possible but clearly not recommended because something could be broken in the future (for example, the program won't be compatible with Linux 5.0 when it will be released).

In the git repository of the package, you have to find the commit number corresponding to the version you want (40ba3a8a7995 for VMware 15.0.0) and build with the following code:

git clone https://aur.archlinux.org/vmware-workstation.git
cd vmware-workstation
git checkout 40ba3a8a7995501bc29a0529e40832ceaeae6aaa
makepkg -si

After that, to prevent updates, add IgnorePkg=vmware-workstation in /etc/pacman.conf.

fredweb commented on 2019-02-02 19:16 (UTC) (edited on 2019-02-02 19:17 (UTC) by fredweb)

Hello, is possible to install an old version of VMware Workstation, like 15.0.0 for example?

Thanks in advance.

PS. I am using Manjaro 18.0.2

vay3t commented on 2018-12-07 14:04 (UTC) (edited on 2018-12-07 14:19 (UTC) by vay3t)

i have this problem

$ sudo systemctl start vmware-networks
Job for vmware-networks.service failed because the control process exited with error code.
See "systemctl status vmware-networks.service" and "journalctl -xe" for details.
$ uname -a
Linux 4.19.4-arch1-1-ARCH #1 SMP PREEMPT Fri Nov 23 09:06:58 UTC 2018 x86_64 GNU/Linux

i have installed linux and linux-headers

logs:

dic 07 11:16:08 hydraStation sudo[3779]:    vay3t : TTY=pts/2 ; PWD=/home/vay3t ; USER=root ; COMMAND=/usr/bin/systemctl start vmware-networks
dic 07 11:16:08 hydraStation sudo[3779]: pam_unix(sudo:session): session opened for user root by (uid=0)
dic 07 11:16:08 hydraStation systemd[1]: Starting VMware Networks...
-- Subject: Unit vmware-networks.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit vmware-networks.service has begun starting up.
dic 07 11:16:08 hydraStation vmnetBridge[3785]: Bridge process created.
dic 07 11:16:08 hydraStation vmnetBridge[3785]: RTM_NEWLINK: name:eth0 index:2 flags:0x00001002
dic 07 11:16:08 hydraStation vmnetBridge[3785]: RTM_NEWLINK: name:wlan0 index:3 flags:0x00011043
dic 07 11:16:08 hydraStation vmnetBridge[3785]: Adding interface wlan0 index:3
dic 07 11:16:08 hydraStation vmnetBridge[3785]: Started bridge wlan0 to virtual network 0.
dic 07 11:16:08 hydraStation vmnetBridge[3785]: RTM_NEWROUTE: index:3
dic 07 11:16:08 hydraStation vmware-networks[3783]: Subnet on vmnet8 is no longer available for usage, please run the network editor to reconfigure different subnet
dic 07 11:16:09 hydraStation systemd-udevd[3796]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
dic 07 11:16:09 hydraStation vmware-networks[3783]: Failed to start some/all services
dic 07 11:16:09 hydraStation vmware-networks[3783]: Started Bridge networking on vmnet0
dic 07 11:16:09 hydraStation vmware-networks[3783]: Enabled hostonly virtual adapter on vmnet1
dic 07 11:16:09 hydraStation vmware-networks[3783]: Started DHCP service on vmnet1
dic 07 11:16:09 hydraStation systemd[1]: vmware-networks.service: Control process exited, code=exited status=1
dic 07 11:16:09 hydraStation vmnetBridge[3785]: Stopped bridge wlan0 to virtual network 0.
dic 07 11:16:09 hydraStation vmnetBridge[3785]: Bridge process exiting.
dic 07 11:16:09 hydraStation systemd[1]: vmware-networks.service: Failed with result 'exit-code'.
dic 07 11:16:09 hydraStation systemd[1]: Failed to start VMware Networks.
-- Subject: Unit vmware-networks.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit vmware-networks.service has failed.
-- 
-- The result is failed.
dic 07 11:16:09 hydraStation audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=vmware-networks comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
dic 07 11:16:09 hydraStation kernel: audit: type=1130 audit(1544192169.278:64): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=vmware-networks comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
dic 07 11:16:09 hydraStation sudo[3779]: pam_unix(sudo:session): session closed for user root
dic 07 11:16:09 hydraStation systemd[1]: vmware-networks.service: Service RestartSec=100ms expired, scheduling restart.
dic 07 11:16:09 hydraStation systemd[1]: vmware-networks.service: Scheduled restart job, restart counter is at 1.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Automatic restarting of the unit vmware-networks.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
dic 07 11:16:09 hydraStation systemd[1]: Stopped VMware Networks.
-- Subject: Unit vmware-networks.service has finished shutting down
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit vmware-networks.service has finished shutting down.
dic 07 11:16:09 hydraStation audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=vmware-networks comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
dic 07 11:16:09 hydraStation audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=vmware-networks comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
dic 07 11:16:09 hydraStation systemd[1]: Starting VMware Networks...
-- Subject: Unit vmware-networks.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit vmware-networks.service has begun starting up.
dic 07 11:16:09 hydraStation kernel: audit: type=1130 audit(1544192169.568:65): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=vmware-networks comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
dic 07 11:16:09 hydraStation kernel: audit: type=1131 audit(1544192169.568:66): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=vmware-networks comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
dic 07 11:16:09 hydraStation vmnetBridge[3807]: Bridge process created.
dic 07 11:16:09 hydraStation vmnetBridge[3807]: RTM_NEWLINK: name:eth0 index:2 flags:0x00001002
dic 07 11:16:09 hydraStation vmnetBridge[3807]: RTM_NEWLINK: name:wlan0 index:3 flags:0x00011043
dic 07 11:16:09 hydraStation vmnetBridge[3807]: Adding interface wlan0 index:3
dic 07 11:16:09 hydraStation vmnetBridge[3807]: Started bridge wlan0 to virtual network 0.
dic 07 11:16:09 hydraStation vmnetBridge[3807]: RTM_NEWROUTE: index:3
dic 07 11:16:10 hydraStation vmware-networks[3805]: Subnet on vmnet8 is no longer available for usage, please run the network editor to reconfigure different subnet
dic 07 11:16:10 hydraStation systemd-udevd[3818]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
dic 07 11:16:10 hydraStation vmware-networks[3805]: Failed to start some/all services
dic 07 11:16:10 hydraStation vmware-networks[3805]: Started Bridge networking on vmnet0
dic 07 11:16:10 hydraStation vmware-networks[3805]: Enabled hostonly virtual adapter on vmnet1
dic 07 11:16:10 hydraStation vmware-networks[3805]: Started DHCP service on vmnet1
dic 07 11:16:10 hydraStation systemd[1]: vmware-networks.service: Control process exited, code=exited status=1
dic 07 11:16:10 hydraStation vmnetBridge[3807]: Stopped bridge wlan0 to virtual network 0.
dic 07 11:16:10 hydraStation vmnetBridge[3807]: Bridge process exiting.
dic 07 11:16:10 hydraStation systemd[1]: vmware-networks.service: Failed with result 'exit-code'.
dic 07 11:16:10 hydraStation systemd[1]: Failed to start VMware Networks.
-- Subject: Unit vmware-networks.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit vmware-networks.service has failed.
-- 
-- The result is failed.
dic 07 11:16:10 hydraStation audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=vmware-networks comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
dic 07 11:16:10 hydraStation kernel: audit: type=1130 audit(1544192170.621:67): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=vmware-networks comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
dic 07 11:16:10 hydraStation systemd[1]: vmware-networks.service: Service RestartSec=100ms expired, scheduling restart.
dic 07 11:16:10 hydraStation systemd[1]: vmware-networks.service: Scheduled restart job, restart counter is at 2.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Automatic restarting of the unit vmware-networks.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
dic 07 11:16:10 hydraStation systemd[1]: Stopped VMware Networks.
-- Subject: Unit vmware-networks.service has finished shutting down
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit vmware-networks.service has finished shutting down.
dic 07 11:16:10 hydraStation audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=vmware-networks comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
dic 07 11:16:10 hydraStation audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=vmware-networks comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
dic 07 11:16:10 hydraStation systemd[1]: Starting VMware Networks...
-- Subject: Unit vmware-networks.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit vmware-networks.service has begun starting up.
dic 07 11:16:10 hydraStation kernel: audit: type=1130 audit(1544192170.818:68): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=vmware-networks comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
dic 07 11:16:10 hydraStation kernel: audit: type=1131 audit(1544192170.818:69): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=vmware-networks comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
dic 07 11:16:10 hydraStation vmnetBridge[3830]: Bridge process created.
dic 07 11:16:10 hydraStation vmnetBridge[3830]: RTM_NEWLINK: name:eth0 index:2 flags:0x00001002
dic 07 11:16:10 hydraStation vmnetBridge[3830]: RTM_NEWLINK: name:wlan0 index:3 flags:0x00011043
dic 07 11:16:10 hydraStation vmnetBridge[3830]: Adding interface wlan0 index:3
dic 07 11:16:10 hydraStation vmnetBridge[3830]: Started bridge wlan0 to virtual network 0.
dic 07 11:16:10 hydraStation vmnetBridge[3830]: RTM_NEWROUTE: index:3
dic 07 11:16:11 hydraStation vmware-networks[3827]: Subnet on vmnet8 is no longer available for usage, please run the network editor to reconfigure different subnet
dic 07 11:16:11 hydraStation systemd-udevd[3841]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
dic 07 11:16:11 hydraStation vmware-networks[3827]: Failed to start some/all services
dic 07 11:16:11 hydraStation vmware-networks[3827]: Started Bridge networking on vmnet0
dic 07 11:16:11 hydraStation vmware-networks[3827]: Enabled hostonly virtual adapter on vmnet1
dic 07 11:16:11 hydraStation vmware-networks[3827]: Started DHCP service on vmnet1
dic 07 11:16:11 hydraStation systemd[1]: vmware-networks.service: Control process exited, code=exited status=1
dic 07 11:16:11 hydraStation vmnetBridge[3830]: Stopped bridge wlan0 to virtual network 0.
dic 07 11:16:11 hydraStation vmnetBridge[3830]: Bridge process exiting.
dic 07 11:16:11 hydraStation systemd[1]: vmware-networks.service: Failed with result 'exit-code'.
dic 07 11:16:11 hydraStation systemd[1]: Failed to start VMware Networks.
-- Subject: Unit vmware-networks.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit vmware-networks.service has failed.
-- 
-- The result is failed.
dic 07 11:16:11 hydraStation audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=vmware-networks comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
dic 07 11:16:11 hydraStation kernel: audit: type=1130 audit(1544192171.888:70): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=vmware-networks comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
dic 07 11:16:12 hydraStation systemd[1]: vmware-networks.service: Service RestartSec=100ms expired, scheduling restart.
dic 07 11:16:12 hydraStation systemd[1]: vmware-networks.service: Scheduled restart job, restart counter is at 3.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Automatic restarting of the unit vmware-networks.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
dic 07 11:16:12 hydraStation systemd[1]: Stopped VMware Networks.
-- Subject: Unit vmware-networks.service has finished shutting down
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit vmware-networks.service has finished shutting down.
dic 07 11:16:12 hydraStation audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=vmware-networks comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
dic 07 11:16:12 hydraStation audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=vmware-networks comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
dic 07 11:16:12 hydraStation systemd[1]: Starting VMware Networks...
-- Subject: Unit vmware-networks.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit vmware-networks.service has begun starting up.
dic 07 11:16:12 hydraStation kernel: audit: type=1130 audit(1544192172.068:71): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=vmware-networks comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
dic 07 11:16:12 hydraStation kernel: audit: type=1131 audit(1544192172.068:72): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=vmware-networks comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
dic 07 11:16:12 hydraStation vmnetBridge[3851]: Bridge process created.
dic 07 11:16:12 hydraStation vmnetBridge[3851]: RTM_NEWLINK: name:eth0 index:2 flags:0x00001002
dic 07 11:16:12 hydraStation vmnetBridge[3851]: RTM_NEWLINK: name:wlan0 index:3 flags:0x00011043
dic 07 11:16:12 hydraStation vmnetBridge[3851]: Adding interface wlan0 index:3
dic 07 11:16:12 hydraStation vmnetBridge[3851]: Started bridge wlan0 to virtual network 0.
dic 07 11:16:12 hydraStation vmnetBridge[3851]: RTM_NEWROUTE: index:3
dic 07 11:16:12 hydraStation vmware-networks[3849]: Subnet on vmnet8 is no longer available for usage, please run the network editor to reconfigure different subnet
dic 07 11:16:13 hydraStation systemd-udevd[3863]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
dic 07 11:16:13 hydraStation vmware-networks[3849]: Failed to start some/all services
dic 07 11:16:13 hydraStation vmware-networks[3849]: Started Bridge networking on vmnet0
dic 07 11:16:13 hydraStation vmware-networks[3849]: Enabled hostonly virtual adapter on vmnet1
dic 07 11:16:13 hydraStation vmware-networks[3849]: Started DHCP service on vmnet1
dic 07 11:16:13 hydraStation systemd[1]: vmware-networks.service: Control process exited, code=exited status=1
dic 07 11:16:13 hydraStation vmnetBridge[3851]: Stopped bridge wlan0 to virtual network 0.
dic 07 11:16:13 hydraStation vmnetBridge[3851]: Bridge process exiting.
dic 07 11:16:13 hydraStation systemd[1]: vmware-networks.service: Failed with result 'exit-code'.
dic 07 11:16:13 hydraStation systemd[1]: Failed to start VMware Networks.
-- Subject: Unit vmware-networks.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit vmware-networks.service has failed.
-- 
-- The result is failed.
dic 07 11:16:13 hydraStation audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=vmware-networks comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
dic 07 11:16:13 hydraStation kernel: audit: type=1130 audit(1544192173.138:73): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=vmware-networks comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'

friday commented on 2018-11-25 12:29 (UTC)

Just discovered the MacOS support easter egg, so I don't have to apply the patch manually after upgrading any more, if I just add the right variable to /etc/makepkg.conf. This is awesome. Thank you jihem!

phoeven commented on 2018-10-30 23:19 (UTC)

The issue got indeed fixed with the (re)installation of the linux-headers and (unfortunately) used the official bundle (I still received errors the "Missing kernel headers" when using yaourt): Name : linux316-headers Version : 3.16.59-1

Thanks for the help, guys!

MisterPresident commented on 2018-10-23 12:57 (UTC)

jihem: Thank you. Activating with the terminal worked perfectly.

MisterPresident commented on 2018-10-23 12:57 (UTC)

jihem: Thank you. Activating with the terminal worked perfectly.

jihem commented on 2018-10-21 13:29 (UTC)

beci: because some people don't use the default kernel and they need to install another package: for example linux-lts-headers for Linux LTS, linux-zen-headers for Linux Zen... The virtualbox-host-dkms package also put linux-headers as optional dependency.

If I try to install VMware on a vanilla Arch without kernel headers, I have a different message: "==> Unable to install module vmware-workstation/15.0.0_10134415 for kernel *: Missing kernel headers."

beci commented on 2018-10-21 12:10 (UTC) (edited on 2018-10-21 12:12 (UTC) by beci)

Why the linux-headers is optional? I got the same error for vmmon on vanilla arch install too. With kernel headers it's fine.

phoeven: try to (re)install the up to date kernel headers:

sudo pacman -S linux-headers

jihem commented on 2018-10-17 19:51 (UTC)

phoeven: I don't use Manjaro so my help is very limited. It seems that you use a real time kernel, maybe you should try with a standard kernel.

buzo: phoeven is failing to compile vmmon module, so he cannot load it.

buzo commented on 2018-10-17 19:47 (UTC)

You can find detailed information about installation and configuration in the Wiki.

buzo commented on 2018-10-17 14:41 (UTC)

phoeven: This is Arch Linux, you won't get much support for Manjaro here. Besides, did you read the pinned comment, especially #1 there?

phoeven commented on 2018-10-16 19:04 (UTC)

Tried to install this with several kernels (4.14, 4.17, 4.18) but failed.

(1/6) Install DKMS modules ==> dkms install vmware-workstation/15.0.0_10134415 -k 4.18.7-rt5-MANJARO error: command terminated by signal 13: Broken pipe

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

Not a lot to find in the make.log, only: /var/lib/dkms/vmware-workstation/15.0.0_10134415/build/vmmon-only/bootstrap/.tmp_monLoaderVmmon.o: warning: objtool: .text: unexpected end of section CC [M] /var/lib/dkms/vmware-workstation/15.0.0_10134415/build/vmmon-only/bootstrap/bootstrap.o /var/lib/dkms/vmware-workstation/15.0.0_10134415/build/vmmon-only/common/.tmp_task.o: warning: objtool: .text: unexpected end of section LD [M] /var/lib/dkms/vmware-workstation/15.0.0_10134415/build/vmmon-only/vmmon.o

Anybody any thoughts what's causing this?

jihem commented on 2018-10-12 20:13 (UTC)

mozzi32: because my bundle includes all the ISO images to install guest additions (stored in /usr/lib/vmware/isoimages). With the 149MB installer, the guest additions are downloaded only when you want to install them on a VM.

mozzi32 commented on 2018-10-12 16:58 (UTC)

I don't understand why your bundle is 420Mb size as on vmware site the download size is only 149Mb

jihem commented on 2018-10-10 21:13 (UTC) (edited on 2018-10-10 21:24 (UTC) by jihem)

MisterPresident: I never had this issue. Does your user have sudo rights? If no, be sure to enter the root credentials when the popup ask your password. You can also try to enter the license key from a terminal with root rights: https://wiki.archlinux.org/index.php/VMware#Entering_the_Workstation_Pro_license_key

MisterPresident commented on 2018-10-09 19:30 (UTC)

After entering my license key / or trying the trail version I get this message: Failed to register license. This may be because the root password is required to register your license. Please contact a system administrator with any questions. Any ideas?

gbr commented on 2018-10-07 20:37 (UTC)

Sounds great, thank you!

jihem commented on 2018-10-07 12:59 (UTC)

gbr: I've made some tests and I can confirm that gcr is responsible of the problem. I will add it in the dependencies in a future package update.

gbr commented on 2018-10-07 07:16 (UTC)

jihem: Thanks a lot for the tips. You're not going to believe this. I had already given up about getting the proper theme in VMware. So, a few minutes ago (literally) I had to use VMware, and I realized that both GTK/Icon themes were picked up correctly. Hilarious. So I had to find out how in the world I was able to fix this. The only thing I did in the past few hours was installing some packages, so it had to be it. I uninstalled about 8 packages and opened up VMware to see if some of them would break theming again. It actually did, so I skipped the ones which had nothing to do with GTK or GNOME and I was left with: gvfs. I found it weird that VMware needed gvfs to detect my default GTK/icon theme, however, when I installed gvfs, it pulled some other package too, called 'gcr'. So I uninstalled gvfs and just left gcr installed. To my surprise it worked...

But tomorrow I'll set up a virtual machine in a clean non-GNOME ambient, then install both vmware-workstation and gcr to see how it goes.

jihem commented on 2018-10-06 20:26 (UTC)

gbr: A (long) explanation of this behaviour: VMware installation includes all the libraries it needs to work. When you start the program, it firstly try to load the libraries installed by your distribution, but if it fails for some reason, it loads its own libraries instead (for information, setting VMWARE_USE_SHIPPED_LIBS=1 force VMware to use its own libraries). The problem is: VMware includes a very old version of GTK3 (version 3.14) and it seems that this version doesn't load the GTK theme defined by the user.

So, if you are lucky, VMware can load the Arch version of GTK and it displays your theme properly, but if it can't, it will display the default GTK 3.14 theme. This behaviour can change simply by upgrading the system, installing or removing some packages.

On VMware 14, I was never able to use the system GTK library, so I added a hack in the package to force VMware to use the user theme by setting the GTK_THEME environment variable. But it doesn't always work well, depending if your theme is compatible with GTK 3.14 or not.

Currently, VMware theme works well for me. So, the problem is probably that you have new packages/missing packages compared to your previous installation. You can try to find which library is responsible by reading logs files in /tmp/vmware-$USER/vmware-apploader*.log, then installing/removing the related packages, but it may be complicated.

Alternatively, you can try to export the environment variable GTK_THEME=Breeze-Dark before starting VMPlayer and see if your theme is compatible with GTK 3.14.

gbr commented on 2018-10-06 14:14 (UTC) (edited on 2018-10-06 14:15 (UTC) by gbr)

Were any of you guys able to make VMplayer use the proper GTK3 theme and icons under KDE (more specifically, Breeze-Dark and Papirus-Dark)? I swear to God. Theming in version 14 didn't work at all for me, but after the 15.0 update, it started to work flawlessly. But then I decided to do a clean install of Arch yesterday, so I installed VMware, but now it doesn't pick up the proper theme and icons, again. I don't get it, it's only happening with VMware amongst all GTK3-based programs. I've tried using VMWARE_USE_SHIPPED_LIBS=1, but it did nothing either. Does anyone have any ideia of what is causing this? VMware always picks up the dark Adwaita theme.

jihem commented on 2018-09-30 07:50 (UTC)

vmAutoStart.xml file is automatically created by VMware if it doesn't exist. On this release, I've added this file in the package, that's why you had this conflict. Deleting this file before upgrading is the right thing to do.

king007 commented on 2018-09-30 06:18 (UTC)

@jihem

Thank you for quick upgrade.

I have got new "updates available" notification from the package manager as I was using version 14. I tried upgrading it and after the build process i got the error "conflicting files : /etc/vmware/hostd/vmAutoStart.xml" (https://imgur.com/a/rV6kJ4y). I then removed version 14 and tried to do fresh install of version 15 and I still got the same error.

Finally I have deleted the file manually and restarted the build process, installation was successful and everything seems to be fine so far.

Regards

jihem commented on 2018-09-29 14:26 (UTC)

Hi,

I've just updated the package for version 15.0.0. Tell me if you see some bugs. I've not tested the new REST API because I don't know what it is exactly and how to test it, so feedback are welcome.

I've created vmware-workstation14 package for people who want to stay on version 14.

strayArch commented on 2018-09-26 15:58 (UTC) (edited on 2018-09-26 15:59 (UTC) by strayArch)

jihem's version worked for me. I think the new thumbnails might not be updated properly. Thanks a ton!

buzo commented on 2018-09-26 14:57 (UTC)

sajmonella9: May I suggest to continue this discussion with jihem via e-mail?

jihem commented on 2018-09-26 14:19 (UTC)

@sajmonella9 The link I provide does not contain the package but the sources to create it; extract the archive, create the package with makepkg and install it with pacman. Or be patient, because there is some bugs with this PKGBUILD.

sajmonella9 commented on 2018-09-26 10:50 (UTC)

@jihem you'r new PKGBUILD send me this output :

sudo pacman -U vmware-workstation.tar.xz loading packages... error: missing package metadata in vmware-workstation.tar.xz error: 'vmware-workstation.tar.xz': invalid or corrupted package

CaskAle13c commented on 2018-09-25 23:43 (UTC)

@jihem Thank you. I will compare this against mine to learn why my work would not build.

jihem commented on 2018-09-25 23:00 (UTC) (edited on 2018-09-29 14:15 (UTC) by jihem)

@CaskAle13c Actually, I already made a PKGBUILD. If you really want it now, you can download it here: (EDIT: this link is not useful anymore)

But I didn't test it well, so you could see some bugs or missing functionalities.

CaskAle13c commented on 2018-09-25 20:55 (UTC) (edited on 2018-09-25 20:58 (UTC) by CaskAle13c)

@jihem I have been very frustrated by trying to update the pkgbuild myself. I keep getting "cp: target 'vmware-workstation-server/vmware-wssc-adminTool' is not a directory" errors on directory structures that are identical in version 15 to what they were in 14. It seems to get stuck here:

cp -r \ vmware-workstation/bin/ \ vmware-vmx/{,s}bin/ \ vmware-vix-core/bin/ \ vmware-vprobe/bin/ \ vmware-workstation-server/{vmware-hostd,vmware-vim-cmd,vmware-wssc-adminTool} \ #vmware-network-editor-ui/bin/ \ vmware-player-app/bin/ \ "$pkgdir/usr/bin"

Aside from the vmware-network-editor-ui/bin/* directory which I commented out. Everything in this cp block seems to be identical to v.14.

Since you may not get to it till the weekend, have you any thoughts on why it wont even build for me>

jihem commented on 2018-09-25 20:41 (UTC)

I will probably update the package this week-end, because I want to check if all functionalities work correctly and I don't have enough time for the moment.

I don't like the new icons. :(

cros13 commented on 2018-09-25 18:04 (UTC)

New build is 15.0.0-10134415 Hashes for VMware-Workstation-Full-15.0.0-10134415.x86_64.bundle MD5SUM: 462e8db2a6d0df59af8ebac3af609235 SHA1SUM: a3de1f597b5facd4a8c084da5717786f88133154 SHA256SUM: 00c50710ef23a88fdff2d6c81554820d45797c62c8d72630cd2c69fd43014d94

vmware-netcfg binary doesn't seem to exist in 15. vmware-network-editor-ui/bin path no longer exists and a quick search didn't find it in the extracted bundle.

vmware-vix-core/vix-perl.tar.nogz doesn't exist anymore.

vmware-tools-freebsd are no longer included in the package.

vmmon and vmnet patches for DKMS apply. vmnet cleanly, vmmon with a line offset. vmmon and vmnet build and insmod OK.

sajmonella9 commented on 2018-09-25 10:32 (UTC)

https://blogs.vmware.com/workstation/2018/09/workstation-15-is-here.html

Check new version, (GREAT NEW ICONS!)

hogar1977 commented on 2018-09-02 02:17 (UTC)

Just a question...

Does anyone else have to manually start networks and usbarbitrator services after update? I think it was not required before... I have this issue for several updates already :/ Or am I imagining things (meaning it was always the case)?

Regs and kudos for all the good work that goes into maintaining this!

Xaero_Vincent commented on 2018-08-30 20:43 (UTC)

Looks like upstream librsvg fixed the bug as of v2.44.1. VMware works again for me without the LD_LIBRARY_PATH variable set.

Adson commented on 2018-08-29 08:10 (UTC)

@daedallus Works like a charm ! Thanks for the tip !

daedallus commented on 2018-08-28 06:58 (UTC) (edited on 2018-08-28 06:58 (UTC) by daedallus)

For people who use VMware® Workstation 14 Player and have the Librsvg v2.44 panic problem and don't want to downgrade to Librsvg v2.42 for whatever reason here is how i did it . "sudo nano /etc/vmware/bootstrap" add the following line "export LD_LIBRARY_PATH=/lib/vmware/lib/librsvg-2.so.2:$LD_LIBRARY_PATH"

save and reboot

jihem commented on 2018-08-26 21:18 (UTC)

I've modified the package to fix this bug. Sorry for the delay.

There is no need to report this problem because it doesn't come from librsvg: this is because the proprietary VMware libraries are compiled for an old version of librsvg and something was broken with the new version.

microdou commented on 2018-08-24 17:29 (UTC)

@Eike Thank you! I'm just like you, a normal user... I have no idea what actually cause the problem. Hope someone can report or find the actual issue.

Eike commented on 2018-08-24 16:24 (UTC)

@microdou: you, sir or madam, are fcking awesome. fixed this for me.

are you going to report this issue back to the maintainer of "librsvg" package or would it be more adequate to report it to the libRSVG team?

microdou commented on 2018-08-24 15:29 (UTC)

I get the same error after updating some packages. I finally pinpointed it to a troublesome package called librsvg. librsvg-2:2.44.0-1 caused the error. Downgrading to a prior one librsvg-2:2.42.6-1 solves the issue. you may find the package in /var/cache/pacman/pkg/

CaskAle13c commented on 2018-08-24 15:18 (UTC)

I have the same error as Eike. I reverted to the prior kernel and it did not fix the problem. I wish I had kept better track of the updates applied this morning.

Eike commented on 2018-08-24 14:19 (UTC) (edited on 2018-08-24 14:30 (UTC) by Eike)

This update breaks my installation - but it might be VMware itself, I'm not sure:

thread '<unnamed>' panicked at 'called `Option::unwrap()` on a `None` value', libcore/option.rs:345:21
note: Run with `RUST_BACKTRACE=1` for a backtrace.
fatal runtime error: failed to initiate panic, error 5´´

jihem commented on 2018-08-16 07:18 (UTC)

For people who have the same issue than @silenx, you should only have to reload the module (modprobe -r vmmon && modprobe vmmon) to fix it.

silenx commented on 2018-08-15 22:26 (UTC) (edited on 2018-08-16 00:18 (UTC) by silenx)

Hello, issue on updating/install 14.1.3-1 :

2018-08-15T23:21:43.780+02:00| vmx| I125: Msg_Post: Error

2018-08-15T23:21:43.780+02:00| vmx| I125: [msg.vmmonPosix.badVersion] Version mismatch with vmmon module: expecting 331.0, got 330.0.

2018-08-15T23:21:43.780+02:00| vmx| I125: [msg.vmmonPosix.badDriver] You have an incorrect version of the 'vmmon' kernel module.

EDIT: Resolved with a clean reinstall ( include dependencies ) issue was with dkms and old 14.1.2 probably not removed correctly

basemax commented on 2018-08-04 04:04 (UTC)

can not installing!

==> Making package: vmware-workstation 14.1.2-1 (Sat 04 Aug 2018 08:32:19 AM +0430)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Downloading VMware-Workstation-Full-14.1.2-8497320.x86_64.bundle...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:08 --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:16 --:--:--     0
100  2201  100  2201    0     0     84      0  0:00:26  0:00:26 --:--:--   507
  -> Found bootstrap
  -> Found vmware-vix-bootstrap
  -> Found config
  -> Found pam.d-vmware-authd
  -> Found configure-initscript.sh
  -> Found vmware-environment.sh
  -> Found config.xml
  -> Found datastores.xml
  -> Found environments.xml
  -> Found proxy.xml
  -> Found vmware-hostd-certificates.service
  -> Found vmware-hostd.service
  -> Found vmware-networks-configuration.service
  -> Found vmware-networks.service
  -> Found vmware-usbarbitrator.service
  -> Found dkms.conf.in
  -> Found Makefile
  -> Found vmmon.patch
  -> Found vmnet.patch
==> Validating source files with sha256sums...
    VMware-Workstation-Full-14.1.2-8497320.x86_64.bundle ... FAILED
    bootstrap ... Passed
    vmware-vix-bootstrap ... Passed
    config ... Passed
    pam.d-vmware-authd ... Passed
    configure-initscript.sh ... Passed
    vmware-environment.sh ... Passed
    config.xml ... Passed
    datastores.xml ... Passed
    environments.xml ... Passed
    proxy.xml ... Passed
    vmware-hostd-certificates.service ... Passed
    vmware-hostd.service ... Passed
    vmware-networks-configuration.service ... Passed
    vmware-networks.service ... Passed
    vmware-usbarbitrator.service ... Passed
    dkms.conf.in ... Passed
    Makefile ... Passed
    vmmon.patch ... Passed
    vmnet.patch ... Passed
==> ERROR: One or more files did not pass the validity check!
==> ERROR: Makepkg was unable to build vmware-workstation.
==> Restart building vmware-workstation ? [y/N]
==> -------------------------------------------
==> 

NowG commented on 2018-07-09 09:38 (UTC) (edited on 2018-07-09 09:40 (UTC) by NowG)

@buzo I did that by pacman -S linux-headers.

In fact, this command will install the version 4.17.3-1 linux-headers. This version is not 4.17-2-1 that vmware expected.

And the command yaourt -S vmware-workstation seems to download the right version. I can find it in the path /usr/lib/moudules/.

buzo commented on 2018-07-09 08:54 (UTC)

NowG: Have you installed linux-headers?

NowG commented on 2018-07-09 06:59 (UTC) (edited on 2018-07-09 06:59 (UTC) by NowG)

module vmmon load failed.

The actions that all I did:

1) yaourt -S vmware-workstation

2) modprobe -a vmw_vmci vmmon

Then the WARNING shows like below: modprobe: WARNING: Module vmmon not found in directory /lib/modules/4.17.2-1-ARCH

buzo commented on 2018-07-08 21:16 (UTC) (edited on 2018-07-08 21:19 (UTC) by buzo)

vmplayer crashed on guest shutdown, leaving this message:

VMware Player Error:
VMware Player unrecoverable error: (vmplayer)
Unexpected signal: 11.
A log file is available in "/tmp/vmware-sts/vmware-vmplayer-19886.log".  
You can request support.  
To collect data to submit to VMware technical support, run "vm-support".
We will respond on the basis of your support entitlement.

But there is no vm-support executable. What should I do?

jihem commented on 2018-07-06 18:29 (UTC)

linarcx: I don't have this error. Your .bundle file is probably corrupted (maybe not fully downloaded). Remove it and rebuild the package.

linarcx commented on 2018-07-06 13:40 (UTC) (edited on 2018-07-06 13:41 (UTC) by linarcx)

Hi. when i want to install, i get some errors:

==> Validating source files with sha256sums...
VMware-Workstation-Full-14.1.2-8497320.x86_64.bundle ... FAILED
bootstrap ... Passed
vmware-vix-bootstrap ... Passed
config ... Passed
pam.d-vmware-authd ... Passed
configure-initscript.sh ... Passed
vmware-environment.sh ... Passed
config.xml ... Passed
datastores.xml ... Passed
environments.xml ... Passed
proxy.xml ... Passed
vmware-hostd-certificates.service ... Passed
vmware-hostd.service ... Passed
vmware-networks-configuration.service ... Passed
vmware-networks.service ... Passed
vmware-usbarbitrator.service ... Passed
dkms.conf.in ... Passed
Makefile ... Passed
vmmon.patch ... Passed
vmnet.patch ... Passed
==> ERROR: One or more files did not pass the validity check!
The build failed.
>>> elapsed time 13s

jihem commented on 2018-06-21 17:55 (UTC)

TheChickenMan: Thanks! I probably wouldn't be able to create this package without the work of the first packager, Synthead. But I also spent a lot of time to improve his package (to fix bugs, add missing functionalities, maintain for new versions...). It is not funny at all, but I'm pleased with the result.

jihem commented on 2018-06-21 17:55 (UTC)

Sherlock-Holo: I'm not sure I can help you, I don't really use this functionality. For testing purpose, I just run the vmware-hostd.service with one shared VM on my computer (which is also the client) and I don't have any problem.

You can check if it is a network problem: do you use the same port number in the host and in the client (see in "Edit", "Preferences", "Shared VMs")? Does the host use a firewall which blocks connections to this port? Moreover, check if you have the sufficient permissions (right click on "Shared VMs", "Permissions..."). You can also try to run vmware-hostd.service on the client machine and see if it works (if yes, the problem comes from the host or the network).

jihem commented on 2018-06-21 17:55 (UTC)

GugaDozero: sorry the the late answer, I hope you have found a solution. Otherwise, be sure that ncurses5-compat-libs package is installed and try to manually run the command "bash VMware-Workstation-Full-14.1.2-8497320.x86_64.bundle --extract=extracted" in the PKGBUILD directory to see the errors.

TheChickenMan commented on 2018-06-21 13:15 (UTC)

I tried to put a package together for this last year, ran into endless trouble and eventually gave up assuming it was just too complicated and likely impossible. Your package works great and is really appreciated! Now, to read through the PKGBUILD in detail and learn something. Lots of credit for putting this together. I'm sure it wasn't easy.

Sherlock-Holo commented on 2018-06-17 00:48 (UTC)

I install vm workstation on 2 computers, one enable and start vmware-networks.service, vmware-usbarbitrator.service, vmware-hostd.service, and then use another computer to connect to the host, I connected but I can't see any vm and when I click create a new machine, my computer(not the host) vm-workstation program is panic.

GugaDozero commented on 2018-06-06 21:16 (UTC) (edited on 2018-06-06 22:19 (UTC) by GugaDozero)

Everything seemed ok, then:

==> Extracting sources... ==> Starting prepare()... ==> ERROR: A failure occurred in prepare(). Aborting... ==> ERROR: Makepkg was unable to build vmware-workstation. ==> Restart building vmware-workstation ? [y/N] ==> -------------------------------------------

PS: I have changed the tmp of yaourt to /home/$USER/tmp, I should say that

i simply don't know what to do anymore

st8plgun commented on 2018-05-23 14:13 (UTC) (edited on 2018-05-23 21:37 (UTC) by st8plgun)

The upgrade to 14.1.2-1 broke the graphical elements of my installation under Antergos. The application starts and functions correctly and my VMs are functional, but the Workstation window is rendered in all black with white text and the menu bar element windows (File, Edit, View) all drop down as fully transparent and the white text overlays the visible text under the transparent dropdown. As a result, it is really difficult to use the Workstation menus. I attempted to reinstall w/ no success.

Any troubleshooting ideas?

Thanks

*EDIT* Appears my issue is a compatibility problem w/ Numix-Frost-Light application theme. Switching it to Adwaita(default) resolves the problem.

bigskyarch commented on 2018-05-15 17:47 (UTC)

I get an error when trying to install vmware workstation from the update manager. /tmp is full and cannot extract. /tmp is currently 2GB in size. It was recommended to edit yaourtrc to point to another tmp directory. I did this but the package still attempts to extract in /tmp.

Any suggestions?

Thanks

Asgaroth commented on 2018-04-27 14:55 (UTC)

@jihem, thank you, that fixed it for me, much appreciated.

jihem commented on 2018-04-27 13:49 (UTC)

@Asgaroth: see https://superuser.com/questions/1210758/error-one-or-more-pgp-signatures-could-not-be-verified-arch-linux

Asgaroth commented on 2018-04-27 10:00 (UTC)

I'm getting some gpg failures for ncurses when trying to install this package.

First occurance is here:


==> Validating source files with md5sums...
    ncurses-6.1.tar.gz ... Passed
    ncurses-6.1.tar.gz.sig ... Skipped
==> Verifying source file signatures with gpg...
    ncurses-6.1.tar.gz ... FAILED (unknown public key 702353E0F7E48EDB)
==> ERROR: One or more PGP signatures could not be verified!

It then completely fails the installation at this point:


==> Validating source files with sha256sums...
    VMware-Workstation-Full-14.1.1-7528167.x86_64.bundle ... Passed
    bootstrap ... Passed
    vmware-vix-bootstrap ... Passed
    config ... Passed
    pam.d-vmware-authd ... Passed
    configure-initscript.sh ... Passed
    vmware-environment.sh ... Passed
    config.xml ... Passed
    datastores.xml ... Passed
    environments.xml ... Passed
    proxy.xml ... Passed
    vmware-hostd-certificates.service ... Passed
    vmware-hostd.service ... Passed
    vmware-networks-configuration.service ... Passed
    vmware-networks.service ... Passed
    vmware-usbarbitrator.service ... Passed
    dkms.conf.in ... Passed
    Makefile ... Passed
    vmmon.patch ... Passed
    vmnet.patch ... Passed
:: failed to verify ncurses5-compat-libs integrity

I am trying to install using the following command (if relevent)


pacaur -S vmware-workstation

al-Kate commented on 2018-04-22 10:11 (UTC)

Wow! This is beautiful work, many thanks to maintainer. I love AUR.

jihem commented on 2018-04-22 05:15 (UTC)

It seems gksu was removed from official repos a few hours ago. I've simply removed this dependency in the package because VMware includes its own gksu version in case it is not installed in the system.

lazydomino commented on 2018-04-22 03:40 (UTC)

when I tried to compile this package, I got these errors:

==> Making package: vmware-workstation 14.1.1-2 (Sun Apr 22 11:39:38 HKT 2018)
==> Checking runtime dependencies...
==> Installing missing dependencies...
error: target not found: gksu
==> ERROR: 'pacman' failed to install missing dependencies.

It seems that gksu is no longer alive in aur repo.

giswqs commented on 2018-03-22 18:53 (UTC)

@jihem I added the following three lines to /etc/pacman.conf. The errors still show up. Thanks anyway!

IgnorePkg = vmware-workstation vmware-horizon-client

NoUpgrade = vmware-workstation vmware-horizon-client

NoExtract = vmware-workstation vmware-horizon-client

jihem commented on 2018-03-21 20:24 (UTC)

@giswqs: I'm sorry, but I don't know how I could fix it, both programs require these files. Maybe adding these files in the NoUpgrade or NoExtract setting in /etc/pacman.conf can help.

giswqs commented on 2018-03-21 01:34 (UTC) (edited on 2018-03-21 01:35 (UTC) by giswqs)

The package conflict between vmware-horizon-client and vmware-workstation was first reported by @jvybihal on 2017-09-07. I can confirm that this issue still exists. I installed vmware-workstation first, then I had to use --force to install vmware-horizon-client. Now everytime I use yaourt to update packages, it shows the following errors (32 lines). Is there a way to fix this? Thanks.

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'

....27 more lines of errors like above.

jihem commented on 2018-02-22 19:09 (UTC)

@joelteixeira: I confirm, I also have this bug. Thanks for your detailed informations, I will investigate when I will have time.

joelteixeira commented on 2018-02-21 21:21 (UTC)

Hello there, when using this package I can't copy a file from any guest (tried windows 10, kali, ubuntu) because it uses a wrong path. For instance, when trying to copy "test.mkv" from guest to host it will show a message saying:

The file or folder /WlgTof/test.mkv does not exist.

But the reference should be "/tmp/VMwareDnD/WlgTof/test.mkv" that is a symlink to default user folder as shown below.

myhost /tmp/VMwareDnD $ ls -lh lrwxrwxrwx 1 username users 48 fev 21 17:51 WlgTof -> /home/username/.cache/vmware/drag_and_drop/WlgTof

So, the file was indeed transferred from guest to host but only the reference was wrong. I could reproduce in two machines (different hardware, DE, WM) and after uninstalling the package and using the standard bundle it works. So I believe its related with some of the patches, services, etc. Anyone else facing the same issue?

Thank you

alexei commented on 2018-02-11 01:11 (UTC)

For multiple monitors feature with Awesome WM, see this workaround: https://github.com/awesomeWM/awesome/pull/2188

joelteixeira commented on 2018-02-09 23:20 (UTC)

@jihem you're absolutely right. I thought headers was a requirement and didn't checked as I should. Thank you a lot.

jihem commented on 2018-02-09 18:56 (UTC)

Hi joelteixeira,

This package should work with Linux 4.15. If it's a fresh installation you have probably forgotten to install the linux-headers package.

joelteixeira commented on 2018-02-09 15:32 (UTC)

Hi all, 4.15 had broke something? I was using normally on a 4.14 machine but on a fresh installed system I got:

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

And trying to load vmmon:

modprobe vmmon <br> modprobe: FATAL: Module vmmon not found in directory /lib/modules/4.15.1-2-ARCH

uname -a Linux hostname 4.15.1-2-ARCH #1 SMP Sun Feb 4 22:27:45 UTC 2018 x86_64 GNU/Linux

Are you guys facing something similar?

jihem commented on 2018-01-31 16:04 (UTC) (edited on 2018-02-03 20:52 (UTC) by jihem)

@ailick: I don't have any problem with this version on the kernel on Arch, I think it's more probably a problem with Manjaro.

I don't have time to investigate your problem and I don't really know Manjaro, but my idea is that the version of GCC used to compile the kernel is more recent than the version of GCC installed on your system which doesn't already include the patch retpoline. If I'm right (not sure at all), you have 2 solutions: downgrade your kernel on the previous version until a new version of GCC, or use a more recent version of GCC (for example from testing repo if there is a testing repo in Manjaro).

Edit: I just discovered a tip that can help you: after the startup, loading vmmon module with: modprobe --force-vermagic vmmon

ailick commented on 2018-01-31 05:40 (UTC) (edited on 2018-01-31 05:41 (UTC) by ailick)

Something is not going well on 'kernel 4.14.15'

[ 7.885870] vmmon: version magic '4.14.15-1-MANJARO SMP preempt mod_unload modversions retpoline ' should be '4.14.15-1-MANJARO SMP preempt mod_unload modversions '

[ 14.081850] vmmon: version magic '4.14.15-1-MANJARO SMP preempt mod_unload modversions retpoline ' should be '4.14.15-1-MANJARO SMP preempt mod_unload modversions '

jmp commented on 2018-01-19 22:57 (UTC) (edited on 2018-01-19 23:29 (UTC) by jmp)

Hey jihem, thanks for the work on this package!

For anyone who might get the following error... On a clean, minimal install of Arch, after installing this AUR package, modprobe -a vmmon came back with: WARNING: Module vmmon not found in directory /lib/modules/4.14.13-1-ARCH

pacman -S linux-headers solved this for me. It runs dkms install vmware-workstation/14.1.1_7528167 -k 4.14.13-1-ARCH and you should be able to run modprobe -a vmmon, afterward.

jihem commented on 2018-01-11 18:58 (UTC)

Hi all,

I finally changed my mind concerning VMware 12. It seems that a lot of people cannot upgrade to VMware 14 (because of the license or an incompatible processor) and VMware continue to provide security updates. Also, vmware-patch package is clearly not as convenient to use as this package.

That's why I created the package vmware-workstation12 and I will try to maintain it for the next kernel versions. It should not be a big work for me, but I will be able to make only very limited tests (my single machine already run VMware 14).

Muddy commented on 2018-01-09 02:54 (UTC)

jihem i'll add this as well in case anyone had installed 12.5.x manually and upgraded to 14.x via AUR as I did and ran the uninstall and deleted all the previous files. Apparently I ended up with 2x /etc/vmware/config files and I had the "[AppLoader] Unable to lookup library directory" error as well but removing the older /etc/vmware/config file (by renaming, just in case) and copying the other config.pacnew file to just config did the trick. Thank you for making this work.

teacher4711 commented on 2018-01-07 20:00 (UTC)

Thank you so much for updating to the latest version 12.5.8!!!

I tried using version 14 with the ' monitor.allowLegacyCPU = "true" ' command in the /etc/vmware/config file but to no avail.

Greetings Michael

jihem commented on 2018-01-07 15:38 (UTC) (edited on 2018-01-08 08:14 (UTC) by jihem)

To be clear, I don't maintain the 12.x.x branch of VMware, because I cannot reliably test the both versions on my personal machine. I only put instructions to install the last version I have built and tested.

Exceptionally, I have updated the package for 12.5.8 because it's probably the last update VMware will provide for this version. But keep in mind that I won't maintain compatibility for Linux > 4.14 (which is fortunately the new LTS) or fix future bugs/incompatibilities.

So, if you don't want to stay on Linux LTS, you should switch to vmware-patch. It is not as convenient to install as this package but the current maintainer provides the compatibility with this version of VMware.

teacher4711 commented on 2018-01-06 18:23 (UTC) (edited on 2018-01-06 18:33 (UTC) by teacher4711)

First of all, thanks for the awesome package and the dedication you put into it.

Is it possible to also get the latest 12.5.8 version since you still seem to maintain the 12.5.7 version and you pinned instructions how to get it?

That would be awesome because I have a Core2Duo which is not capable of running the latest 14.x.x version.

What I changed in the PKGBUILD to get the version is: pkgver=12.5.8_7098237

The first line in the sha256sums to '04b93507724a5d38ea154436fb5c96e85b1009955eea5bb7995c5289a5acac32'

Unfortunately, there is an error message: Hunk #1 FAILED at 77. 1 out of 1 hunk FAILED -- saving rejects to file vmnetInt.h.rej

Thanks in advance Michael

jihem commented on 2018-01-03 19:51 (UTC)

@Win8Error: Thanks! It's done.

Win8Error commented on 2018-01-03 10:28 (UTC)

Can you please add "ncurses5-compat-libs" to the dependencies list?

Without it VMware can't use the Guest-Additions-ISOs for the VMs.

zigo commented on 2017-12-29 08:44 (UTC) (edited on 2017-12-29 08:46 (UTC) by zigo)

@jihem i removed the /var/lib/dkms/vmware-workstation/14.1.0_7370693/build directory and restarted the command "dkms install -k 4.14.8-1-ARCH vmware-workstation/14.1.0_7370693". I get the same error

Kernel preparation unnecessary for this kernel. Skipping...

Building module:

cleaning build area...

make -j4 KERNELRELEASE=4.14.8-1-ARCH KVERSION=4.14.8-1-ARCH SRCDIR=/usr/src/vmware-workstation-14.1.0_7370693....(bad exit status: 2)

Error! Bad return status for module build on kernel: 4.14.8-1-ARCH (x86_64) Consult /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/make.log for more information.

jihem commented on 2017-12-29 07:47 (UTC)

Try to remove /var/lib/dkms/vmware-workstation/14.1.0_7370693/build directory and restart the command.

zigo commented on 2017-12-29 06:53 (UTC)

@jihem i started the command "dkms install -k 4.14.8-1-ARCH vmware-workstation/14.1.0_7370693" and i get this

Building module: cleaning build area... make -j4 KERNELRELEASE=4.14.8-1-ARCH KVERSION=4.14.8-1-ARCH SRCDIR=/usr/src/vmware-workstation-14.1.0_7370693...(bad exit status: 2) Error! Bad return status for module build on kernel: 4.14.8-1-ARCH (x86_64) Consult /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/make.log for more information.

this is the output of the "/var/lib/dkms/vmware-workstation/14.1.0_7370693/build/make.log"

DKMS make.log for vmware-workstation-14.1.0_7370693 for kernel 4.14.8-1-ARCH (x86_64) Fri Dec 29 08:51:39 EET 2017 cp -r /usr/src/vmware-workstation-14.1.0_7370693/vmmon-only vmmon-only cp -r /usr/src/vmware-workstation-14.1.0_7370693/vmnet-only vmnet-only make KVERSION=4.14.8-1-ARCH VM_KBUILD=yes -C vmnet-only make KVERSION=4.14.8-1-ARCH VM_KBUILD=yes -C vmmon-only make[1]: Entering directory '/var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only' Using kernel build system. make[1]: Entering directory '/var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only' Using kernel build system. make -C /lib/modules/4.14.8-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[2]: Entering directory '/usr/lib/modules/4.14.8-1-ARCH/build' make -C /lib/modules/4.14.8-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[2]: Entering directory '/usr/lib/modules/4.14.8-1-ARCH/build' CC [M] /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/linux/driver.o CC [M] /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/driver.o CC [M] /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/hub.o CC [M] /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/linux/hostif.o In file included from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/./common/vmx86.h:32:0, from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/linux/driver.h:32, from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/linux/driver.c:48: /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/./include/x86msr.h:115:0: warning: "MSR_MISC_FEATURES_ENABLES" redefined #define MSR_MISC_FEATURES_ENABLES 0x140

In file included from ./arch/x86/include/asm/msr.h:5:0, from ./arch/x86/include/asm/processor.h:21, from ./arch/x86/include/asm/cpufeature.h:5, from ./arch/x86/include/asm/thread_info.h:53, from ./include/linux/thread_info.h:38, from ./arch/x86/include/asm/preempt.h:7, from ./include/linux/preempt.h:81, from ./include/linux/spinlock.h:51, from ./include/linux/seqlock.h:36, from ./include/linux/time.h:6, from ./include/linux/ktime.h:24, from ./include/linux/timer.h:6, from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/./include/compat_timer.h:4, from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/linux/driver.c:24: ./arch/x86/include/asm/msr-index.h:572:0: note: this is the location of the previous definition #define MSR_MISC_FEATURES_ENABLES 0x00000140

In file included from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/./include/vm_asm.h:43:0, from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/linux/hostif.c:65: /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/./include/x86msr.h:115:0: warning: "MSR_MISC_FEATURES_ENABLES" redefined #define MSR_MISC_FEATURES_ENABLES 0x140

In file included from ./arch/x86/include/asm/msr.h:5:0, from ./arch/x86/include/asm/processor.h:21, from ./arch/x86/include/asm/cpufeature.h:5, from ./arch/x86/include/asm/thread_info.h:53, from ./include/linux/thread_info.h:38, from ./arch/x86/include/asm/preempt.h:7, from ./include/linux/preempt.h:81, from ./include/linux/spinlock.h:51, from ./include/linux/seqlock.h:36, from ./include/linux/time.h:6, from ./include/linux/ktime.h:24, from ./include/linux/timer.h:6, from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/./include/compat_timer.h:4, from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/linux/hostif.c:32: ./arch/x86/include/asm/msr-index.h:572:0: note: this is the location of the previous definition #define MSR_MISC_FEATURES_ENABLES 0x00000140

In file included from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/./include/vm_asm_x86.h:41:0, from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/./include/vm_asm_x86_64.h:40, from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/./include/vm_asm.h:46, from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/linux/hostif.c:65: /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/./include/x86_basic_defs.h:78:0: warning: "CR3_PCID_MASK" redefined #define CR3_PCID_MASK 0xFFF

In file included from ./arch/x86/include/asm/processor.h:5:0, from ./arch/x86/include/asm/cpufeature.h:5, from ./arch/x86/include/asm/thread_info.h:53, from ./include/linux/thread_info.h:38, from ./arch/x86/include/asm/preempt.h:7, from ./include/linux/preempt.h:81, from ./include/linux/spinlock.h:51, from ./include/linux/seqlock.h:36, from ./include/linux/time.h:6, from ./include/linux/ktime.h:24, from ./include/linux/timer.h:6, from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/./include/compat_timer.h:4, from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/linux/hostif.c:32: ./arch/x86/include/asm/processor-flags.h:39:0: note: this is the location of the previous definition #define CR3_PCID_MASK 0xFFFull

In file included from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/./include/vm_asm_x86.h:41:0, from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/./include/vm_asm_x86_64.h:40, from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/./include/vm_asm.h:46, from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/linux/driver.c:50: /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/./include/x86_basic_defs.h:78:0: warning: "CR3_PCID_MASK" redefined #define CR3_PCID_MASK 0xFFF

In file included from ./arch/x86/include/asm/processor.h:5:0, from ./arch/x86/include/asm/cpufeature.h:5, from ./arch/x86/include/asm/thread_info.h:53, from ./include/linux/thread_info.h:38, from ./arch/x86/include/asm/preempt.h:7, from ./include/linux/preempt.h:81, from ./include/linux/spinlock.h:51, from ./include/linux/seqlock.h:36, from ./include/linux/time.h:6, from ./include/linux/ktime.h:24, from ./include/linux/timer.h:6, from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/./include/compat_timer.h:4, from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/linux/driver.c:24: ./arch/x86/include/asm/processor-flags.h:39:0: note: this is the location of the previous definition #define CR3_PCID_MASK 0xFFFull

/var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/linux/hostif.c: In function 'HostIF_EstimateLockedPageLimit': /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/linux/hostif.c:1536:19: error: implicit declaration of function 'global_page_state'; did you mean 'global_numa_state'? [-Werror=implicit-function-declaration] lockedPages += global_page_state(NR_PAGETABLE); ^~~~~~~~~~~~~~~~~ global_numa_state CC [M] /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/linux/driverLog.o CC [M] /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/userif.o CC [M] /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/netif.o CC [M] /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/common/memtrack.o cc1: some warnings being treated as errors make[3]: [scripts/Makefile.build:315: /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only/linux/hostif.o] Error 1 make[3]: Waiting for unfinished jobs.... CC [M] /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/bridge.o make[2]: [Makefile:1504: module/var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only] Error 2 make[2]: Leaving directory '/usr/lib/modules/4.14.8-1-ARCH/build' make[1]: [Makefile:114: vmmon.ko] Error 2 make[1]: Leaving directory '/var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmmon-only' make: [Makefile:13: vmmon.ko] Error 2 make: Waiting for unfinished jobs.... CC [M] /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/procfs.o In file included from ./include/linux/pci.h:37:0, from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/compat_netdevice.h:27, from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/netif.c:43: ./include/linux/pci_ids.h:2261:0: warning: "PCI_VENDOR_ID_VMWARE" redefined #define PCI_VENDOR_ID_VMWARE 0x15ad

In file included from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/net.h:38:0, from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/vnetInt.h:26, from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/netif.c:42: /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/vm_device_version.h:57:0: note: this is the location of the previous definition #define PCI_VENDOR_ID_VMWARE 0x15AD

In file included from ./include/linux/pci.h:37:0, from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/compat_netdevice.h:27, from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/netif.c:43: ./include/linux/pci_ids.h:2262:0: warning: "PCI_DEVICE_ID_VMWARE_VMXNET3" redefined #define PCI_DEVICE_ID_VMWARE_VMXNET3 0x07b0

In file included from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/net.h:38:0, from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/vnetInt.h:26, from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/netif.c:42: /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/vm_device_version.h:75:0: note: this is the location of the previous definition #define PCI_DEVICE_ID_VMWARE_VMXNET3 0x07B0

CC [M] /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/smac_compat.o CC [M] /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/smac.o In file included from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/net.h:38:0, from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/vnetInt.h:26, from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/bridge.c:53: /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/vm_device_version.h:75:0: warning: "PCI_DEVICE_ID_VMWARE_VMXNET3" redefined #define PCI_DEVICE_ID_VMWARE_VMXNET3 0x07B0

In file included from ./include/linux/pci.h:37:0, from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/compat_netdevice.h:27, from /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/bridge.c:52: ./include/linux/pci_ids.h:2262:0: note: this is the location of the previous definition #define PCI_DEVICE_ID_VMWARE_VMXNET3 0x07b0

CC [M] /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/vnetEvent.o CC [M] /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/vnetUserListener.o LD [M] /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/vmnet.o Building modules, stage 2. MODPOST 1 modules CC /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/vmnet.mod.o LD [M] /var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only/vmnet.ko make[2]: Leaving directory '/usr/lib/modules/4.14.8-1-ARCH/build' make -C $PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= postbuild make[2]: Entering directory '/var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only' make[2]: 'postbuild' is up to date. make[2]: Leaving directory '/var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only' cp -f vmnet.ko ./../vmnet.o make[1]: Leaving directory '/var/lib/dkms/vmware-workstation/14.1.0_7370693/build/vmnet-only'

jihem commented on 2017-12-29 06:29 (UTC)

@zigo: start the command (with root privileges) "dkms install -k 4.14.8-1-ARCH vmware-workstation/14.1.0_7370693". If it doesn't fail, start "modprobe -a vmw_vmci vmmon" and it should work.

zigo commented on 2017-12-28 20:16 (UTC) (edited on 2017-12-28 21:01 (UTC) by zigo)

@jihem i have linux and linux headers version is 4.14.8-1

when i started any vm by vmware i get this error message

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

and when i execute the command modprobe -a vmmon i get this error

"modprobe: WARNING: Module vmmon not found in directory /lib/modules/4.14.8-1-ARCH"

jihem commented on 2017-12-28 14:44 (UTC)

@zigo: I'm not sure, but I guess you don't have the same version of linux and linux-headers packages (one is 4.14.5 and the other is 4.14.8). Please update your system (pacman -Syu) before trying to reinstall the package.

zigo commented on 2017-12-28 13:03 (UTC) (edited on 2017-12-28 13:04 (UTC) by zigo)

i have this error when installing vmware-workstation 14.1.0-4

==> No kernel 4.14.5-1-ARCH modules. You must install them to use DKMS!

==> dkms remove vmware-workstation/14.1.0_7370693 -k 4.14.8-1-ARCH

any help please

jihem commented on 2017-12-28 10:07 (UTC)

I've tested a VM on Fedora with VMware encryption and UEFI. I am full SSD on my laptop and I didn't see any loss of performances compared to other VMs. iotop showed me good values (with peaks at more than 150MB/s during Fedora installation).

In my opinion, the main problem is that you use an NTFS partition. NTFS driver use FUSE which has bad performances. Maybe it is particularly bad on big files with a lot of random accesses (but I don't know why there are differences with BIOS/UEFI and encryption). So, I think you should also make tests to compare performances on ext4/ntfs.

Also, I made my tests on linux-zen, which includes some optimizations for desktop use. You could test this kernel too.

gbr commented on 2017-12-28 04:01 (UTC) (edited on 2017-12-28 04:22 (UTC) by gbr)

I think I know what the problem is, but I don't have a solution. Based on a few tests I did with recently created VMs, the slow startup happens when I simply encrypt the VM (using VMware's built-in encryption tool), and most importantly when I choose UEFI over BIOS in the VM's options. You can try it for yourself and see if you can reproduce this issue. I have a decent PC (i5 3570k, 8GB RAM, GTX 660), and yet VMware takes about two minutes to start an EMPTY Ubuntu VM with 20GB of encrypted storage. It's worth noting that I have all my VMs on a 1TB HDD (NTFS filesystem). I've also monitored the I/O data on my HDD while I'm booting that VM, and here's how it looks (note the peak writing usage, it's 180.1 kilobytes, yet the disk utilization % is at 100!!!): https://i.imgur.com/IYmAUH9.png

Now, I don't think my HDD went bad because I also did a benchmark test and it looks fine, here's the result: https://i.imgur.com/PO82lwK.png

Thing is, when the VM is booting, browsing files on that HDD is nearly impossible, because it's painfully slow. I've checked VMware's log files but I couldn't find anything relevant as well. I have a SSD too, but I haven't tried setting up a VM on it yet, but I'll try to do that tomorrow and reproduce this.

Any help is appreciated. Thanks

jihem commented on 2017-12-27 17:05 (UTC)

@gbr: yes, you should. This file is automatically generated by VMware if it doesn't exist, but I decided to include it directly in the package.

Did you finally solve your problem of slow VMs on Linux 4.14?

gbr commented on 2017-12-27 16:41 (UTC) (edited on 2017-12-27 16:43 (UTC) by gbr)

I'm getting this error while trying to update from 14.1.0-1 to 14.1.0-3:

error: failed to commit transaction (conflicting files)

vmware-workstation: /etc/vmware-vix/bootstrap exists in filesystem

Errors occurred, no packages were upgraded.

Should I use --force to install it?

hunk commented on 2017-12-27 06:38 (UTC)

@jihem Thank you for your time. I created another OVA file, and this time it works.

jihem commented on 2017-12-26 10:18 (UTC)

@viljeml: I've updated the package with python2-six dependency. It will fix your problem.

jihem commented on 2017-12-26 10:16 (UTC)

@hunk: I have never used i3 or any other tiling WM, I don't know if it can change anything. I use xfce, if you want to test on this desktop environment.

To get more information about the error, you can start VMware from a terminal and see if it display an error when you try to import your file. You should also search informations on log files. They are stored in /tmp/vmware-$USER. Just read files whose name contains the number corresponding to the PID of VMware currently running.

jihem commented on 2017-12-26 10:07 (UTC)

@timofonic: I use linux-zen as default kernel and I don't have your problem.

Firstly, try to uninstall modules (dkms remove -k 4.14.8-1-zen vmware-workstation/14.1.0_7370693) before reinstall them (dkms install -k 4.14.8-1-zen vmware-workstation/14.1.0_7370693).

Now, when you start command "dkms status" on a terminal, do you see the line "vmware-workstation, 14.1.0_7370693, 4.14.8-1-zen, x86_64: installed"? Does the module files exist (/usr/lib/modules/4.14.8-1-zen/kernel/drivers/misc/vmmon.ko and /usr/lib/modules/4.14.8-1-zen/kernel/drivers/net/vmnet.ko)?

If you used bundle installation before trying this package, maybe some modules are still installed and cause conflicts. On /usr/lib/modules/4.14.8-1-zen directory, search and remove following files: vmmon.ko, vmci.ko, vmnet.ko, vmblock.ko and vsock.ko (but don't touch those have extension .gz or .xz). And retry the dkms command to install modules.

viljeml commented on 2017-12-25 11:17 (UTC)

=> Patching VMware for macOS guest support Traceback (most recent call last): File "/tmp/yaourt-tmp-vili/aur-vmware-workstation/src/unlocker.py", line 47, in <module> import six ImportError: No module named six ==> ERROR: A failure occurred in package(). Aborting... ==> ERROR: Makepkg was unable to build vmware-workstation.</module>

hunk commented on 2017-12-25 00:59 (UTC)

@jihem:Thank you for your reply! I still can't open OVA file. This OVA file was made by virtualbox. I clicked File->Open... and it will show a dialog of "Open virtual machines", then I double clicked my OVA file, it does nothing, no warning, no error dialog, just like i didn't double click it. I'm using i3wm, is that OK? Where can I get further info about this problem?

timofonic commented on 2017-12-23 22:38 (UTC) (edited on 2017-12-23 23:29 (UTC) by timofonic)

Modules don't get build here. Would you be able to fix that? What about a separate packages for dkms modules? They can be part of the same PKGBUILD.

modprobe -a vmw_vmci vmmon vmnet

modprobe: WARNING: Module vmmon not found in directory /lib/modules/4.14.8-1-zen modprobe: WARNING: Module vmnet not found in directory /lib/modules/4.14.8-1-zen ZZ

Why? Am I doing some more conplex for me modprobe -a vmw_vmci vmmon vmnet even insmod Sat 23 Dec 2017 11:15:52 PM CET modprobe: WARNING: Module vmmon not found in directory /lib/modules/4.14.8-1-zen modprobe: WARNING: Module vmnet not found in directory /lib/modules/4.14.8-1-zen

Modules aren't in /var/lib/dkms directory. Why? anbox-modules-binder/ dkms_dbversion

I used the following commands and the relevant module (vmmon) got built and installed:

dkms install vmware-workstation/14.1.0_7370693/ -k 4.14.8-1-zen

Creating symlink /var/lib/dkms/vmware-workstation/14.1.0_7370693//source -> /usr/src/vmware-workstation-14.1.0_7370693/

DKMS: add completed.

Kernel preparation unnecessary for this kernel. Skipping...

Building module: make clean rm -rf vmmon vmnet rm -rf vmmon-only vmnet-only rm -f vmmon.ko vmnet.ko rm -f vmmon.o vmnet.o

{ make -j2 KERNELRELEASE=4.14.8-1-zen KVERSION=4.14.8-1-zen SRCDIR=/usr/src/vmware-workstation -14.1.0_7370693; } >> /var/lib/dkms/vmware-workstation/14.1.0_7370693//build/make.log 2>&1

make clean rm -rf vmmon vmnet rm -rf vmmon-only vmnet-only rm -f vmmon.ko vmnet.ko rm -f vmmon.o vmnet.o

Kernel cleanup unnecessary for this kernel. Skipping...

DKMS: build completed.

vmmon.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /usr/lib/modules/4.14.8-1-zen/kernel/drivers/misc/

vmnet.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /usr/lib/modules/4.14.8-1-zen/kernel/drivers/net/

do_depmod 4.14.8-1-zen

sudo dkms install vmware-workstation/14.1.0_7370693/ -k 4.14.8-1-ARCH

Kernel preparation unnecessary for this kernel. Skipping...

Building module: make clean rm -rf vmmon vmnet rm -rf vmmon-only vmnet-only rm -f vmmon.ko vmnet.ko rm -f vmmon.o vmnet.o

{ make -j2 KERNELRELEASE=4.14.8-1-ARCH KVERSION=4.14.8-1-ARCH SRCDIR=/usr/src/vmware-workstati on-14.1.0_7370693; } >> /var/lib/dkms/vmware-workstation/14.1.0_7370693//build/make.log 2>&1

make clean rm -rf vmmon vmnet rm -rf vmmon-only vmnet-only rm -f vmmon.ko vmnet.ko rm -f vmmon.o vmnet.o

Kernel cleanup unnecessary for this kernel. Skipping...

DKMS: build completed.

vmmon.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /usr/lib/modules/4.14.8-1-ARCH/kernel/drivers/misc/

vmnet.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /usr/lib/modules/4.14.8-1-ARCH/kernel/drivers/net/

do_depmod 4.14.8-1-ARCH

DKMS: install completed.

After this process, the modules load sucessfully :D

jihem commented on 2017-12-23 10:39 (UTC)

@hunk: I have just updated the package, can you test with the last version? (the changes I've made are probably not related to your problem, but I didn't test on the older version)

On this version, I can open ova files without problem, I get a message talking about a problem with OVF specification conformance but if I click on "Retry" the VM is imported.

If you still can't import your OVA file, can you tell me more informations: error messages, how the file was created (with VMware or VirtualBox), can you open it with VirtualBox?

hunk commented on 2017-12-23 03:01 (UTC)

I can't open ova file, any solution here?

avarx commented on 2017-12-20 20:42 (UTC) (edited on 2017-12-21 07:54 (UTC) by avarx)

jihem, worked! Thank you for your help!! I owe you!

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.

gbr commented on 2017-12-04 02:50 (UTC)

Not working for me anymore on kernel 4.14.3, all my VMs became REALLY slow to start (they don't even start to be honest).

jihem commented on 2017-11-28 10:39 (UTC)

@timofonic: I know there is a new version of unlocker, but it is useless to update it for the moment: I patched the previous version to work with VMware 14 and it does the job. This file will be updated on the next version of the package. Canberra is probably not related to your problem: I have the same message and it doesn't matter if the package can be created. I think the mistake is that you didn't install linux-headers package before. This package is required when you compile kernel modules with DKMS (but is not defined as a dependency of this package because its exact name depends which kernel you use: for example it is linux-lts-headers if you use linux-lts). In the case you already installed linux-headers but it does not work, give me the output of "dkms install -k 4.13.12-1-ARCH vmware-workstation/14.0.0_6661328"

timofonic commented on 2017-11-28 08:56 (UTC) (edited on 2017-11-28 09:15 (UTC) by timofonic)

Error... Why does it happen? Help me, please:( Because of this error: Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so: cannot open shared object file: No such file or directory I installed both "lincanberra" "lib32-libcanberra-gtk3" and packages, I also tried to switch the first one with "libcanberra-git". The same error happens again. pkgfile libcanberra-gtk-module.so Tue 28 Nov 2017 10:09:18 AM CET extra/libcanberra multilib/lib32-libcanberra Also... # modprobe -a vmw_vmci # modprobe -a vmmon modprobe: WARNING: Module vmmon not found in directory /lib/modules/4.13.12-1-ARCH My lsmod: https://0x0.st/soeP.vmw_vmc :: Package vmware-workstation not found in repositories, trying AUR... :: resolving dependencies... :: looking for inter-conflicts... :: vmware-workstation-14.0.0-2 is up to date -- reinstalling :: vmware-workstation-14.0.0-2 has been flagged out of date on Tue 28 Nov 2017 09:47:50 AM CET AUR Packages (1) vmware-workstation-14.0.0-2 :: Proceed with installation? [Y/n] :: Retrieving package(s)... sudo: a password is required [sudo] password for timofonic: :: Checking vmware-workstation integrity... ==> Making package: vmware-workstation 14.0.0-2 (Tue Nov 28 09:50:44 CET 2017) ==> Retrieving sources... -> Found VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle -> Found bootstrap -> Found config -> Found pam.d-vmware-authd -> Found configure-initscript.sh -> Found vmware-environment.sh -> Found config.xml -> Found datastores.xml -> Found environments.xml -> Found proxy.xml -> Found vmware-hostd-certificates.service -> Found vmware-hostd.service -> Found vmware-networks-configuration.service -> Found vmware-networks.service -> Found vmware-usbarbitrator.service -> Found dkms.conf.in -> Found Makefile -> Found vmblock.patch -> Found vmci.patch -> Found vmmon.patch -> Found vmnet.patch -> Found vsock.patch ==> Validating source files with sha256sums... VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle ... Passed bootstrap ... Passed config ... Passed pam.d-vmware-authd ... Passed configure-initscript.sh ... Passed vmware-environment.sh ... Passed config.xml ... Passed datastores.xml ... Passed environments.xml ... Passed proxy.xml ... Passed vmware-hostd-certificates.service ... Passed vmware-hostd.service ... Passed vmware-networks-configuration.service ... Passed vmware-networks.service ... Passed vmware-usbarbitrator.service ... Passed dkms.conf.in ... Passed Makefile ... Passed vmblock.patch ... Passed vmci.patch ... Passed vmmon.patch ... Passed vmnet.patch ... Passed vsock.patch ... Passed :: Preparing vmware-workstation... ==> Making package: vmware-workstation 14.0.0-2 (Tue Nov 28 09:50:47 CET 2017) ==> WARNING: Skipping dependency checks. ==> Retrieving sources... -> Found VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle -> Found bootstrap -> Found config -> Found pam.d-vmware-authd -> Found configure-initscript.sh -> Found vmware-environment.sh -> Found config.xml -> Found datastores.xml -> Found environments.xml -> Found proxy.xml -> Found vmware-hostd-certificates.service -> Found vmware-hostd.service -> Found vmware-networks-configuration.service -> Found vmware-networks.service -> Found vmware-usbarbitrator.service -> Found dkms.conf.in -> Found Makefile -> Found vmblock.patch -> Found vmci.patch -> Found vmmon.patch -> Found vmnet.patch -> Found vsock.patch ==> WARNING: Skipping all source file integrity checks. ==> Extracting sources... ==> Starting prepare()... Extracting VMware Installer...done. Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so: cannot open shared object file: No such file or directory

timofonic commented on 2017-11-28 08:41 (UTC) (edited on 2017-11-28 08:46 (UTC) by timofonic)

Would you like toupdate the unlocker? There's a newer version here https://github.com/DrDonk/unlocker/blob/master/unlocker.py

jihem commented on 2017-10-22 09:38 (UTC)

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

mirh commented on 2017-10-20 17:40 (UTC)

> 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 (UTC)

For me not install Vmware 14

JiPRA commented on 2017-10-06 01:19 (UTC)

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 (UTC)

@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 (UTC)

@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 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

@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 (UTC) (edited on 2017-10-01 09:29 (UTC) by jihem)

@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 (UTC)

@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 (UTC)

@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 (UTC)

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 (UTC)

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 (UTC)

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 (UTC) (edited on 2017-09-25 15:19 (UTC) by ngkaho1234)

@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 (UTC)

@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 (UTC) (edited on 2017-09-24 05:06 (UTC) by ngkaho1234)

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 (UTC)

@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 (UTC)

@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 (UTC)

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 (UTC)

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

tholinka commented on 2017-08-19 02:04 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

@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 (UTC)

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 (UTC)

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 (UTC)

Después de instalado, no se actualizan los complementos

jihem commented on 2017-07-11 15:03 (UTC)

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 (UTC)

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 (UTC)

@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 (UTC)

"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 (UTC)

@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 (UTC)

@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 (UTC)

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 (UTC)

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

jihem commented on 2017-06-19 08:56 (UTC)

@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 (UTC)

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 (UTC)

@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 (UTC)

@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 (UTC)

@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 (UTC) (edited on 2017-06-06 07:21 (UTC) by zelluz)

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 (UTC)

@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 (UTC) (edited on 2017-06-05 17:14 (UTC) by Sarithis)

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 (UTC)

@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 (UTC)

@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 (UTC)

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 (UTC)

/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 (UTC)

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 (UTC)

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 (UTC) (edited on 2017-05-26 19:31 (UTC) by jihem)

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 (UTC)

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 (UTC)

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 (UTC)

Best. Package. Ever. Love the dkms hook that rebuilds when upgrading the kernel

jihem commented on 2017-05-25 14:37 (UTC)

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

treeshateorcs commented on 2017-05-25 14:07 (UTC)

does this thing cost money?

jihem commented on 2017-05-25 14:01 (UTC)

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 (UTC)

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 (UTC)

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

jihem commented on 2017-05-21 12:04 (UTC)

@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 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

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 (UTC) (edited on 2017-05-03 00:33 (UTC) by F1nny)

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 (UTC) (edited on 2017-04-16 20:38 (UTC) by F1nny)

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 (UTC)

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 (UTC)

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

Synthead commented on 2017-03-31 19:56 (UTC)

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 (UTC)

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 (UTC) (edited on 2017-03-14 12:49 (UTC) by Awesome_Donkey)

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 (UTC) (edited on 2017-03-13 21:50 (UTC) by Synthead)

@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 (UTC)

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!

commented on 2017-03-13 19:17 (UTC)

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 (UTC)

@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 (UTC)

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 (UTC)

Hi x-drum! Thanks for the feedback! I have added ovftool in release 12. Enjoy!

x-drum commented on 2017-02-24 15:33 (UTC)

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 (UTC) (edited on 2017-02-16 21:48 (UTC) by Synthead)

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 (UTC)

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 (UTC)

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 (UTC)

Added systemd service files for vmware-networks.

Synthead commented on 2017-02-12 19:37 (UTC) (edited on 2017-02-12 19:37 (UTC) by Synthead)

modprobe vmmon ;) Seems like there should be a modules-load.d or something

Pival81 commented on 2017-02-12 18:45 (UTC)

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 (UTC)

Added support for VMware's USB Arbitrator.

Synthead commented on 2017-02-10 19:15 (UTC)

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!