It's something we're investigating.
A reboot sorts it, and in some cases quitting fusion and relaunching it does.
In the case of Docker, you have to quit Docker, then quit and reload Fusion.
Wil| Author of Vimalin. The virtual machine Backup app for VMware Desktop Products1 person found this helpful
| Vimalin : Automated backups for VMware Fusion and VMware Workstation Professional
| More info at https://www.vimalin.com
| Twitter @wilva
| VMware Wiki at http://www.vi-toolkit.com
FWIW, I had this happen during the beta (on High Sierra) when I tried to launch 3 VM's all at once. Just a data point.
I noticed that some mix of rebooting, restarting Fusion, and restarting Docker seemed to help. The last time I had the issue, I stopped Docker and restarted Fusion and continued to see the issue. I restarted Fusion a couple more times and continued to see the issue. However, when I tried starting a VM again after a few minutes (not having made any other system changes), it worked.
Thanks. I looked for similar issues, but somehow missed that one.
Same issue. As the original poster noted, this happens when no machines are currently running. This needs a fix asap and is not trivial. This has left me in a bad spot several times.
I have the same problem. And none of the steps you are suggesting do anything! I need this working! Please advise.
The advice (quit docker and then re-run VMware) was good and worked but doesn't leave me with great confidence in the testing of VMware.
2 people found this helpful
This is the solution I was given that worked for me:
- - Quit VMware Fusion
- - Open Finder
- - Select the option 'Go' on the top Mac menu bar > Select 'Go to folder' > Type '~/Library/Application Support' and press the Return key
- - Remove the folders 'VMware Fusion' and 'VMware Fusion Applications Menu'
- - Empty trash
- - Start VMware Fusion
- - Add the Virtual Machine in the Virtual Machine. You may also scan for the Virtual Machines.
- - Start the Virtual Machine
I have this same issue in terms of too many virtual machines. I do not have or use docker; however, I do have Android Studio installed which uses qemu. A reboot does sort the issue temporarily, but after using Android Studio/qemu, it goes back to the error again. This is very frustrating, please fix this!
Upgraded from Fusion v10 standard to Pro as part of the upgrade. I am running on a Mac Pro with Mojave with 64Gb Memory and 12 cores. v10 worked fine. I have tried reinstalling, I have tried with Docker stopped but have failed to get anything to work.
Currently, I have a VMware platform that has stopped me dead in my tracks !!
I can confirm that the solution given on the suggested thread fixed the issue for me.
- MacOS High Sierra (10.13.6)
- Running the latest version of Docker CE
- Running VMware Fusion 11
I have the same problem after upgrading to Fusion 11 Pro. Version 10 did not have this issue but I decided to upgrade to 11 in order to ensure best compatibility with Mojave. The end result is that I can no longer run my VMs at all unless I jump through very specific hoops every time. It's ridiculous that the net result of spending $119 to upgrade from 10 Pro to 11 Pro for better compatibility with Mojave and Windows 10 is a product that does not work most of the time. Time to see about getting a refund I guess.
For anyone else having the same issue, if you quit Docker while Fusion is running and then restart Fusion it will not work. You need to first quit Fusion, then quit Docker, then re-open Fusion and then it should work.
I had the same problems with Docker installed. Restarting the OS can solve the issue but that just temporarily. Restarting Docker does not solve the issue immediately, at least for me.
HOWEVER, when I click on the VMWare Helper on the toolbar, I saw that it showed all my virtual machines are running, even though they were appeared to be off. I then clicked stop button on one of the virtual machines in the helper and clicked start. I was being to start the virtual machine immediately. Mikero