MacOS Sonoma ready?

[gb667]

Agreed - this is a very useful thread. Thank you to all who've contributed.

I just updated to Sonoma (14.3.1) from Ventura (13.6). I have a very large Ubuntu VM and I held off updating to Sonoma expressly because VirtualBox did not appear to work. I am happy to report that after some effort, I now have my Ubuntu VM running on VB on Sonoma 14.3.1. It took some doing, and much of the above wisdom was useful. Here is in general what I had to do to get over the

Code: Select all

NSFAILURE (0X80004005)

that occurred on initial start.

In addition having to allow the security preferences in System Settings and rebooting, I still had issues. What I ended up doing was re-downloading Virtual Box (7.0.14 r161095) and then reinstalling VB directly. Note that I did not uninstall first. I simply had to install, reboot, then my old VB VM worked just fine. (At least so far).

Part of why I updated to Sonoma is because my Mac seems to be getting slower and more fragile WRT how the mouse pointer actually works and it was nearly impossible to use machine at some point. (Could well be one of the other apps I've updated recently which 'broke' MacOS, and one of the ways it shows happens to be in VB). In the end, things seem more stable now and faster. Having said that, I'm not yet strongly using the VM. That will be shortly (Running EDA engineering tools which beat the crap out of the VM).

My computer:
2019 MacBook Pro 16 inch
8 core 2.4Ghz i9
64GB RAM (48GB applied to VM)
Sonoma 14.3.1

[granada29]

Now the VM will freeze after a few minutes of using Excel (especially when running macors). Note: using the same Excel macro file now that I used before when this worked.

Testing and actions:

• Checked VM settings to used Hyper-V and disable 3D acceleration. Increased processors from 2 to 3 (of 8 total). Set memory from 4GB to 8GB (of 16GB total on host).

Sorry for the late response. You have oversubscribed the memory in your VM.

Code: Select all

00:00:01.926625 Host RAM: 16384MB (16.0GB) total, 4826MB (4.7GB) available
00:00:02.121957   RamSize           <integer> = 0x0000000200000000 (8 589 934 592, 8.0 GiB)

You only have 4.7GB available. You should reduce the VM allocation back to 4GB.

If your VM really needs more than this then use Activity Monitor to find what other process are consuming RAM on your machine. Alternatively - add more RAM to the host.

[toddmh70]

Thank you Granada. Much appreciated. I'll have a look. I may now have an excuse to get a new beefier mackbook

KR

Todd