VMware Communities
iridianetes
Contributor
Contributor

VM hangs and gives message when trying to exit "The virtual machine "Fedora 64-bit" is busy."

Hello!

I recently installed VMWare Fusion via Homebrew. The installation succeeded just fine.

```

brew cask install vmware-fusion

```

I opened it up and started a Trial and when trying to run a VM nothing happens at all. No BIOS, nothing. When I try to close the VM I get the message in the title. In order to get the VM to close I have to find the PID and send a SIGTERM, which works and Fusion gives a popup saying things went wrong (expected).

I've tried rebooting.

I've already Allowed Fusion in: System Preferences → Security & Privacy → General

Apps are allowed to run from Identified Developers.

Mac version is: Catalina 10.15

Current version of Fusion is: Professional Version 11.5.0 (14634996)

I do see this file:

```

ls -la /dev/vmmon

crw------- 1 root wheel 36, 0 Oct 27 13:54 /dev/vmmon

```

My current user isn't in the wheel group.

VMWare network interfaces seem to exist:

```

ifconfig | grep vmnet

vmnet1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

vmnet8: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

```

Kernel modules matching VMWare:

```

kextstat | grep vmware

  179    0 0xffffff7f83718000 0x15000    0x15000    com.vmware.kext.vmnet (1463.49.96) 7DA94F7D-B518-3496-8793-E781232B171C <6 5 3 1>

  180    0 0xffffff7f8372d000 0x13000    0x13000    com.vmware.kext.vmx86 (1463.49.96) 768F57A7-655C-3DCE-835D-29966A5CE4D9 <8 6 5 3 1>

  181    0 0xffffff7f82916000 0x7000     0x7000     com.vmware.kext.vmioplug.18.7.0 (18.7.0) 53E03BEC-2BFD-3A6D-B092-A2116987781F <60 6 5 3 1>

```

Processes matching VMWare:

```

ps aux | grep vmware

username          96420   0.0  0.0  4268268    668 s006  S+    2:03PM   0:00.00 grep --color=auto --exclude-dir=.bzr --exclude-dir=CVS --exclude-dir=.git --exclude-dir=.hg --exclude-dir=.svn vmware

root             90809   0.0  0.1  4379772  13276   ??  S     1:54PM   0:00.22 /Users/username/Applications/VMware Fusion.app/Contents/Library/vmware-vmx -E en -s vmx.stdio.keep=TRUE -# product=64;name=VMware Fusion;version=11.5.0;buildnumber=14634996;licensename=VMware Fusion for Mac OS;licenseversion=11.0; -@ duplex=3;msgs=ui -D 4 /Users/username/Virtual Machines.localized/Fedora 64-bit.vmwarevm/Fedora 64-bit.vmx

root             90538   0.0  0.0  4307592   2200   ??  Ss    1:54PM   0:00.17 /Users/username/Applications/VMware Fusion.app/Contents/Library/vmware-usbarbitrator

root             90536   0.0  0.0  4293920    152   ??  Ss    1:54PM   0:00.00 /Users/username/Applications/VMware Fusion.app/Contents/Library/vmnet-dhcpd -s 6 -cf /Library/Preferences/VMware Fusion/vmnet8/dhcpd.conf -lf /var/db/vmware/vmnet-dhcpd-vmnet8.leases -pf /var/run/vmnet-dhcpd-vmnet8.pid vmnet8

root             90529   0.0  0.0  4302112    152   ??  Ss    1:54PM   0:00.00 /Users/username/Applications/VMware Fusion.app/Contents/Library/vmnet-dhcpd -s 6 -cf /Library/Preferences/VMware Fusion/vmnet1/dhcpd.conf -lf /var/db/vmware/vmnet-dhcpd-vmnet1.leases -pf /var/run/vmnet-dhcpd-vmnet1.pid vmnet1

```

In this case, the hanging VM is PID 90809. So, VM's are running as root, which looks like a good sign. Kernel extensions are installed. Everything has been _allowed_ in the Mac settings.

Ideas?

-- Regards

0 Kudos
0 Replies