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.
Search Criteria
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: | 203 |
| Popularity: | 3.30 |
| First Submitted: | 2017-02-10 19:04 (UTC) |
| Last Updated: | 2024-10-11 05:17 (UTC) |
Dependencies (13)
- dkms (dkms-gitAUR, dkms-fast-zstdAUR)
- fuse2
- gcr
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- gtkmm3
- hicolor-icon-theme (hicolor-icon-theme-gitAUR)
- libaio (libaio-gitAUR)
- libcanberra
- libxcrypt-compat
- pcsclite (pcsclite-gitAUR)
- vmware-keymapsAUR
- sqlite (sqlite-fossilAUR) (make)
- linux-headers (optional) – build modules against Arch kernel
Required by (6)
Sources (22)
- config
- configure-initscript.sh
- dkms.conf.in
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-linux-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-linuxPreGlibc25-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-netware-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-solaris-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-winPre2k-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-winPreVista-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.6.1/24319023/linux/core/VMware-Workstation-17.6.1-24319023.x86_64.bundle.tar
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.6.1/24319023/linux/packages/vmware-tools-windows-12.4.5-23787635.x86_64.component.tar
- Makefile
- vmmon.patch
- vmnet.patch
- vmware-bootstrap
- vmware-environment.sh
- vmware-networks-configuration.service
- vmware-networks.path
- vmware-networks.service
- vmware-usbarbitrator.path
- vmware-usbarbitrator.service
- vmware-vix-bootstrap
sizzen commented on 2019-03-07 03:43 (UTC) (edited on 2019-03-07 03:47 (UTC) by sizzen)
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!
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