1 2 3 Previous Next 37 Replies Latest reply on Nov 27, 2016 11:31 AM by sshaw_ Go to original post
      • 15. Re: Fusion 5 - Could not open /dev/vmmon: No such file or directory.
        akarpo Novice

        Good news everyone! Uninstalling SNS Network Solutions iSCSI initiator did the trick! Everything is working normally again. I didn't even have to reinstall Fusion, just a restart after the SNS uninstall was sufficient.

         

        One other thing worth mentioning, since I had SNS installed alongside Fusion for quite some time (and it was working just fine) - I'm starting to think there may have been a third object in play that could have modified my enviroment. I installed the Intel Hardware Accelerator Execution Manager (HAXM) through the Android SDK recently. I know Intel released an update on November 21st for HAXM to resolve some issues experienced by users with Ivy Bridge chips (and I have a 2012 Macbook Air). I'm not sure if the 1.04 update available on Intel's site is also pushed through the Android SDK manager (which updates all the subcomponents). Perhaps that could have messed up the Fusion hypervisor? Hard to tell.

         

        Also, Woody - I've attached the requested output as well, in case you wanted to look at it. Let me know if there's any other diagnostic information you'd like to take a look at.

         

        Thank you everyone!

        • 17. Re: Fusion 5 - Could not open /dev/vmmon: No such file or directory.
          RJIn Novice

          Glad that you took time to explain why the steps helped me won't help in this case. Now, I understand

          • 18. Re: Fusion 5 - Could not open /dev/vmmon: No such file or directory.
            dariusd Virtuoso
            VMware EmployeesUser Moderators

            Cool.  Glad we got things going again!

             

            I still felt there was too much mystery (and too little explanation) in the solution, though, so I dug a little bit deeper, and found something interesting...

             

            On my Mountain Lion host (MacPro5,1, 10.8.2, with no 3rd-party drivers loaded), I have only eight free character device major numbers free immediately after the OS boots.  This is very surprising – it's much lower than I'd expected.  The dump of /dev you kindly provided shows that VirtualBox claims at least two of them (37=vboxdrv, 38=vboxnetctl), Viscosity VPN claims at least another two (39=tap*, 40=tun*), Intel HAXM claims at least one (18=HAX);.  It's entirely possible for drivers to claim those numbers without appearing in the listing of /dev, so there may be others consumed besides the ones we can see.

             

            VMware Fusion wants at least two (one for vmmon – a.k.a. vmx86 – and one for vsock).

             

            So... I think that it may not have been any one single driver that caused the problem...  it was simply that there were too many "character drivers" on your host, and removing one of them freed up enough devices for Fusion to successfully launch.  It would seem that we need to ask Apple to allow more of these character devices to be created...

             

            Thanks for your patience with this issue.  Not only did we successfully solve your immediate problem, but I learned a lot about how our driver integrates into Mac OS, and we've found another possible action we can take to help make Fusion more robust in the future.  Awesome!

             

            Cheers,

            --

            Darius

            • 19. Re: Fusion 5 - Could not open /dev/vmmon: No such file or directory.
              vmwtece Lurker

              I have this exact same issue 'Could not open /dev/vmmon  " etc.

               

              I do not have,  or at least am not aware that I have the SNS Network Solutions iSCSI initiator on my system.  Even if I did I wouldn't know how to uninstall it.

               

              My situation is that I have this OS X 10.8.4 system, onto which I migrated an old 10.7.4 system using Migration Assistant. I didn't power down my Windows 7 VM before doing the migration, should have read the manual I suppose.  Whatever the MA did to my old system it now won't boot.   I just powered it down following the migration not thinking anything of it and now it won't boot.  My guess is that the Apple Migration Assistant did something to prevent the old apps and system from booting.  Googling the problem comes up with nothing.  The long and the short of it is that I can't get back to my old system to shut down the VM.

               

              I followed the advice of uninstalling VM 5.x and reinstalling and repairing permissions, no dice.  I followed the suggestions to fake the VM into a shutdown state, no dice.

               

              I have attached my 'ls -l /dev' in the file called devlist.txt.  I have attached my Support Information from VM Fusion.

               

              Help please is all I can ask.

              • 20. Re: Fusion 5 - Could not open /dev/vmmon: No such file or directory.
                dariusd Virtuoso
                User ModeratorsVMware Employees

                Hi vmwtece!

                 

                The cause of your problem is quite different: Your hardware does not meet Fusion's System Requirements.  You'll need to move Fusion to supported host hardware before we can help.

                 

                Cheers,

                --

                Darius

                • 21. Re: Fusion 5 - Could not open /dev/vmmon: No such file or directory.
                  vmwtece Lurker

                  Darius,

                   

                  Thanks for taking a look. 

                   

                  Here's how I 'fixed' the issue.  

                   

                  I edited the Library configuration of the image (option-click) and changed the state of the VM to powered down.

                   

                  I moved the VM out of the library location and rebooted my Mac.  On return I re-started Fusion without a VM present.  I quit Fusion.  I moved the VM image back to the library and re-launched the VM.   There was no message about /dev/vmmon!  The VM came back to my Windows login screen much to my joy and I logged into the Admin account.  The VM crashed and offered to save a debug image for support.  I thought I had lost the VM.   Naturally I have not attached that crash resport as you won't examine it.

                   

                  Following the crash with nothing to lose  I attempted to boot the VM into Safe Mode of WIndows.  It came up in safe mode.  I rebooted to normal mode. The admin login crashed again the same way.  I rebooted to Safe Mode once again.  I changed nothing as nothing appeared to be wrong.  On my third re-cycle to normal mode the Admin account allowed a login without crashing!   The VM is now back up and running.  It looks normal.

                   

                  Perseverance pays off I suppose.

                  • 22. Re: Fusion 5 - Could not open /dev/vmmon: No such file or directory.
                    WoodyZ Guru

                    vmwtece wrote: I moved the VM out of the library location and rebooted my Mac.

                     

                    Well according to the information in the support bundle, you do not have a Mac and are not in compliance with Apple's SLA for OS X by running it on non-Apple-branded hardware!  Illegally running OS X on a PC doesn't make it a Mac!

                    • 23. Re: Fusion 5 - Could not open /dev/vmmon: No such file or directory.
                      gschiltz Lurker

                      Darius, I appreciate your response since I'm pretty sure I have the same problem. Would you please elaborate on your answer (number 18 of this thread)? Specifically, how could you tell from the directory listing of /dev how many "character drivers" are in use and how many are available? I have attached a file with the results of an 'ls -l /dev' command. I have the HAX driver for doing Android development installed (which I saw mentioned elsewhere in this thread) as well as openvpn. All is well until I install VirtualBox, which I suspect steals some of the necessary devices from Fusion, after which VirtualBox works but Fusion gives the message about /dev/vmmon not existing. If I uninstall VirtualBox, all is well, but at times I'd like to have both installed at the same time. Many thanks in advance.

                      • 24. Re: Fusion 5 - Could not open /dev/vmmon: No such file or directory.
                        geeklizzard Lurker

                        I'm having a similar issue, and I need to keep VirtualBox and Viscosity both installed. Do you have any advice that might help me be able to use Fusion as well? Would upgrading to the latest version help? Thanks!

                        • 25. Re: Fusion 5 - Could not open /dev/vmmon: No such file or directory.
                          dariusd Virtuoso
                          User ModeratorsVMware Employees

                          I don't think there will be any difference between Fusion 5 and Fusion 6 regarding this issue.  I have not yet investigated whether OS X 10.9 makes this situation better, makes it worse, or is unchanged...

                           

                          Unfortunately this is a limitation within OS X that we're running into, and I don't know of any way to work around it short of building your own Darwin kernel that allows more character devices...

                          --

                          Darius

                          • 26. Re: Fusion 5 - Could not open /dev/vmmon: No such file or directory.
                            dariusd Virtuoso
                            User ModeratorsVMware Employees

                            Hi gschiltz,

                             

                            There is no easy way to determine the number of available character device nodes from the listing of /dev.  It can provide clues, but the interpretation of those clues would be challenging to explain – it involves matching up the list of loaded drivers with the names of registered nodes in /dev, and matching all of that up against the source code for the "xnu" kernel of Mac OS.  I lack the time to write up a full explanation... sorry.

                             

                            If you are encountering the issue described in this thread, and you can resolve it by removing one or more of the software packages you mentioned, then you probably have no workaround other than to remove one of those software packages, I'm afraid.

                            --

                            Darius

                            • 27. Re: Fusion 5 - Could not open /dev/vmmon: No such file or directory.
                              Masa201110141 Lurker

                              I had the same issue of vmmon not found after installing Intel HAXM. Just uninstalled it, and restarted VMware Fusion. All is well now. Thank you for your post!

                              • 28. Re: Fusion 5 - Could not open /dev/vmmon: No such file or directory.
                                ironrob Lurker

                                Darius,

                                 

                                Here is my support info file. I'm getting the same error. I believe it has something to do with having an expired trial version of Fusion7. Post trial, I'm interested in going back to my licensed Fusion5 and am unable to shutdown the VM last used with Fusion7 in order to edit compatibility settings, etc. It appears the only way to shutdown a session is to open it, which requires an upgrade post trial. I've tried uninstalling Fusion7, reinstalling Fusion5, and adding another VM. Note: I'd prefer to use the existing VM if possible. However, I get this "error message" when starting the new VM and the "upgrade requirement" when I try to open the VM used with Fusion7. How do I get out of this error or upgrade loop?

                                Thanks

                                • 29. Re: Fusion 5 - Could not open /dev/vmmon: No such file or directory.
                                  dariusd Virtuoso
                                  User ModeratorsVMware Employees

                                  Hi ironrob, and welcome to the VMware Communities!

                                   

                                  The cause of the problem you're facing is simply that VMware Fusion 5 is not compatible with OS X 10.10 (Yosemite).  You'll need at least Fusion 6.0.5 simply to be compatible with your newer version of OS X.

                                  --

                                  Darius