VMware Communities
johnsig
Contributor
Contributor

My solution to the "/dev/vmmon: Broken pipe" error

Yesterday I got the "/dev/vmmon: Broken pipe" error when tried to fire up my VM running on Mojave 10.14.6.

After trying all sorts of things suggested in this forum, including uninstalling and reinstalling multiple times, turning SIP off and on, disabling anti-virus monitoring, etc., etc., all to no avail, I thought back on recent applications I've installed that required security clearance.

The most recent one of those I installed was just the day before, namely Google Drive FileStream. So I uninstalled both that app and VMWare Fusion, shutdown, booted back up again, and reinstalled Fusion. And voilà, the error went away and I could start the VM.

As an additional test, I then reinstalled Google Drive FileStream, and then tried Fusion. The "/dev/vmmon: Broken pipe" error reappeared. And then I once again uninstalled Google Drive FileStream, rebooted, ran Fusion (without reinstalling), and the error is gone.

So it's rather certain that Google Drive FileStream breaks VMWare Fusion.

1 Reply
djr36
Contributor
Contributor

And annoyingly it seems that fixing VMware Fusion breaks Google Drive in my case. 

Reply
0 Kudos