Fusion Causing Ventura Host (Intel) to Reboot

[Craie]

While still on Big Sur, I upgraded to Fusion 13.5 and all was fine.  Just a stray message about a missing serial device I wasn't using anyway.

Fast-forward to winter break and I upgraded to Ventura (13.6.3).  Now the host machine is rebooting whenever VMWare is running for a while -- even without a guest in play!

I've been removing apps one at a time and the only one that stopped this crashing situation is Fusion.  Is anyone else having such an issue?

I really need my VMs for work and it starts up later this week!

Thanks for any help,                                  Jason

[Technogeezer · Accepted solution]

That's very unusual. Are there any indications in the Mac's unified logging (use the Console utility) as to what's going on?

Fusion 13.5 is not supported on Big Sur (see https://kb.vmware.com/s/article/2088571 ) so I wonder if something with that installation is causing problems because of the subsequent upgrade to Ventura.  Have you tried a full uninstall of Fusion per KB article https://kb.vmware.com/s/article/1017838, reboot your Mac, then re-install Fusion?

[Technogeezer]

By “import”, what do you mean? You should simply be able to open them from the Fusion UI by locating them in the dialog that is presented when using File > Open…

Where are the VMs that you have been using? Internal disk or external? If external, what is the drive formatted as?

[Craie]

Technogeezer,

Sorry.  I realized after posting that the initial import dialog Fusion gives wasn't what I needed for VMWare created machines.  So I found the scan feature and got them loaded that way.  It offered there the old placement of '~/Documents/Virtual Machines' instead of just '~/Virtual Machines' as well.

I'm testing it now.  But it could take several hours before it crashes if history is accurate.  *fingers crossed*

Thanks for the help so far!                                  Jason

[Craie]

Technogeezer,

As my system has been stable for over 2 days now, I'm accepting this as the correct solution.  Thank you for all your help!

Later,                                                   Jason