VMware Workstation 17 External Hardware Connection Issues

Hey everyone,

Before we get started with the question, here is the inxi....

 ╭─fenris@fenris in ~ took 11ms
 ╰─λ garuda-inxi
System:
  Kernel: 6.1.52-1-lts arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc available: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-lts
    root=UUID=0aec1b80-acf5-4c03-b7ec-23a5b53001b6 rw rootflags=subvol=@
    quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0
    resume=UUID=d0305655-a1d7-4f5a-9bad-37ed6b2bfae4 loglevel=3 ibt=off
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm
    v: 4.18.0 vt: 7 dm: LightDM v: 1.32.0 Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME B250M-C v: Rev X.0x
    serial: <superuser required> UEFI: American Megatrends v: 0404
    date: 12/28/2016
CPU:
  Info: model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake
    gen: core 7 level: v3 note: check built: 2018 process: Intel 14nm family: 6
    model-id: 0x9E (158) stepping: 9 microcode: 0xF4
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
    L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB
    L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 3900 min/max: 800/3900 scaling: driver: intel_pstate
    governor: performance cores: 1: 3900 2: 3900 3: 3900 4: 3900 bogomips: 31211
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel HD Graphics 630 vendor: ASUSTeK driver: i915 v: kernel
    arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: HDMI-A-3
    empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5912
    class-ID: 0300
  Display: x11 server: X.Org v: 21.1.8 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting alternate: fbdev,intel,vesa dri: iris gpu: i915
    display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93")
  Monitor-1: HDMI-A-3 mapped: HDMI-3 model: Acer G247HYL serial: <filter>
    built: 2016 res: 1920x1080 hz: 60 dpi: 93 gamma: 1.2
    size: 527x296mm (20.75x11.65") diag: 604mm (23.8") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  API: OpenGL Message: Unable to show GL data. Required tool glxinfo
    missing.
Audio:
  Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a2f0
    class-ID: 0403
  API: ALSA v: k6.1.52-1-lts status: kernel-api tools: N/A
  Server-1: PipeWire v: 0.3.79 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
  IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel 82571EB/82571GB Gigabit Ethernet D0/D1
    vendor: Hewlett-Packard NC360T Dual Port Server driver: e1000e v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 4 port: e020 bus-ID: 01:00.0
    chip-ID: 8086:105e class-ID: 0200
  IF: enp1s0f0 state: down mac: <filter>
  Device-3: Intel 82571EB/82571GB Gigabit Ethernet D0/D1
    vendor: Hewlett-Packard NC360T Dual Port Server driver: e1000e v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 4 port: e000 bus-ID: 01:00.1
    chip-ID: 8086:105e class-ID: 0200
  IF: enp1s0f1 state: down mac: <filter>
Drives:
  Local Storage: total: 3.64 TiB used: 758.6 GiB (20.4%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital
    model: WD40EFPX-68C6CN0 size: 3.64 TiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5400 serial: <filter>
    fw-rev: 0A81 scheme: GPT
Partition:
  ID-1: / raw-size: 500 GiB size: 500 GiB (100.00%) used: 31.36 GiB (6.3%)
    fs: btrfs dev: /dev/sda3 maj-min: 8:3
  ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
    used: 576 KiB (0.1%) fs: vfat dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 1.14 TiB size: 1.14 TiB (100.00%)
    used: 302.19 GiB (25.8%) fs: btrfs dev: /dev/sda4 maj-min: 8:4
  ID-4: /var/log raw-size: 500 GiB size: 500 GiB (100.00%)
    used: 31.36 GiB (6.3%) fs: btrfs dev: /dev/sda3 maj-min: 8:3
  ID-5: /var/tmp raw-size: 500 GiB size: 500 GiB (100.00%)
    used: 31.36 GiB (6.3%) fs: btrfs dev: /dev/sda3 maj-min: 8:3
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 23.35 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 4 dev: /dev/zram0
  ID-2: swap-2 type: partition size: 6 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/sda2 maj-min: 8:2
Sensors:
  System Temperatures: cpu: 40.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Processes: 292 Uptime: 22m wakeups: 0 Memory: total: 24 GiB
  available: 23.35 GiB used: 6.2 GiB (26.6%) Init: systemd v: 254
  default: graphical tool: systemctl Compilers: gcc: 13.2.1 Packages:
  pm: pacman pkgs: 1694 libs: 416 tools: pamac,paru,yay Shell: Bash v: 5.1.16
  running-in: xfce4-terminal inxi: 3.3.29
Garuda (2.6.16-1):
  System install date:     2023-08-25
  Last full system update: 2023-09-09
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       No/Undetected
  Failed units:            

 ╭─fenris@fenris in ~ took 1s
 ╰─λ 

Ok so here is the issue, I have been using an older version of Garuda for a number of years now without incident and I was using VMware Workstation 17 on it quite nicely until one day a power outage came and nuked my hard drive out of existence. This forced me to get a new hard drive and load up the latest and greatest version of Garuda. I don't know if this matters or not, but just FYI, I'm using the XFCE version. So far, I have to compliment the developers, because I am still beyond impressed with this operating system. Absolutely everything works flawlessly fast without incident, except for VMware Workstation. I'm not sure if this is a Garuda issue or not but I thought I would start here at this forum.

Lucky for me, my VM that I was using with the older version of Garuda is on a hard drive with a USB 3 port so I can keep it portable. It worked nicely before, and it still works the way I need it to when I go to a machine with windows loaded on it. However, now that I have this newly loaded version of Garuda, I'm starting to get problems were none of my hardware is accessible. No DVD drive, no sound adaptor, no network access, nothing which leads me to think that I did or didn't do something to Garuda settings to make this problem surface.

I have provided a few screen shots to show you what I mean:


If My links don't work, sorry. I'm unable to upload the picture for public access

I move from Newbies to Xfce
but maybe it is Unsupported Software (AUR & Other)

Well it worked

Well it worked before, why would it be any different now? It’s available for install in pacman so I would assume that everything in there is all good to go for install when called up in a terminal

Who knows? :slight_smile:

Well…that’s no good. >.<

No idea’s come to mind?

Do you have VMWare tools installed in the guest?

There are systemd services you can set up as well for device and networking passthrough, check out the wiki article here:

https://wiki.archlinux.org/title/VMware#systemd_services

1 Like

Yes I do, and it’s up to date. The problem is when you look at the screen shots I linked, you can’t get a NIC, a sound adapter, or anything USB into the interface from Garuda.

I’m not going to lie, I appreciate the link and all, but I don’t fully understand enough of what is actually going on here, or what to do about it. This is part of the reason why I had originally posted this in the newbie forum before it was moved here

Have you tried different kernels, yet? I see you’re running the LTS.

1 Like

No I have not, I just downloaded the XFCE version of Garuda, and followed the install instructions. I used XFCE for all versions of linux I ever used, and never deviated. I don’t know what you mean by different kernals or how to install them or even change them without stripping the hard drive clean just to start over again.

Why would you strip your HDD clean just to change kernels… Download a different kernel you wanna test along with it’s headers (they are important since they contain libraries for the kernel to work) then reboot and from grub menu go to “advanced settings for garuda linux” and choose the kernel you desire.

For example, you want linux mainline kernel,

sudo pacman -S linux linux-headers

reboot and while in grub use your arrow keys to navigate to “advanced menu” and hit enter to enter in the said menu. There you would see three different entries for each kernel

garuda linux with linux-lts
garuda linux with linux-lts (recovery)
garuda-linux with linux-lts (fallback)
garuda linux with linux
garuda linux with linux (recovery)
garuda linux with linux (fallback)

Not exactly the same but you get the idea. Use your arrow keys to move down the list and select garuda linux with linux to boot with the mainline kernel. You can check the kernel you are using, using the command

uname -r

Note; The recovery and fallback entries are the same kernels with recovery and fallback initramfs, the thing that loads modules at startup and basically used to troubleshoot broken systems.

Well…I did what you suggested…

fenris@fenris in ~ took 11ms
 ╰─λ uname -r
6.4.12-arch1-1

 ╭─fenris@fenris in ~ took 5ms
 ╰─λ garuda-inxi
System:
  Kernel: 6.4.12-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc available: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux
    root=UUID=0aec1b80-acf5-4c03-b7ec-23a5b53001b6 rw rootflags=subvol=@
    quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0
    resume=UUID=d0305655-a1d7-4f5a-9bad-37ed6b2bfae4 loglevel=3 ibt=off
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm
    v: 4.18.0 vt: 7 dm: LightDM v: 1.32.0 Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME B250M-C v: Rev X.0x
    serial: <superuser required> UEFI: American Megatrends v: 0404
    date: 12/28/2016
CPU:
  Info: model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake
    gen: core 7 level: v3 note: check built: 2018 process: Intel 14nm family: 6
    model-id: 0x9E (158) stepping: 9 microcode: 0xF4
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
    L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB
    L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 3900 high: 3901 min/max: 800/3900 scaling:
    driver: intel_pstate governor: performance cores: 1: 3900 2: 3901 3: 3900
    4: 3900 bogomips: 31211
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel HD Graphics 630 vendor: ASUSTeK driver: i915 v: kernel
    arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: HDMI-A-3
    empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5912
    class-ID: 0300
  Display: x11 server: X.Org v: 21.1.8 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting alternate: fbdev,intel,vesa dri: iris gpu: i915
    display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93")
  Monitor-1: HDMI-A-3 mapped: HDMI-3 model: Acer G247HYL serial: <filter>
    built: 2016 res: 1920x1080 hz: 60 dpi: 93 gamma: 1.2
    size: 527x296mm (20.75x11.65") diag: 604mm (23.8") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  API: OpenGL Message: Unable to show GL data. Required tool glxinfo
    missing.
Audio:
  Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3
    chip-ID: 8086:a2f0 class-ID: 0403
  API: ALSA v: k6.4.12-arch1-1 status: kernel-api tools: N/A
  Server-1: PipeWire v: 0.3.79 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
  IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel 82571EB/82571GB Gigabit Ethernet D0/D1
    vendor: Hewlett-Packard NC360T Dual Port Server driver: e1000e v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 4 port: e020 bus-ID: 01:00.0
    chip-ID: 8086:105e class-ID: 0200
  IF: enp1s0f0 state: down mac: <filter>
  Device-3: Intel 82571EB/82571GB Gigabit Ethernet D0/D1
    vendor: Hewlett-Packard NC360T Dual Port Server driver: e1000e v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 4 port: e000 bus-ID: 01:00.1
    chip-ID: 8086:105e class-ID: 0200
  IF: enp1s0f1 state: down mac: <filter>
Drives:
  Local Storage: total: 3.64 TiB used: 1.28 TiB (35.1%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital
    model: WD40EFPX-68C6CN0 size: 3.64 TiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5400 serial: <filter>
    fw-rev: 0A81 scheme: GPT
Partition:
  ID-1: / raw-size: 500 GiB size: 500 GiB (100.00%) used: 31.43 GiB (6.3%)
    fs: btrfs dev: /dev/sda3 maj-min: 8:3
  ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
    used: 576 KiB (0.1%) fs: vfat dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 1.14 TiB size: 1.14 TiB (100.00%)
    used: 302.18 GiB (25.8%) fs: btrfs dev: /dev/sda4 maj-min: 8:4
  ID-4: /var/log raw-size: 500 GiB size: 500 GiB (100.00%)
    used: 31.43 GiB (6.3%) fs: btrfs dev: /dev/sda3 maj-min: 8:3
  ID-5: /var/tmp raw-size: 500 GiB size: 500 GiB (100.00%)
    used: 31.43 GiB (6.3%) fs: btrfs dev: /dev/sda3 maj-min: 8:3
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 23.35 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 4 dev: /dev/zram0
  ID-2: swap-2 type: partition size: 6 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/sda2 maj-min: 8:2
Sensors:
  System Temperatures: cpu: 49.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Processes: 291 Uptime: 14m wakeups: 0 Memory: total: 24 GiB
  available: 23.35 GiB used: 5.56 GiB (23.8%) Init: systemd v: 254
  default: graphical tool: systemctl Compilers: gcc: 13.2.1 Packages:
  pm: pacman pkgs: 1697 libs: 417 tools: pamac,paru,yay Shell: Bash v: 5.1.16
  running-in: xfce4-terminal inxi: 3.3.29
Garuda (2.6.16-1):
  System install date:     2023-08-25
  Last full system update: 2023-09-10
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       No/Undetected
  Failed units:            

 ╭─fenris@fenris in ~ took 2s
 ╰─λ 

However, that didn’t fix the problem :disappointed_relieved:

It is very important that you do your own research…Google is handy, so is this and other forums, the Garuda & Arch wikis, etc. The point being, there is a wide venue of help available.

Then please tell us what your research found, what you read, what you attempted and those results and what you did not.

Otherwise it is a game of “64 Questions” and helpers quickly tire of that. It also can lead to Help Vampirism and nobody wants to get bled dry.
:slight_smile:

2 Likes

The article is describing some systemd services that can be set up which may be helpful. Some of the services may already exist if you installed the vmware-workstation package and may only need to be enabled.

To set up one of these services, create the file using the path in the wiki article:

sudo micro /etc/systemd/system/vmware.service

Paste in the contents of the service:

[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

Press Ctrl+Q to quit out of Micro–be sure to save the file.

Then set up the other services.

sudo micro /etc/systemd/system/vmware-usbarbitrator.service
Paste:
[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
sudo micro /etc/systemd/system/vmware-networks-server.service
Paste:
[Unit]
Description=VMware Networks
Wants=vmware-networks-configuration.service
After=vmware-networks-configuration.service

[Service]
Type=forking
ExecStartPre=-/sbin/modprobe vmnet
ExecStart=/usr/bin/vmware-networks --start
ExecStop=/usr/bin/vmware-networks --stop

[Install]
WantedBy=multi-user.target

The last one you may or may not want. It is for connecting to your VMware Workstation installation from another Workstation Server Console. If you don’t need it, just skip it.

If you want to add the service for VMware Workstation Server:
sudo micro /etc/systemd/system/vmware-workstation-server.service

Paste in the service:

[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
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target

Then start and enable the services.

sudo systemctl enable --now vmware.service vmware-usbarbitrator.service 
vmware-networks-server.service 

Add vmware-workstation-server.service to the list as well if you decided to set up that service.

A reboot may be in order, I’m honestly not sure if it is needed but it can’t hurt. Then fire up the VM and test again. :crossed_fingers:

1 Like

Well, your right, perhaps I could have done some more research before I asked. I started out with this could no connect 'ethernet 0' to virtual network '... - VMware Technology Network VMTN because it was (at least on the surface) one of many problems I was having so I figured I should start there.

Then I started looking at this VMware - ArchWiki which was kind of pointed out to me already. Problem is, I was kind of overwhelmed with everything listed here and didn’t know how to process mentally the information being provided.

Then I started looking here for answers https://linuxconfig.org/install-arch-linux-in-vmware-workstation, but noticed this was an older version and figured there maybe some conflicts to deal with.

Now, I have used other forums before like the Arch forums. Why I don’t use it is because every time I have a question, it’s like someone is always beating me over the head with forum policies and I can’t seem to clue in what I am doing that is so wrong and getting people upset with me there. This is why I gave up on raw Arch cause the support isn’t there if I can’t ask a question. I was having the same problem with the Debian forums as well. It’s like the ego in people came out, and they would talk down to you for asking a question. That is why I am here using Garuda. Everything just seems to magically work somehow. Sometimes some people need little tweaks in how information is being presented so it’s not so overwhelming. This forum layout with all the dark colours seems to help re-orientate how information gets presented which goes a long way.

You know what…I think this did the job. I loaded up the virtual machine, it has internet access, sound plays through it, and it forwarded a USB drive right into the VM. Its just the icons on the bottom right corner of the screen have little red x’s on them which makes them look on the indicators that there disconnected which is deceiving. A bug perhaps? Who knows, that’s extra. It seems to work and that’s enough for me I guess.

╭─fenris@fenris in ~ 17m4s
 ╰─λ systemctl list-units --type=service --all
  UNIT                                                  LOAD      ACTIVE   SUB >
  accounts-daemon.service                               loaded    active   runn>
● acpid.service                                         not-found inactive dead>
  ananicy-cpp.service                                   loaded    active   runn>
● apparmor.service                                      not-found inactive dead>
  archlinux-keyring-wkd-sync.service                    loaded    inactive dead>
  auditd.service                                        loaded    inactive dead>
  avahi-daemon.service                                  loaded    active   runn>
  btrfs-balance.service                                 loaded    inactive dead>
  btrfs-defrag.service                                  loaded    inactive dead>
  btrfs-scrub.service                                   loaded    inactive dead>
  btrfs-trim.service                                    loaded    inactive dead>
  cups.service                                          loaded    active   runn>
  dbus.service                                          loaded    active   runn>
  dm-event.service                                      loaded    inactive dead>
  dracut-cmdline.service                                loaded    inactive dead>
  dracut-initqueue.service                              loaded    inactive dead>
  dracut-mount.service                                  loaded    inactive dead>
  dracut-pre-mount.service                              loaded    inactive dead>
  dracut-pre-pivot.service                              loaded    inactive dead>
  dracut-pre-trigger.service                            loaded    inactive dead>
  dracut-pre-udev.service                               loaded    inactive dead>
  dracut-shutdown-onfailure.service                     loaded    inactive dead>
  dracut-shutdown.service                               loaded    active   exit>
  emergency.service                                     loaded    inactive dead>
  fstrim.service                                        loaded    inactive dead>
  garuda-pacman-lock.service                            loaded    inactive dead>
  garuda-pacman-snapshot-reject.service                 loaded    inactive dead>
  [email protected]                                    loaded    inactive dead>
  grub-btrfs-snapper.service                            loaded    inactive dead>
  initrd-cleanup.service                                loaded    inactive dead>
  initrd-parse-etc.service                              loaded    inactive dead>
  initrd-switch-root.service                            loaded    inactive dead>
  initrd-udevadm-cleanup-db.service                     loaded    inactive dead>
  ipp-usb.service                                       loaded    inactive dead>
  irqbalance.service                                    loaded    active   runn>
● iscsid.service                                        not-found inactive dead>
  kmod-static-nodes.service                             loaded    active   exit>
  ldconfig.service                                      loaded    inactive dead>
  libvirtd.service                                      loaded    inactive dead>
  lightdm.service                                       loaded    active   runn>
  linux-modules-cleanup.service                         loaded    inactive dead>
  logrotate.service                                     loaded    inactive dead>
  lvm2-lvmpolld.service                                 loaded    inactive dead>
  lvm2-monitor.service                                  loaded    active   exit>
  man-db.service                                        loaded    inactive dead>
  ModemManager.service                                  loaded    active   runn>
  [email protected]                             loaded    inactive dead>
  modprobe@dm_mod.service                               loaded    inactive dead>
  [email protected]                                  loaded    inactive dead>
  [email protected]                                 loaded    inactive dead>
  [email protected]                                 loaded    inactive dead>
  NetworkManager-wait-online.service                    loaded    active   exit>
  NetworkManager.service                                loaded    active   runn>
  nmb.service                                           loaded    active   runn>
● nslcd.service                                         not-found inactive dead>
  pamac-cleancache.service                              loaded    inactive dead>
  pamac-daemon.service                                  loaded    active   runn>
  plymouth-quit-wait.service                            loaded    active   exit>
  plymouth-quit.service                                 loaded    active   exit>
  plymouth-read-write.service                           loaded    active   exit>
  plymouth-start.service                                loaded    active   exit>
  plymouth-switch-root.service                          loaded    inactive dead>
  polkit.service                                        loaded    active   runn>
  preload.service                                       loaded    active   runn>
● rc-local.service                                      not-found inactive dead>
  rescue.service                                        loaded    inactive dead>
  rtkit-daemon.service                                  loaded    active   runn>
  shadow.service                                        loaded    inactive dead>
  smb.service                                           loaded    active   runn>
  snapper-cleanup.service                               loaded    inactive dead>
● syslog.service                                        not-found inactive dead>
  systemd-ask-password-console.service                  loaded    inactive dead>
  systemd-ask-password-plymouth.service                 loaded    inactive dead>
  systemd-ask-password-wall.service                     loaded    inactive dead>
  systemd-battery-check.service                         loaded    inactive dead>
  systemd-binfmt.service                                loaded    active   exit>
  systemd-boot-random-seed.service                      loaded    inactive dead>
  systemd-firstboot.service                             loaded    inactive dead>
  systemd-fsck-root.service                             loaded    inactive dead>
  systemd-fsck@dev-disk-by\x2duuid-7716\x2d2516.service loaded    active   exit>
  systemd-hwdb-update.service                           loaded    inactive dead>
  systemd-journal-catalog-update.service                loaded    inactive dead>
  systemd-journal-flush.service                         loaded    active   exit>
  systemd-journald.service                              loaded    active   runn>
  systemd-logind.service                                loaded    active   runn>
  systemd-machine-id-commit.service                     loaded    inactive dead>
  systemd-machined.service                              loaded    active   runn>
  systemd-modules-load.service                          loaded    active   exit>
  systemd-oomd.service                                  loaded    active   runn>
  systemd-pcrmachine.service                            loaded    inactive dead>
  systemd-pcrphase-initrd.service                       loaded    inactive dead>
  systemd-pcrphase-sysinit.service                      loaded    inactive dead>
  systemd-pcrphase.service                              loaded    inactive dead>
  systemd-quotacheck.service                            loaded    inactive dead>
  systemd-random-seed.service                           loaded    active   exit>
  systemd-remount-fs.service                            loaded    active   exit>
  systemd-repart.service                                loaded    inactive dead>
  systemd-rfkill.service                                loaded    inactive dead>
  systemd-sysctl.service                                loaded    active   exit>
  systemd-sysext.service                                loaded    inactive dead>
  systemd-sysusers.service                              loaded    inactive dead>
  systemd-timesyncd.service                             loaded    active   runn>
  systemd-tmpfiles-clean.service                        loaded    inactive dead>
  systemd-tmpfiles-setup-dev-early.service              loaded    active   exit>
  systemd-tmpfiles-setup-dev.service                    loaded    active   exit>
  systemd-tmpfiles-setup.service                        loaded    active   exit>
  systemd-udev-settle.service                           loaded    inactive dead>
  systemd-udev-trigger.service                          loaded    active   exit>
  systemd-udevd.service                                 loaded    active   runn>
  systemd-update-done.service                           loaded    inactive dead>
  systemd-update-utmp.service                           loaded    active   exit>
  systemd-user-sessions.service                         loaded    active   exit>
  systemd-vconsole-setup.service                        loaded    active   exit>
  [email protected]                      loaded    active   exit>
  udisks2.service                                       loaded    active   runn>
  updatedb.service                                      loaded    inactive dead>
  upower.service                                        loaded    active   runn>
  [email protected]                         loaded    active   exit>
  [email protected]                                     loaded    active   runn>
  virtlockd.service                                     loaded    inactive dead>
  virtlogd.service                                      loaded    inactive dead>
  vmware-networks-configuration.service                 loaded    inactive dead>
  vmware-networks-server.service                        loaded    active   runn>
  vmware-usbarbitrator.service                          loaded    active   exit>
● vmware.service                                        loaded    failed   fail>
  winbind.service                                       loaded    inactive dead>
● xencommons.service                                    not-found inactive dead>
● xendomains.service                                    not-found inactive dead>

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
128 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.
~
~
~
~
lines 113-135/135 (END)

I don’t know if this has something to do with the icons looking weird, vmware.service failed

Glad to hear it. :slightly_smiling_face:

What does “systemctl status vmware.service” say?

Check if you have the script it is trying to call in that directory.

ls /etc/init.d/

If you specified a different directory for the system service scripts during installation (/etc/init.d is the default), you will have to amend your service to point to that directory.

1 Like
fenris@fenris in ~ took 66ms
 ╰─λ systemctl status vmware.service
× vmware.service - VMware daemon
     Loaded: loaded (/etc/systemd/system/vmware.service; enabled; preset: disab>
     Active: failed (Result: exit-code) since Sun 2023-09-10 15:41:54 CDT; 4h 3>
   Duration: 3ms
   Main PID: 684 (code=exited, status=203/EXEC)
        CPU: 1ms

Sep 10 15:41:54 fenris-garuda systemd[1]: Started VMware daemon.
Sep 10 15:41:54 fenris-garuda (vmware)[684]: vmware.service: Failed to locate e>
Sep 10 15:41:54 fenris-garuda (vmware)[684]: vmware.service: Failed at step EXE>
Sep 10 15:41:54 fenris-garuda systemd[1]: vmware.service: Main process exited, >
Sep 10 15:41:54 fenris-garuda systemd[1]: vmware.service: Failed with result 'e>


 ╭─fenris@fenris in ~ took 9s
[🧱] × 
╭─fenris@fenris in ~ took 6ms
[🧱] × ls /etc/init.d/
ls: cannot access '/etc/init.d/': No such file or directory

 ╭─fenris@fenris in ~ took 16ms
[🔴] × 

Doesn’t look like I have one :unamused:

Did you install VMware with Pacman (vmware-workstation is in the ChaoticAUR), or some other way? My understanding is setting the system service scripts directory as /etc/init.d is the default, but if you installed it off their website or something they may set it up differently (I’m honestly not sure).

You can try searching for the script:

sudo find / -name vmware

You might get a lot of unhelpful returns on that search because they decided to just name the script “vmware” (:unamused:) but hopefully it won’t be a needle in a haystack.

Yes I used pacman. I learned that lesson before on this forum already when I didn’t use pacman and then came here looking for help when an update made it malfunction. Got the smack down for that one.

Your right…if you want to see what happened…

 ╭─fenris@fenris in ~ took 16ms
[🔴] × 
sudo find / -name vmware
find-the-command: "╭─fenris@fenris" is not found locally, searching in repositories...
find-the-command: /var/lib/pacman/sync/*.files are out of date, update? [Y/n] 
[sudo] password for fenris:         
:: Synchronizing package databases...
 garuda is up to date
 core is up to date
 extra                  38.2 MiB  82.6 KiB/s 07:53 [----------------------] 100%
 multilib is up to date
 chaotic-aur            51.2 MiB   172 KiB/s 05:05 [----------------------] 100%
 blackarch is up to date
find-the-command: command not found: "╭─fenris@fenris"
find-the-command: "[🧱]" is not found locally, searching in repositories...
find-the-command: command not found: "[🧱]"
find-the-command: "ls:" is not found locally, searching in repositories...
find-the-command: command not found: "ls:"
find-the-command: "╭─fenris@fenris" is not found locally, searching in repositories...
find-the-command: command not found: "╭─fenris@fenris"
find-the-command: "[🔴]" is not found locally, searching in repositories...
find-the-command: command not found: "[🔴]"
[sudo] password for fenris:         
/root/.cache/vmware
/var/log/vmware
/var/lib/vmware
/home/fenris/.cache/vmware
/run/vmware
find: ‘/run/user/1000/doc’: Permission denied
find: ‘/run/user/1000/gvfs’: Permission denied
/etc/conf.d/vmware
/etc/vmware
/usr/bin/vmware
/usr/lib/vmware
/usr/lib/vmware/bin/vmware
/usr/lib/vmware-ovftool/schemas/vmware
/.snapshots/85/snapshot/var/lib/vmware
/.snapshots/85/snapshot/etc/conf.d/vmware
/.snapshots/85/snapshot/etc/vmware
/.snapshots/85/snapshot/usr/bin/vmware
/.snapshots/85/snapshot/usr/lib/vmware
/.snapshots/85/snapshot/usr/lib/vmware/bin/vmware
/.snapshots/85/snapshot/usr/lib/vmware-ovftool/schemas/vmware
/.snapshots/86/snapshot/var/lib/vmware
/.snapshots/86/snapshot/etc/conf.d/vmware
/.snapshots/86/snapshot/etc/vmware
/.snapshots/86/snapshot/usr/bin/vmware
/.snapshots/86/snapshot/usr/lib/vmware
/.snapshots/86/snapshot/usr/lib/vmware/bin/vmware
/.snapshots/86/snapshot/usr/lib/vmware-ovftool/schemas/vmware
/.snapshots/87/snapshot/var/lib/vmware
/.snapshots/87/snapshot/etc/conf.d/vmware
/.snapshots/87/snapshot/etc/vmware
/.snapshots/87/snapshot/usr/bin/vmware
/.snapshots/87/snapshot/usr/lib/vmware
/.snapshots/87/snapshot/usr/lib/vmware/bin/vmware
/.snapshots/87/snapshot/usr/lib/vmware-ovftool/schemas/vmware
/.snapshots/88/snapshot/var/lib/vmware
/.snapshots/88/snapshot/etc/conf.d/vmware
/.snapshots/88/snapshot/etc/vmware
/.snapshots/88/snapshot/usr/bin/vmware
/.snapshots/88/snapshot/usr/lib/vmware
/.snapshots/88/snapshot/usr/lib/vmware/bin/vmware
/.snapshots/88/snapshot/usr/lib/vmware-ovftool/schemas/vmware
/.snapshots/89/snapshot/var/lib/vmware
/.snapshots/89/snapshot/etc/conf.d/vmware
/.snapshots/89/snapshot/etc/vmware
/.snapshots/89/snapshot/usr/bin/vmware
/.snapshots/89/snapshot/usr/lib/vmware
/.snapshots/89/snapshot/usr/lib/vmware/bin/vmware
/.snapshots/89/snapshot/usr/lib/vmware-ovftool/schemas/vmware
/.snapshots/90/snapshot/var/lib/vmware
/.snapshots/90/snapshot/etc/conf.d/vmware
/.snapshots/90/snapshot/etc/vmware
/.snapshots/90/snapshot/usr/bin/vmware
/.snapshots/90/snapshot/usr/lib/vmware
/.snapshots/90/snapshot/usr/lib/vmware/bin/vmware
/.snapshots/90/snapshot/usr/lib/vmware-ovftool/schemas/vmware
/.snapshots/91/snapshot/var/lib/vmware
/.snapshots/91/snapshot/etc/conf.d/vmware
/.snapshots/91/snapshot/etc/vmware
/.snapshots/91/snapshot/usr/bin/vmware
/.snapshots/91/snapshot/usr/lib/vmware
/.snapshots/91/snapshot/usr/lib/vmware/bin/vmware
/.snapshots/91/snapshot/usr/lib/vmware-ovftool/schemas/vmware
/.snapshots/92/snapshot/var/lib/vmware
/.snapshots/92/snapshot/etc/conf.d/vmware
/.snapshots/92/snapshot/etc/vmware
/.snapshots/92/snapshot/usr/bin/vmware
/.snapshots/92/snapshot/usr/lib/vmware
/.snapshots/92/snapshot/usr/lib/vmware/bin/vmware
/.snapshots/92/snapshot/usr/lib/vmware-ovftool/schemas/vmware
/.snapshots/93/snapshot/var/lib/vmware
/.snapshots/93/snapshot/etc/conf.d/vmware
/.snapshots/93/snapshot/etc/vmware
/.snapshots/93/snapshot/usr/bin/vmware
/.snapshots/93/snapshot/usr/lib/vmware
/.snapshots/93/snapshot/usr/lib/vmware/bin/vmware
/.snapshots/93/snapshot/usr/lib/vmware-ovftool/schemas/vmware
/.snapshots/94/snapshot/var/lib/vmware
/.snapshots/94/snapshot/etc/conf.d/vmware
/.snapshots/94/snapshot/etc/vmware
/.snapshots/94/snapshot/usr/bin/vmware
/.snapshots/94/snapshot/usr/lib/vmware
/.snapshots/94/snapshot/usr/lib/vmware/bin/vmware
/.snapshots/94/snapshot/usr/lib/vmware-ovftool/schemas/vmware
/.snapshots/95/snapshot/var/lib/vmware
/.snapshots/95/snapshot/etc/conf.d/vmware
/.snapshots/95/snapshot/etc/vmware
/.snapshots/95/snapshot/usr/bin/vmware
/.snapshots/95/snapshot/usr/lib/vmware
/.snapshots/95/snapshot/usr/lib/vmware/bin/vmware
/.snapshots/95/snapshot/usr/lib/vmware-ovftool/schemas/vmware
/.snapshots/96/snapshot/var/lib/vmware
/.snapshots/96/snapshot/etc/conf.d/vmware
/.snapshots/96/snapshot/etc/vmware
/.snapshots/96/snapshot/usr/bin/vmware
/.snapshots/96/snapshot/usr/lib/vmware
/.snapshots/96/snapshot/usr/lib/vmware/bin/vmware
/.snapshots/96/snapshot/usr/lib/vmware-ovftool/schemas/vmware

 ╭─fenris@fenris in ~ as 🧙 took 9m18s
[🔴] × 

LOL, I feel your pain. The Arch forums are specific to Arch as far as asking questions go, but a wonderful resource on what-the-heck-is-going-on-now? research. Ever have a new problem crop up suddenly? Well, you’re probably not on your own. And there is where you’ll find help. But, yeah, that’s Arch-specific. However, the Arch Wiki is considered by some to be a Linux compendium GOAT resource. And Garuda is Garuda, and our forums and wiki work just swell. :slight_smile:

I couldn’t agree with you more about the official Debian Forums, where I was a member pre-Arch and ran Debian Testing. Those swelled-headed bigots consider anyone an unwashed, dumb novice who hasn’t run Debian since it was Deb & Ian.

But thank you very much for listing your resources, what you’ve tried, etc. That carries a lot of the weight that might have burdoned helpers with duplication. And time is a lot more precious than money, trust me on that. :wink:

Yer doing great, pardner. :smiley:

2 Likes

These ones look promising. You could try using these paths against the “start” argument and see if any of them are the right script.

/etc/conf.d/vmware start
/etc/vmware start

And so on.

I am guessing it will provide some kind of output if the command works, although I must admit I don’t really know.

2 Likes