1 2 3 Previous Next 40 Replies Latest reply on Aug 14, 2019 6:12 PM by benau_99 Go to original post
      • 30. Re: Could not open /dev/vmmon: Broken pipe.
        Uxian Lurker

        I've tried all of these solutions.  Enabling full disk access worked for me for a single boot and then next time I boot from cold the problem comes back.

         

        If I try to load the driver using kextload I get the following in dmesg:

        vmmon: Loaded com.vmware.kext.vmx86 Version 1366.85.89 Build 13668589 (May 12 2019 14:05:51)

        vmmon: Warning: Failed to register the major device number.

        Kext com.vmware.kext.vmx86 start failed (result 0x5).

        Kext com.vmware.kext.vmx86 failed to load (0xdc008017).

        Failed to load kext com.vmware.kext.vmx86 (error 0xdc008017).

         

        Turns out I just had too many third-party kexts loaded and after I removed a few (SoundFlower, tun and tap VPN drivers) I was then able to load vmmon.

        • 31. Re: Could not open /dev/vmmon: Broken pipe.
          brbaus Lurker

          One tip for folks on Mojave.

           

          Look on the General tab in the Security and Privacy settings. There was a button on that tab that enables vmWare to run. Then it works like a charm.

          • 32. Re: Could not open /dev/vmmon: Broken pipe.
            lurch999 Lurker

            This solution works for cases where the "Allow" button does not appear in Security & Privacy > General:

             

            Using Terminal, get the TeamIdentifier value from the VMWare Fusion version you're using (the % is the prompt, so omit that):

             

               % codesign -dv --verbose=4 /Applications/VMware\ Fusion.app

             

            From the results of that command, find the "TeamIdentifier" value, for example:

             

               TeamIdentifier=EG7KH642X6

             

            Write that down, and note this is case-sensitive.

             

            Reboot your Mac into Recovery Mode (hold down Command + R at boot)

             

            In Recovery Mode, open Terminal, then:

             

              % /usr/sbin/spctl kext-consent add EG7KH642X6

             

            Reboot, and you should be good to go now.

            • 33. Re: Could not open /dev/vmmon: Broken pipe.
              mastlonda Lurker

              SOLVED

              This a complete video tutorial for fix of this error

              You can find it right here:-

              VMware Could not open dev/vmmon | Unable to open kernel device | Failed to initialize monitor device - YouTube

              He has some good and awesome stuff

              • 34. Re: Could not open /dev/vmmon: Broken pipe.
                AndrewBurkhart9W Lurker

                I tried all the other responses I saw in here (Allow in Security & Privacy, allow full disk access, try different things in recovery terminal, etc.) but my issue turned out to be maxing out the number of kernel extensions that can be loaded (at least this is my understanding). I ran 'kextstat' and found some to remove (all virtualbox kext's in my case). As soon as I freed up some slots, all my VM's began working again in VMware.

                 

                Again, this is a little outside my expertise so I'm paraphrasing assistance I got, but essentially they told me there are only a certain number of slots for kext's to be running and VMware needed more slots than what I had available on my machine.

                 

                 

                To check (in a terminal):

                - run 'kextstat | grep vmware'

                - if you only see 2 or less kext's, run 'sudo kextutil /Applications/VMware\ Fusion.app/Contents/Library/kexts/vmmon.kext'

                - if you see something like 'Failed to load /Library/StagedExtensions/Applications/VMware Fusion.app/Contents/Library/kexts/vmmon.kext - (libkern/kext) kext (kmod) start/stop routine failed.', this is probably your fix

                 

                My Steps to fix (again in a terminal):

                - run 'kextstat' to see a list of kext's

                - run 'sudo kextunload -b /whatever/kext/you/can/remove' (i.e. 'sudo kextunload -b org.virtualbox.kext.VBoxDrv')

                - I did that for 4 kext's

                - run vm in VMware again

                - all good

                 

                 

                Hopefully that helps someone.

                • 35. Re: Could not open /dev/vmmon: Broken pipe.
                  CharlieSMF Lurker

                  I am still having a problem running VMware Fusion on Mojave 10.14.6. Is there any fix for this problem?  I could not follow the following as I got a very long list from kextstat

                  Ater 3 hours on this problem I am getting very desperate...

                  ..........

                   

                  I tried all the other responses I saw in here (Allow in Security & Privacy, allow full disk access, try different things in recovery terminal, etc.) but my issue turned out to be maxing out the number of kernel extensions that can be loaded (at least this is my understanding). I ran 'kextstat' and found some to remove (all virtualbox kext's in my case). As soon as I freed up some slots, all my VM's began working again in VMware.

                   

                  Again, this is a little outside my expertise so I'm paraphrasing assistance I got, but essentially they told me there are only a certain number of slots for kext's to be running and VMware needed more slots than what I had available on my machine.

                   

                   

                  To check (in a terminal):

                  - run 'kextstat | grep vmware'

                  - if you only see 2 or less kext's, run 'sudo kextutil /Applications/VMware\ Fusion.app/Contents/Library/kexts/vmmon.kext'

                  - if you see something like 'Failed to load /Library/StagedExtensions/Applications/VMware Fusion.app/Contents/Library/kexts/vmmon.kext - (libkern/kext) kext (kmod) start/stop routine failed.', this is probably your fix

                   

                  My Steps to fix (again in a terminal):

                  - run 'kextstat' to see a list of kext's

                  - run 'sudo kextunload -b /whatever/kext/you/can/remove' (i.e. 'sudo kextunload -b org.virtualbox.kext.VBoxDrv')

                  - I did that for 4 kext's

                  - run vm in VMware again

                  - all good

                  • 36. Re: Could not open /dev/vmmon: Broken pipe.
                    AndrewBurkhart9W Lurker

                    CharlieSMF My best guess would be to try running something like

                     

                    kextstat | grep -v com.apple

                     

                    That way kextstat will just show you things that are third-party (more or less). That might help you find some kexts that you may be able to unload.

                     

                    Hopefully that helps.

                    • 37. Re: Could not open /dev/vmmon: Broken pipe.
                      CharlieSMF Lurker

                      Thanks or the quick response:

                       

                      I ran that in the terminal and did not get anything.

                      grep -v com.apple

                      Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>

                      • 38. Re: Could not open /dev/vmmon: Broken pipe.
                        AndrewBurkhart9W Lurker

                        And if you run "kextstat" by itself, scroll to the bottom, do you see any line items whose name doesn't start with com.apple (i.e. com.vmware, com.sophos, etc.)?

                         

                        If not, you may be dealing with a different issue than I had, unfortunately.

                        • 39. Re: Could not open /dev/vmmon: Broken pipe.
                          CharlieSMF Lurker

                          Problem Solved:

                          From Lurch999 (32)

                          This solution works for cases where the "Allow" button does not appear in Security & Privacy > General:

                           

                          Using Terminal, get the TeamIdentifier value from the VMWare Fusion version you're using (the % is the prompt, so omit that):

                           

                             % codesign -dv --verbose=4 /Applications/VMware\ Fusion.app

                           

                          From the results of that command, find the "TeamIdentifier" value, for example:

                           

                             TeamIdentifier=EG7KH642X6

                           

                          Write that down, and note this is case-sensitive.

                           

                          Reboot your Mac into Recovery Mode (hold down Command + R at boot)

                           

                          In Recovery Mode, open Terminal, then:

                           

                            % /usr/sbin/spctl kext-consent add EG7KH642X6

                           

                          Reboot, and you should be good to go now.

                           

                          Thanks for all the help

                          • 40. Re: Could not open /dev/vmmon: Broken pipe.
                            benau_99 Lurker

                            That did the trick for me. Thanks for taking the time to reply.

                            1 2 3 Previous Next