Thanks for the response. Your message serves as a much more instructive error message...perhaps that can be coded into the software reducing frustration and streamlining the upgrade process. FYI, I initially initiated the trial required to test a SAS product, however I discovered a workaround. My Yosemite auto upgrade took place within the past couple days during this issue, so I wasn't suspecting it as the cause for error as I was not shopping a Fusion upgrade. Other than typical functionality I really didn't notice gains from the upgrade. Unless there are new Yosemite dependent features, which I was unable to experience; perhaps such upgrades can be done with a patch? This whole experience has brought your competition into my consciousness.
That said, from reading through many of your posts I find your personal service to be top notch.
Thank you for your service
This helped me solve my problem. I realized that I had installed an Android SDK since my Fusion quit working. I did a search for uninstalling HAXM and found these instructions -
/System/Library/Extensions/intelhaxm.kext/Contents/Resources/uninstall.sh. They are from this page - https://software.intel.com/en-us/forums/topic/477793.
I didn't have to reboot. Just shut down Fusion and restarted it. Now my Windows VM comes up without the "Could not open /dev/vmmon: No such file or directory" message.
What a crock. VMWare holding us to ransom. Surely they can make it compatible with Yosemite, they just want to extract more $$ from their customers. I'll be looking at Virtual Box for sure.
I don't use VMWare much, so it was a "want" not a "need" purchase. Very disappointed that an operating system upgrade disabled Fusion. That sucks bigtime.
Hey there, I am having the same problem described here, can you take a look at my support information and see if there's a solution possible? I'll attach the support info and paste the results of the "ls -ld /dev /dev/vmmon" command.
Logans-MacBook-Pro:~ loganinwonder$ ls -ld /dev /dev/vmmon
ls: /dev/vmmon: No such file or directory
dr-xr-xr-x 3 root wheel 4287 Sep 3 10:06 /dev
vm-09-03-15.939.tgz 1.4 MB
Hi Logan, and welcome to the VMware Communities!
Fusion 5.0.5 is too old to work with OS X 10.10. Apple have been steadily improving the security around the use of kernel extensions, and those included with Fusion 5.0.x (which was designed to work with OS X 10.8) do not meet the requirements of OS X 10.10. There are probably many other compatibility issues beyond that one, but that is specifically what's causing the failure you are seeing.
To resolve the problem, you'll need to upgrade your copy of Fusion.
Balls... do you have a coupon or $50 i can borrow ??
Thanks for the quick response!
I have not yet investigated whether OS X 10.9 makes this situation better, makes it worse, or is unchanged...
I encountered this on 10.9.
My box has a ton of VirtualBox, OpenVPN, Cisco VPN, Docker, etc... stuff. To free up a slot I uninstalled OpenVPN. Fusion is now working, only needed to restart it.