Agreed that it is a very, very bad idea to have VM stored on locations that are being sync'ed to any cloud storage provider (such as Dropbox, iCloud Drive, Google Drive, or Microsoft OneDrive). The time needed to recall a VM's virtual disks that have been uploaded is just one of the reasons why. Fusion isn't aware of anything being done to the files by the macOS cloud storage mechanisms that pretty much all of these cloud providers use.
To be fair, as I say if I recall correctly Fusion creates its folder of VMs in your Mac's Documents folder by default, and iCloud backs up the Documents folder also by default!
You are correct that older versions of Fusion created the default Virtual Machines in your Documents folder, Newer versions do not - they create the Virtual Machines.localized (default location) folder immediately under a user's home folder -- at the same level in the hierarchy as the Documents, Music, Photos, etc folders. (I don't remember exactly when the behavior changed). But the old default location in the Documents folder will be recognized and won't be touched if it exists when upgrading.
Having iCloud Drive enabled does not automatically mean that the Documents and Desktop folders are synchronized to iCloud. There's a separate setting in your System Preferences/Settings to enable that sync of Documents and Desktop folders. I've seen this setting turned on by default in some circumstances, or can be turned on by answering the questions on managing macOS disk storage.
My recommendation is if you have any cloud sync turned on for your Documents folder or Desktop folder, move any virtual machines you've stored there into another folder outside those locations. An external USB3/4 SSD is best (this easily lets you disable TIme Machine having anything to do with your VMs -- that too is another discussion). Going forward, make sure you don't store new VMs anywhere in the Documents folder hierarchy or the Desktop
Unfortunately as you found out, moving an offloaded VM first recalls it to the user's home folder first, then moves/copies it. That means you have to have the disk space available to hold it.
Yes, indeed backup of VMs is another topic entirely. Cloud sync,
------------------------------
- Paul (technogeezer)
vExpert 2025
------------------------------
Original Message:
Sent: May 24, 2025 02:35 PM
From: Oliver de Peyer
Subject: Fusion 12 Hanging on startup
Dear all,
I'm pretty sure these phenomena are due to your VMs getting transferred into the cloud by iCloud.
Most of us will have iCloud active, and by default, iCloud backs up your Mac's Documents and Desktop folders to iCloud. Cruclally, it will transfer files entirely to the cloud, with no local copy on your Mac, if disk space gets low on your Mac.
If I recall, by default Fusion will create your VMs in a folder in Documents. VMs are often very large - easily 10s of Gb - so iCloud will often quietly transfer then entirely to the cloud to regain local disk space. This has been my experience anyway.
Go and have a look for yourself - find a VM you would like to open in your Mac's Finder and see if it has the cloud symbol next to it...
When you click on a file like this, iCloud then transfers the file back for local access on your Mac's disk.
However, A: This can take an appreciable amount of time, and B: you might not have enough space locally on your disk anyway...
For instance, Fusion on my Mac (I'm running Fusion 13 on MacOS 12.7) seemed to hang for a long time - like others have observed, for many hours - and when I noticed the VM I was trying to open had the cloud symbol by it in Finder, I did a rough calculation of how long the file would take to be copied back to my local disk, based on its size and my local network speed - for instance, a 100Gb VM transferring at 0.1Gbps.... will take 8000s to open! That's over 2 hours. And indeed that was indeed how long Fusion took to open roughly for the file in question.
Ok, but then why does Fusion hang when you are starting it up even when you are not trying to open a particular VM?:
I think this is the same phenomenon. Fusion usually start up and displays the list of recent VMs you have used. It's basically hanging before even this list appears, at least that's what happened to me.
I went back and looked at the VMs I had on Finder - several of these had the cloud symbol, showing that they had got transferred by iCloud fully into the cloud. Despite my efforts to get these transferred to my Mac's local disk (e.g right click on the VM in Finder and select "Download Now") some of the VMs never transferred, quite possibly because there just wasn't enough space on my Mac's disk locally (e.g a 100Gb VM with less than 100Gb free space on my Mac's disk)
I postulate that Fusion is checking ALL the VMs on the list in some way, and hangs until they are all present locally.
I assume that Fusion is asking MacOS to look at the VM files, and MacOS is asking iCloud to transfer the files back to Mac's local disk, and iCloud never completes this... because the network connection is slow, or there is not enough space on the local disk, etc. So VM just hangs - for hours (until iCloud transfers ALL the VMs back to the local disk) or forever (if there just isn't enough disk space)
There is an obvious test for this which is to totally disconnect your Mac from the network - no wifi, no ethernet etc.
I tried this - Fusion started working again instantly.
I then edited the list of VMs in Fusion - I deleted absolutely any VM from the list that I didn't need. NOTE, Fusion will ask if you want to delete the actual VM and its files, or just it's presence in the list. Obviously, if you still need the VM, don't delete the files by accident!
Once you have your pruned list - and you have made sure that the VMs you need are indeed actually present locally on your Mac's disk and are not in the cloud - you will find that Fusion works perfectly again. At least, that's what happened to me.
You can always add a VM back onto the list later by opening that VM from Fusion's file menu. There's no real need to have all your VMs in the on screen list in Fusion all the time, since it obviously adds the possible hazard than any one of them might hang Fusion as above.
Many of you might scold me for allowing iCloud to get its hands on my VMs in the first place. To be fair, as I say if I recall correctly Fusion creates its folder of VMs in your Mac's Documents folder by default, and iCloud backs up the Documents folder also by default!
If you put your VMs your desktop instead.... iCloud backs up your Mac's desktop by default as well!
So, you would need to find some other place to put it. And from another angle, if your VMs are important to you then you probably DO want to have them backed up - somehow. Perhaps that could be a topic for another thread!
Ironically, I got myself in trouble with Fusion hanging again by trying to get iCloud to download my VMs back to the local disk, and then transferring them all to a RAID1 mirrored external drive I happen to have. Not all the VMs would complete the download - not enough disk space on my Mac.... - which I think "broke" Fusion's list of VMs again.
I will gingerly try opening the VMs from my external disk.... again that's maybe a topic for another thread.
Hope this is helpful to people!!
Original Message:
Sent: Oct 28, 2024 06:59 PM
From: M1-MaxUser
Subject: Fusion 12 Hanging on startup
SOLUTION
Top Menu -> Virtual Machine -> Send Key --> HOME
- Send a key to the virtual machine to possibly break its current start or start a new state.
.
.
I had the same problem.
- Sometimes (rarely) would be blank and not boot the Virtual machine
- rebooting my mac completely would not solve it
- turning off all apps, closing everything not needed.. nothing helped.
- If I open it in the evening, when I try to use it in the morning it magically has loaded and worked
.
System Info
- MacBook M1 Max
- VMware Fusion 13.6.1
- MacOS Sequoia
- VM: Windows 11 64bit
Original Message:
Sent: Dec 27, 2020 05:02 AM
From: PrinceAlbert
Subject: Fusion 12 Hanging on startup
Today for no apparent reason, when I started VM Fusion 12, it just hangs.
What should I do first to resolve this problem.
I've been running Big Sur since it's release.
I have removed it and re-installed, same thing happens