Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
VMware Engineer Confirms macOS Catalina 10.15.6 Bug Causes Crashes with Virtualization
- Thread starter MacRumors
- Start date
- Sort by reaction score
I have zero issues with Mojave, from which I never upgraded predominantly because I’ve been too lazy to sort through my Apple for 64-bit compatibility (and, in retrospect, I’m glad I didn’t).
Big Sur beta 3 has broken all virtualization software
My 2019 mbp 15" crashed and rebooted by itself on wake from sleep 2 days ago running 10.15.6. I really dislike using catalina. Crappiest macos in years. Fixes one bug and breaks 2 more other things. Not sure if it is related to this issue or not, but a fix should be on the way.
Just getting you ready for the barren wasteland of virtualization that will be apple silicone.
9.2.2 was pretty stable.
All kidding said, I found the last 10.14 to be pretty good here.
You will be able to run Windows ARM natively and I am sure that it's going to get a lot of attention now that Apple is switching. The same will apply to all the Linux community, arm will get more emphasis. So, the future looks strong with a real competition to the stagnant x86
Having this issue since 10.15.6. Contacted apple about it, and again today. I have a calls setup with them at 1pm EST to review. Now, I'll bring this up as well. Since this is exactly what's happening to me as well. Each day using my VM's, everything is fine. Go home, come back to work. Crashed overnight. Same Kernel memory issue. I thought I was going to have to reinstall everything!! Thanks to VMware for confirming this and letting Apple know. Saved me a rebuild!
Thanks to VMware for confirming this and letting Apple know. Saved me a rebuild!
No you won't.
Windows on ARM (WoA) is an exclusive build for Snapdragon SOCs only. Microsoft does not sell a public license for WoA and, even if they did, there is no version for Apple Silicon.
Yup, and you know what else runs great?... a Catalina 10.15.6 guest running on a Mojave host with VMware Fusion. Rock solid host and guest[*] and very decent performance within the Catalina VM. My host machine is a 2016 MBP 15" with only 16GB RAM, so while I gave the VM 4 cores, I only gave it 4GB of memory. As long as I don't run too many apps within the VM, everything is all good.
Perhaps the only safe and sane Catalina is one that's caged up within a VM.
[*] Well, ok, to be clear the Catalina guest has been totally stable. That doesn't mean it's doing everything well; virtualized or not, it is still Catalina.
Last edited:
Windows 10 also runs great...Getting used to it now for when my current MBP bites the dust.
Mojave was stable from the very first beta, it is better than Snow Leopard, SL had big issues in the beginning, Mojave also has a lot more features.
My Mac crashed overnight running Parallels on Big Sur b2.
Most probably Mojave. You don't want to be going too far back, as you need the latest security features. As other people have said, Mojave has everything you need from a modern OS.
That said, millions of people have been using Catalina with no problems. Running VMs is quite a power-user thing to do so if you only use your mac for basic everyday things - office apps, browsers etc, then you are likely fine with Catalina.
I stayed on Mojave myself firstly because my MS Office was still 32-bit, and secondly because of my Steam games catalogue. Now I'm on O365, and I haven't touched my 32-bit Steam games in over a year, I could probably go to Catalina right now and be fine. I probably won't though, I'm happy on Mojave for now and there's nothing I want in Catalina.
(I will probably upgrade my kids macs to Catalina for the improved Screen Time parental control functionality.)
Not a VM user, but encountered 10.15.6 crashes repeatedly with last 2 public betas before it went to GM. What I noticed was my Apple Magic Bluetooth keyboard became unresponsive after kernel crash restart. I isolated this disabling Bluetooth in the system preferences, and not restarting, but power off, and then on. After that the 10.15.6 was stable using a USB keyboard instead. I reported this to Apple, and this news sounds very similar.
Note never encountered anything as bad as this issue in all the time I been testing public betas since the program has been going. Surprised it was released leaking kernel memory. Note using a late 2015 27” iMac, 4 ghz i7. Using a 2GB Fusion drive. Diagnostics showed no issues.
Last edited: