VMware Communities
abujesus
Contributor
Contributor

VMWare Fusion Professional Version 11.0.3 (12992109) Could not open /dev/vmmon: Broken pipe. Please make sure that the kernel module `vmmon' is loaded.

Hello,

I just upgraded to Mac OS Mojave v10.14.5 Beta (18F108f). Ever since doing that I can no longer start any of my VMs. I'm running VMWare Fusion Professional Version 11.0.3 (12992109). I've allowed VMWare under security & privacy previously and it's not showing as needing to be allowed again. I've uploaded my support info to Google Drive. Any help would be greatly appreciated.

https://drive.google.com/open?id=1m43f2GA9SdHzARAef6AFVfIf_a1qqFgc

0 Kudos
6 Replies
bfan
VMware Employee
VMware Employee

This is a known issue for MacOS 10.14.5 beta, we are working on it now.

The workaround is disable SIP of Mac host,  please refer to https://www.imore.com/how-turn-system-integrity-protection-macos

0 Kudos
Mohannad
Contributor
Contributor

A better solution posted in another thread on the same subject.

New installation of Vmware fusion 11 pro on macos Mojave Could not open /dev/vmmon: Broken pipe

1Click the Apple menu.
2Select Restart...
3Hold down Command-R to boot into the Recovery System.
4Click the Utilities menu and select Terminal.
5Type /usr/sbin/spctl kext-consent add EG7KH642X6 and press return.
6Close the Terminal app.
7Click the Apple menu and select Restart....
0 Kudos
mfat1317
Contributor
Contributor

The solution proposed by Mohannad does not work For VMware Fusion Professional 11.0.3.

I suggest you to downgrade and do not do what proposed before.

ArthurValiev
Contributor
Contributor

Yes. This issue is most probably related to notarisation issues which macOS 10.14.5 beta 2 introduced.

All that the developer needs to do is to submit the kext to Apple for notarisation (even without the whole package including the product). After that, macOS will start accepting it in few minutes.

Here is a note on Apple's website (Notarizing Your App Before Distribution | Apple Developer Documentation

Beginning in macOS 10.14.5, all new or updated kernel extensions and all software from developers new to distributing with Developer ID must be notarized in order to run. In a future version of macOS, notarization will be required by default for all software.

For example, in my case, my machine is a managed office workstation. I do not have access to recovery mode due to company's policy.

Old kexts are still working fine. VMware Fusion Pro 11.0.2 works perfectly fine on the latest macOS beta 2 as its kext was built before March (all kexts updated after March require notarisation).

0 Kudos
mfat1317
Contributor
Contributor

Actually I'm under 10.14.4

0 Kudos
Roy25
Contributor
Contributor

Absolutely true.First of all downgrade your version and then apply above solution..Or else u will be wasting your time and energy both myccpay.com

0 Kudos