1 2 3 Previous Next 37 Replies Latest reply on Nov 27, 2016 11:31 AM by sshaw_

    Fusion 5 - Could not open /dev/vmmon: No such file or directory.

    akarpo Novice

      Receiving the following errors when I try to start up my virtual machine(s) in Vmware Fusion 5 -

       

      • Could not open /dev/vmmon: No such file or directory.
      • Failed to initialize monitor device
      • Cannot find a valid peer process to connect to.

       

      Reinstalled Vmware Fusion 5 using these instructions - http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1017838

       

      Uninstalled. Restarted. Reinstalled. Restarted. Started virtual machine, same errors.

       

      Thinking it might be a problem with the virtual machine, I copy over another virtual machine that's running just fine on another Mac downstairs. Same errors. I'm running 10.8.2 on a 2012 Macbook Air.

       

      Starting to think this is an enviroment problem, but I'm not sure where to start looking beyond the manual uninstall instructions. Any assitance would be greatly appreciated.

       

      One strange thing I noticed - even after a manual uninstall and subsequent reinstall, it still lists the old virtual machine name in the Virtual Machine library list. Also, /dev/vmmon is still missing after a reinstall.

        • 1. Re: Fusion 5 - Could not open /dev/vmmon: No such file or directory.
          avanish321 Expert

          Repair hard disc permissions on mac hard disc using disc utility app and then try to install fusion.

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

            Thanks for the reply avanish. I tried that, disk utility isn't reporting anything abnormal - http://cl.ly/image/3U1W3Y1S2w2j

             

            Attempting to start the virtual machine after the repair yields the same errors.

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

              Thank you for the reply, WoodyZ. Unfortunately, the items listed in the KB do not resolve my issue (manually reinstalling & removing library files + repairing disk persmissions). Trying to create a brand new VM yields the same errors on first startup. Again, I think it's an enviroment issue.

               

              Somewhere in my enviroment, there exists VMware data/settings that persist after a manual uninstall. This data goes beyond what's listed here  http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1017838

               

              I've manually deleted all these files, restarted and upon a reinstall (and an additional restart), Fusion still somehow remembers the name of the last virtual machine I had in my virtual machine library. How is this possible? Again, there is data/service that is in corrupted/malformed which is not corrected during the reinstall process.

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

                Please do not follow those instructions. (NOTE: the parent post containing the instructions, including steps purporting to create a directory at /dev/vmmon, has now been deleted.)  /dev/vmmon is not supposed to be a directory... it is a device node.  It should never be created manually.  Creating a directory at that location is quite likely to make VMware Fusion fail.  (FWIW, Mac OS won't even allow me to make a directory under /dev, even as root/sudo...)
                --

                Darius

                 

                Message was edited by: dariusd to mention the deletion of the parent post to which I referred.

                1 person found this helpful
                • 6. Re: Fusion 5 - Could not open /dev/vmmon: No such file or directory.
                  akarpo Novice

                  Thanks, dariusd. Any advice on how we might go about replacing the missing /dev/vmmon/ ?

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

                    Hi akarpo,

                     

                    The device node /dev/vmmon should be created automatically when our vmmon kernel extension (com.vmware.kext.vmx86) loads.  That kernel extension should automatically be loaded when you start VMware Fusion, and should automatically be unloaded when you quit VMware Fusion.

                     

                    There are all sorts of places where environmental problems could cause the above procedure to fail.  The best way for us to figure out what's happening is through a support information bundle: Launch VMware Fusion, go to the Help menu and choose Collect Support Information.  That will create a file on your Desktop.  Attach that file to a reply in this thread, and I'll take a look.  There will probably be sufficient information in that file for me to figure out what's going wrong.

                     

                    Cheers,

                    --

                    Darius

                    1 person found this helpful
                    • 8. Re: Fusion 5 - Could not open /dev/vmmon: No such file or directory.
                      akarpo Novice

                      Diagnostic information generated by Fusion, attached below.

                       

                      Merry Christmas to all!

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

                        Hi again akarpo, and a Merry Christmas to you too!  If only I had a nice solution to your problem that I could gift-wrap up and give you, but not yet...

                         

                        Thanks for the support information bundle.  It's told me a little bit about what's going on, but there are still more questions than answers.  I'd appreciate if you could do the following steps in order:

                         

                        1. Launch VMware Fusion.  Don't attempt to power on any VMs... just leave it running.

                        2. On your host, also launch Applications > Utilities > Terminal.

                        3. At the prompt in the Terminal window, run the following exact command:

                         

                           ls -ld /dev /dev/vmmon

                         

                        The output should look something like this (but it might also contain error messages in your case)...

                         

                        host:~ username$ ls -ld /dev /dev/vmmon

                        dr-xr-xr-x  3 root  wheel      4259 Dec 24 18:48 /dev

                        crw-------  1 root  wheel   36,   0 Dec 26 01:12 /dev/vmmon

                        host:~ username$

                         

                        4. Copy the resulting output from your Terminal window and paste it into a reply in this thread.

                        5. Quit Terminal and quit VMware Fusion.

                         

                        Let me know if you have any questions, particularly if you don't already happen to be familiar with Terminal and aren't comfortable with it!

                         

                        Thanks!

                        --

                        Darius

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

                          Thanks for looking into this, Darius. Hope you had an enjoyable Christmas

                           

                          Output below.

                           

                          Last login: Wed Dec 26 04:36:31 from localhost
                          Alexs-MacBook-Air:~ Alex$ ls -ld /dev /dev/vmmon
                          ls: /dev/vmmon: No such file or directory
                          dr-xr-xr-x  3 root  wheel  4639 Dec 25 18:46 /dev
                          Alexs-MacBook-Air:~ Alexmce_markernbsp;

                           

                           

                          Which confirms that /vmmon is missing. What might the next step be?

                           

                          -alex

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

                            Thanks, Alex.

                             

                            Looking further back in the support information bundle's history gave me a big clue.  It seems that some driver on your system is triggering the problem by consuming all of the available "character device major numbers" (a small number used to identify a driver/device).  I can't immediately identify the culprit driver, but the possibilities include:

                             

                            • Studio Network Solutions iSCSI initiator
                            • Viscosity VPN
                            • VirtualBox

                             

                            We have quite a few users with VirtualBox alongside Fusion, so I doubt that VirtualBox is the cause, or I'd expect to have seen more widespread reports of this problem, unless it's being exacerbated by some other environmental factor.

                             

                            It's also possible (although less likely) that it is a problem with one of the drivers built in to Mac OS, or it might even be one of the other drivers in VMware Fusion, but – again – in either of those cases I'd expect to have encountered more reports of the problem unless it's triggered by some other factor on your system.

                             

                            Could you try temporarily uninstalling either the SNS iSCSI initiator or Viscosity VPN and see if that helps?

                             

                            Cheers,

                            --

                            Darius

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

                              Hello,

                               

                              Thanks for the response Darius.

                               

                              Recently we had a smilar issue and when we went to ~/library/logs folder, VMware folder was missing.

                              So, we created folder named "VMware" inside ~/library/logs folder with the correct permissions and retsarted the and that fixed the issue for me. So, if you would like try the steps and see.

                              Also if the folder exists delete the folder and re-create it and do restart  the Mac.

                               

                              Thanks

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

                                RJIn wrote: Recently we had a smilar issue and when we went to ~/library/logs folder, VMware folder was missing.

                                So, we created folder named "VMware" inside ~/library/logs folder with the correct permissions and retsarted the and that fixed the issue for me. So, if you would like try the steps and see.

                                Also if the folder exists delete the folder and re-create it and do restart  the Mac.

                                 

                                First of all "similar" and "same", especially in cases like this, are two distinctly different issues and secondly (as shown by the contents of the support bundle) the appropriate log folders exist on akarpo's system with the appropriate logs in them, therefore deleting and recreating them will really do nothing more then the state they're already exist in.

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

                                  Alex, In a Terminal could you copy and paste the following command and then press Enter.  Then attach the devlist.txt file it created on the Desktop to a reply.

                                   

                                  ls -l /dev > ~/Desktop/devlist.txt
                                  1 2 3 Previous Next