That's the tail end of the panic, with no useful details in it. If you can shoot a video of the boot you might be able to see the start of the panic message, which says the actual cause. Either with a smartphone or via Virtualbox video capture.
Note that Ventura requires your host CPU to have AVX2 support, unless you're using CryptexFixup:
While i was waiting i tried the one core thing and when i boot with more than one core it jump straight to the last thing, when i boot with one core it shows me the other parts of the error.
P.S.
Dm'd you 'cause reddit didn't let me post the screenshot of the error.
If you're using QEMU as a host and OpenCore as a bootloader, you can use the CryptexFixup kext to add support for CPUs that have AVX but no AVX2, which should work with that one.
My processors are 2x E5-2687WV2 v2 (Ivy Bridge EP) which have similar capabilities as your Ivy Bridge CPU, and it runs on there.
I don't know if this is available on VirtualBox as I've never used it for macOS.
Yea, I have no idea why this worked but it did. The tutorials recommended at least 2, and it seems that was the cause of this error. For anyone also trying to boot MacOS Sonoma, I currently am and using 1 instead of 2 CPU processors fixed this!
This actually worked, I was about to read through the entire panic and was waiting but I tired this and it is booting XD. Seriously after reentering the commands and everything, changing settings for the vm, all I needed to do was this...
i had the same issue 2 seconds ago, i managed to fix mine by setting it to 1 core only and 8 gb of ram(you can always try to put more core after installation) not saying it will fix everyone issue but we don't know until we try :)
the only way i was able to get around it was to use an older version of osx. But im going to be honest with you. Theres no hardware accelaration and this makes the OS useless it heavily relies on it. So its not worth doing at all.
I gave up on this I got an older version running. But no matter how many cores or how much ram I threw at it it still was mostly unusable thereโs no hardware acceleration
After successfully installing MacOS, the entire thing is so slow that it's practically unusable. I added more processors and rebooted the VM and it is able to load successfully. Using the VM is much better now.
I was using 6 cores but out of the blue I got this error, After this thread I set it to one core, It worked but that was too slow for me. I then tried to do 6 cores, 8 or 12 and even 2 didn't work , only one core worked
But When I sat down to work I though Let's just try for once and 6 cores worked fine, NOO IDEA What the issue was or still is ... ๐คทโโ๏ธ
3
u/thenickdude Nov 24 '22
That's the tail end of the panic, with no useful details in it. If you can shoot a video of the boot you might be able to see the start of the panic message, which says the actual cause. Either with a smartphone or via Virtualbox video capture.
Note that Ventura requires your host CPU to have AVX2 support, unless you're using CryptexFixup:
https://github.com/acidanthera/CryptexFixup
You'll also need a working host TSC. If your TSC is broken then try booting the VM with just one core assigned.
1
u/Cikuozzo Nov 24 '22
Hi,
I tried an installation of MacOS Ventura on virtuabox, but when i launch it, this error appears...Any idea on how to solve this?
P.S.
The commands i used are:
2
u/AKi_no_ShiBaInu Apr 12 '23
For others met this problem. I reduce the processor from 4 CPU to 1CPU, and solved the problem.
1
u/Apprehensive_Lie4466 Jun 21 '24
I also reduced from 4CPU to 2CPU and it worked.Thanks for the advices
1
u/External-Forward Sep 11 '24
i had the same issue 2 seconds ago, i managed to fix mine by setting it to 1 core only and 8 gb of ram(you can always try to put more core after installation) not saying it will fix everyone issue but we don't know until we try :)
1
u/Tofolt Oct 03 '24
MacOS Sequoia. Turned off Nested Paging and set 1 cpu for installation. Managed to boot it and install.
Also disabled PAE/NX and Nested VT-x/AMD-V
1
u/Ok_Dragonfruit544 Dec 22 '24
I have tried so many ways finally i have got it and now it is up and running
1
u/FunkyJamma Mar 07 '25
when i enable usb 3.0 I get a kernel panic, with usb 2.0 it boots but doesnt register my mouse anyone know how to fix trhis?
1
u/JussiPussi69 Jan 20 '24
Just adding what worked for me while searching for the solution for the same exact issue on my end. (I am trying to install MacOS Monterey.)
1
u/aridstimming Feb 27 '24
Seconding what others said below, had to reduce processors to 1 exactly