AUR (en) - vmware-workstation

Search Criteria

Enter search criteria

Search by

Keywords

Out of Date

Sort by

Sort order

Per page

Package Details: vmware-workstation 17.6.1-2

Package Actions

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:	202
Popularity:	2.79
First Submitted:	2017-02-10 19:04 (UTC)
Last Updated:	2024-10-11 05:17 (UTC)

Dependencies (13)

dkms (dkms-git^AUR, dkms-fast-zstd^AUR)
fuse2
gcr
gtk3 (gtk3-no_deadkeys_underline^AUR, gtk3-classic^AUR, gtk3-classic-xfce^AUR, gtk3-patched-filechooser-icon-view^AUR)
gtkmm3
hicolor-icon-theme (hicolor-icon-theme-git^AUR)
libaio (libaio-git^AUR)
libcanberra
libxcrypt-compat
pcsclite (pcsclite-git^AUR)
vmware-keymaps^AUR
sqlite (sqlite-fossil^AUR) (make)
linux-headers (optional) – build modules against Arch kernel

Required by (6)

Sources (22)

Pinned Comments

jihem commented on 2020-02-10 17:29 (UTC) (edited on 2021-06-19 13:19 (UTC) by jihem)

After the first installation, please:

1) install the appropriate headers package(s) for your installed kernel(s): linux-headers for default kernel, linux-lts-headers for LTS kernel...

2) reboot or load vmw_vmci and vmmon kernel modules (modprobe -a vmw_vmci vmmon)

3) Enable the services you need (using .service units to activate them during boot or .path units to activate them when a VM is started) :

vmware-networks: to have network access inside VMs
vmware-usbarbitrator: to connect USB devices inside VMs

Latest Comments

« First ‹ Previous 1 .. 18 19 20 21 22 23 24 25 26 27 28 .. 66 Next › Last »

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 2023-03-18 01:31 (UTC) by strayArch)

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

Before install: sudo systemctl stop vmware-networks.service vmware-usbarbitrator.service

After Install: sudo rmmod vmw_vmci vmmon; sudo modprobe -a vmw_vmci vmmon; sudo systemctl restart vmware-networks.service 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.