Obviously, this post is MacOS-specific. This is about when Fusion throws the dreaded
/dev/vmmon: broken pipe
or
/dev/vmmon: No such file or directory
Here are three different fixes, because this is definitely nor a “one size fits all” scenario:
1-If Fusion complains about not being authorized
Go to the Security and Privacy control panel; make sure that both App Store and signed applications are authorized; check that Fusion is not explicitely blacklisted.
2-Starting with Mojave: is disk access authorized?
In the same control panel, go to the Privacy tab and make sure that Fusion is allowed to write to disk…
3-If Fusion still complains about not being authorized
Check if it’s because the image itself got quarantined: run
xattr -l ~/Downloads/VMware-Fusion-*.dmg | grep quarantine
If you are getting any output, this is going to be a bit more work: you need to uninstall Fusion; run the command below; re-install Fusion:
xattr -dr com.apple.quarantine ~/Downloads/VMware-Fusion-*.dmg
4-If that still did not help
Maybe you have loaded too many kernel extensions (kext files) – this can happen easily if you also installed VirtualBox, Parallels, etc.
Run:
kextstat | grep com.vmware | awk '{print $6}'
You should get something similar to:
com.vmware.kext.vmci
com.vmware.kext.vmnet
com.vmware.kext.vmx86
com.vmware.kext.vmioplug.18.1.2
If you are getting fewer rows, this could be your issue. Now, you need to select what other software you wish to sacrifice to allow Fusion to work.
Let’s say you decide on VirtualBox. First, remove it from your system. I find something like App Zapper to be quite thorough. Unfortunately, even this little guy will not remove the kexts. You will need to remove them manually.
As super user, run:
for kext in $(ls /Library/Application\ Support/VirtualBox); do
kextutil /Library/Application\ Support/VirtualBox/${kext} \
-r /Library/Application\ Support/VirtualBox;
done
Voila. (I hope!)
Comments powered by Talkyard.