[Solved] VMWare Installation Step

Hello,

I am trying to install VMWare WorkStation on Manjaro KDE guide on Wiki

I am failing at this step :

sudo systemctl enable --now vmware-hostd.service

Getting message :

Failed to enable unit: Unit file vmware-hostd.service does not exist

Also this

Created symlink /etc/systemd/system/multi-user.target.wants/vmware-
networks.service → /usr/lib/systemd/system/vmware-networks.service.
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.
systemctl status vmware-networks.service
    Nov 23 15:33:51 Manjaro-HQ vmware-networks[23827]: Failed to start DHCP service on vmnet8
    Nov 23 15:33:51 Manjaro-HQ vmware-networks[23827]: Failed to start some/all services
    Nov 23 15:33:51 Manjaro-HQ vmware-networks[23827]: Started Bridge networking on vmnet0
    Nov 23 15:33:51 Manjaro-HQ vmware-networks[23827]: Enabled hostonly virtual adapter on vmnet1
    Nov 23 15:33:51 Manjaro-HQ vmware-networks[23827]: Started DHCP service on vmnet1
    Nov 23 15:33:51 Manjaro-HQ systemd[1]: vmware-networks.service: Control process exited, code=exited, status=1/FAILURE
    Nov 23 15:33:51 Manjaro-HQ vmnetBridge[23845]: Stopped bridge enp8s0 to virtual network 0.
    Nov 23 15:33:51 Manjaro-HQ vmnetBridge[23845]: Bridge process exiting.
    Nov 23 15:33:51 Manjaro-HQ systemd[1]: vmware-networks.service: Failed with result 'exit-code'.
    Nov 23 15:33:51 Manjaro-HQ systemd[1]: Failed to start VMware Networks.

journalctl -xe
Nov 23 15:40:48 Manjaro-HQ audit[28782]: USER_START pid=28782 uid=0 auid=1000 ses=1 subj==unconfined msg='op=PAM:session_open grantors=pam_limits,pam_>
Nov 23 15:40:48 Manjaro-HQ sudo[28782]: techxero : TTY=pts/2 ; PWD=/home/techxero ; USER=root ; COMMAND=/usr/bin/modprobe -a vmw_vmci vmmon
Nov 23 15:40:48 Manjaro-HQ sudo[28782]: pam_unix(sudo:session): session opened for user root(uid=0) by techxero(uid=0)
Nov 23 15:40:48 Manjaro-HQ sudo[28782]: pam_unix(sudo:session): session closed for user root
Nov 23 15:40:48 Manjaro-HQ audit[28782]: USER_END pid=28782 uid=0 auid=1000 ses=1 subj==unconfined msg='op=PAM:session_close grantors=pam_limits,pam_u>
Nov 23 15:40:48 Manjaro-HQ audit[28782]: CRED_DISP pid=28782 uid=0 auid=1000 ses=1 subj==unconfined msg='op=PAM:setcred grantors=pam_faillock,pam_perm>
Nov 23 15:40:48 Manjaro-HQ kernel: audit: type=1106 audit(1606138848.853:214): pid=28782 uid=0 auid=1000 ses=1 subj==unconfined msg='op=PAM:session_cl>
Nov 23 15:40:48 Manjaro-HQ kernel: audit: type=1104 audit(1606138848.853:215): pid=28782 uid=0 auid=1000 ses=1 subj==unconfined msg='op=PAM:setcred gr>
Nov 23 15:41:55 Manjaro-HQ nmbd[1455]: [2020/11/23 15:41:55.153773,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Nov 23 15:41:55 Manjaro-HQ nmbd[1455]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.69 for name WORKGROUP<1d>
Nov 23 15:41:55 Manjaro-HQ nmbd[1455]:   This response was from IP 192.168.1.128, reporting an IP address of 192.168.1.128.
Nov 23 15:45:17 Manjaro-HQ plasmashell[1228]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15>
Nov 23 15:45:24 Manjaro-HQ kwin_x11[1175]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 26642, resource id: 10486059, major code: 1>
Nov 23 15:45:33 Manjaro-HQ plasmashell[1228]: qrc:/plasma/plasmoids/org.kde.plasma.volume/contents/ui/main.qml:494:39: QML StreamListItem: Binding loo>
Nov 23 15:47:02 Manjaro-HQ nmbd[1455]: [2020/11/23 15:47:02.589539,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Nov 23 15:47:02 Manjaro-HQ nmbd[1455]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.69 for name WORKGROUP<1d>
Nov 23 15:47:02 Manjaro-HQ nmbd[1455]:   This response was from IP 192.168.1.128, reporting an IP address of 192.168.1.128.
Nov 23 15:51:57 Manjaro-HQ kwin_x11[1175]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 33445, resource id: 123731969, major code: >
Nov 23 15:52:04 Manjaro-HQ nmbd[1455]: [2020/11/23 15:52:04.040555,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Nov 23 15:52:04 Manjaro-HQ nmbd[1455]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.69 for name WORKGROUP<1d>
Nov 23 15:52:04 Manjaro-HQ nmbd[1455]:   This response was from IP 192.168.1.128, reporting an IP address of 192.168.1.128.
Nov 23 15:57:05 Manjaro-HQ nmbd[1455]: [2020/11/23 15:57:05.728952,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Nov 23 15:57:05 Manjaro-HQ nmbd[1455]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.69 for name WORKGROUP<1d>
Nov 23 15:57:05 Manjaro-HQ nmbd[1455]:   This response was from IP 192.168.1.128, reporting an IP address of 192.168.1.128.
Nov 23 15:57:34 Manjaro-HQ kwin_x11[1175]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 41991, resource id: 123731969, major code: >

I have no idea what to do next. I am a Linux n00b… So be gentle on me…

1 Like

If you are a noob like me then the easiest thing to do is just install vmware from the aur with pamac gui

I just installed that rebooted and job done everything installed and working

1 Like

I followed a guide it’s the same as AUR but via terminal…

I remember getting the same/similar issue when I installed via terminal from the vmware website but didn’t get it when I installed from the aur. Hopefully someone more knowledgeable than me will know why

VMware on Arch based platforms are unsupported.

The only viable method is to build using the AUR PKGBUILD.

1 Like

I used this command
pamac build vmware-workstation

It’s a guide on Manjaro site so if not supported than why post a guide ?

Did you install kernel headers for your kernel?

They are required for dkms to be able to build the required modules.

Even it is unsupported by VMware - users keep asking - so we provide a basic guide.

Yes I have. I done everything following the guide Here

When you install using the AUR script - the last lines should look like this

==> Before using VMware, you need to reboot or load vmw_vmci and vmmon kernel modules (in a terminal on root: modprobe -a vmw_vmci vmmon)
==> You may also need to enable some of these services:
- vmware-networks.service: to have network access inside VMs
- vmware-usbarbitrator.service: to connect USB devices inside VMs

Running post-transaction hooks...
Reloading system manager configuration...                                  [1/6]
Arming ConditionNeedsUpdate...                                             [2/6]
Install DKMS modules                                                       [3/6]
==> dkms install --no-depmod -m vmware-workstation -v 16.1.0_17198959 -k 5.9.10-1-MANJARO
==> depmod 5.9.10-1-MANJARO
==> Unable to install module vmware-workstation/16.1.0_17198959 for kernel 5.10.0-1-MANJARO: Missing kernel modules tree.
Updating icon theme caches...                                              [4/6]
Updating the desktop file MIME type cache...                               [5/6]
Updating the MIME type database...                                         [6/6]
Transaction successfully finished.

These are the instructions to get VMware working.

modprobe -a vmw_vmci vmmon

If you need the vm to have network access (add --enable) if you want any of the service to start at boot.

systemctl enable vmware-networks

If you need to pass on USB device into the vm

systemctl enable vmware-usbarbitrator

If that doesn’t do it you need to contact vmware support - after all it is a paid service - but as I said Arch based distribution are unsupported by VMware.

1 Like

Could not connect ‘Ethernet0’ to virtual network ‘/dev/vmnet8’. More information can be found in the vmware.log file.
Failed to connect virtual device ‘Ethernet0’.

That’s what I get

This is a configuration issue of your vm.

Example from my system

● vmware-networks.service - VMware Networks
     Loaded: loaded (/usr/lib/systemd/system/vmware-networks.service; disabled; vendor preset: disabled)
     Active: active (running) since Mon 2020-11-23 16:14:37 CET; 10s ago
    Process: 58344 ExecStartPre=/sbin/modprobe vmnet (code=exited, status=0/SUCCESS)
    Process: 58346 ExecStart=/usr/bin/vmware-networks --start (code=exited, status=0/SUCCESS)
      Tasks: 6 (limit: 77017)
     Memory: 2.4M
     CGroup: /system.slice/vmware-networks.service
             ├─58364 /usr/bin/vmnet-bridge -s 6 -d /var/run/vmnet-bridge-0.pid -n 0
             ├─58373 /usr/bin/vmnet-netifup -s 6 -d /var/run/vmnet-netifup-vmnet1.pid /dev/vmnet1 vmnet1
             ├─58377 /usr/bin/vmnet-dhcpd -s 6 -cf /etc/vmware/vmnet1/dhcpd/dhcpd.conf -lf /etc/vmware/vmnet1/dhcpd/dhc>
             ├─58380 /usr/bin/vmnet-natd -s 6 -m /etc/vmware/vmnet8/nat.mac -c /etc/vmware/vmnet8/nat/nat.conf
             ├─58382 /usr/bin/vmnet-netifup -s 6 -d /var/run/vmnet-netifup-vmnet8.pid /dev/vmnet8 vmnet8
             └─58385 /usr/bin/vmnet-dhcpd -s 6 -cf /etc/vmware/vmnet8/dhcpd/dhcpd.conf -lf /etc/vmware/vmnet8/dhcpd/dhc>

nov 23 16:14:37 ts vmnet-natd[58380]: RTM_NEWROUTE: index:2
nov 23 16:14:37 ts vmnet-natd[58380]: RTM_NEWADDR: index:2, addr:172.30.30.20
nov 23 16:14:37 ts vmware-networks[58346]: Started Bridge networking on vmnet0
nov 23 16:14:37 ts vmware-networks[58346]: Enabled hostonly virtual adapter on vmnet1
nov 23 16:14:37 ts vmware-networks[58346]: Started DHCP service on vmnet1
nov 23 16:14:37 ts vmware-networks[58346]: Started NAT service on vmnet8
nov 23 16:14:37 ts vmware-networks[58346]: Enabled hostonly virtual adapter on vmnet8
nov 23 16:14:37 ts vmware-networks[58346]: Started DHCP service on vmnet8

It’s fixed now. I set to NAT after reboot …

Thanks for help :wink:

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.