Hello, I have an unusual problem here. Everything goes through as normal then as it boots into the macOS Ventura installation screen it goes blank and says 'System Rebooted after Panic'
@@EpidemicTutorials-qh6de Hi, I get a message saying: "An error occurred preparing the software update" After I click OK, it asks me to select the system I want to start up my computer. But then there's no options to chose below there. How do I proceed? I was having the panic boot loop before.
The "automatically rebooted after panic" error during macOS Sonoma installation on VirtualBox is a common issue. Here are some steps you can try to resolve it: 1. **Reduce CPU Cores**: Set the number of CPU cores to 2 or fewer. You can do this in the VirtualBox settings under **System > Processor**³. 2. **Use Correct Boot Flags**: Add the following boot flags to your VM configuration. Open a terminal and run: ```sh VBoxManage setextradata "Your_VM_Name" "VBoxInternal/TM/TSCMode" "RealTSCOffset" ``` Replace `"Your_VM_Name"` with the actual name of your VM⁵. 3. **Update VirtualBox and Extensions**: Ensure you have the latest version of VirtualBox and the Extension Pack installed⁴. 4. **Check EFI Settings**: Make sure EFI is enabled in your VM settings. Go to **Settings > System > Motherboard** and check the **Enable EFI (special OSes only)** box¹. 5. **Adjust Memory and Graphics**: Sometimes, adjusting the memory and graphics settings can help. Try increasing the video memory to 128MB and ensuring you have at least 4GB of RAM allocated to the VM². 6. **Use Clover Configurator**: If you're using Clover as your bootloader, make sure your configuration is correct. You can use Clover Configurator to adjust settings and ensure compatibility¹. If these steps don't resolve the issue, you might want to check out detailed video tutorials on RUclips, such as [this one](ruclips.net/video/iUyvW1dOo7k/видео.html) or [this one](ruclips.net/video/J5AsQJX28s4/видео.html) for more specific guidance¹². Let me know if you need further assistance or if there's anything else I can help with!
I found a solution for this, you can mask the amd to intel, with the following command VBoxManage modifyvm "VM Name" --cpu-profile "Intel Core i7-6700K" Of course, you can use other model of intel, but well, is your decision
para los que tengan problema "in memory panic stackshot succeeded" simplemente cambien procesadores a 1 y reinicien la VM y listo. funcional. For those who have the problem "in memory panic stackshot succeeded" simply change processors to 1 and restart the VM and that's it. functional.
@@EpidemicTutorials-qh6de KP boot loop after the GUI portion of the install. 7.0.20 everything is updated. These guides (they're all basically the same) don't work on 13th gen. Lots of the same reports as I have. Not my first Mac OS install in VirtualBox. I tried running the Sonoma installer from my Mojave VM, but same thing, after the GUI part finishes it reboots and the progress bar runs for a while but eventually it enters a KP boot loop.
Hello, i have a bit of a different problem, my MacOS Ventura install after it is on the first part booting from the iso image, then it needs to restart but it just won't go to the next step with the apple logo, and it keeps booting from the iso image, fix?
Hi, I get a message saying: "An error occurred preparing the software update" After I click OK, it asks me to select the system I want to start up my computer. But then there's no options to chose below there. How do I proceed? I was having the panic boot loop before.
Ah, the infamous “error bdsdxe: failed to start boot0000” during macOS installation in VirtualBox-it’s like a digital hiccup that just won’t quit! But fear not, intrepid virtual explorer; we’ll get you out of that boot loop and back on the path to Mac-land. 🍎🌟 Here are a few steps to help you troubleshoot and break free from this loop: 1. Check Your Boot Order: o Sometimes the boot order gets a little mixed up, like a deck of virtual cards. o In your VM settings, make sure the virtual hard disk (where macOS is installed) is set as the first boot device. o You don’t want it endlessly chasing its tail by trying to boot from other devices. 2. EFI Shell Escape: o If you find yourself stuck in the EFI shell (like a digital castaway), try typing exit. o This should take you back to the VirtualBox boot menu. 3. Manual Boot from File: o From the boot menu, choose “Boot Maintenance Manager.” o Then select “Boot From File.” o Navigate to the location of your macOS boot file (usually System/Library/CoreServices/boot.efi). o Run it like a digital conductor waving a baton: fs0:System/Library/CoreServices/boot.efi. 4. The Magic of setup.nsh: o If you encounter messages about missing or unrecognized files (like “macOS Install DataLocked FilesBoot Filesboot.efi”), don’t panic! o Run setup.nsh (yes, it’s like casting a spell in the digital realm). o Then try booting again. 5. Community Wisdom: o Fellow adventurers have likely faced similar challenges. Check forums and discussions related to macOS installations on VirtualBox. o Sometimes they’ve discovered hidden treasure chests of solutions. 6. Patience and Persistence: o Virtual machines can be moody. Be patient during the boot process-it might run disk checks and repairs. o If all else fails, consider trying an older version of VirtualBox (sometimes stability varies across releases).
After installing, it reboots to macOS Update Assistant. Choose Startup Disk window is open, with the message "Select the system you want to use to start up your computer" and nothing follows. Only options are a gray "Restart..." button and the red close button on the upper left corner
this command: cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "VM Name" "VBoxInternal/TM/TSCMode" "RealTSCOffset" should fix the issue, plz check your machine settings and try agin
I keep on looping on kernel panic, even after applying all recommendations. I'll move onto VMWare now, but thanks a lot for all your efforts in helping people out there!
Hi @ecarran! I’m sorry to hear that you’re still facing kernel panic issues despite trying all the recommendations. Switching to VMWare sounds like a good plan. Thank you for your kind words and for giving it a shot with VirtualBox. If you need any help with VMWare or have any other questions, feel free to reach out. Good luck with your setup!
@@EpidemicTutorials-qh6de Yes. Thanks for the reply. It did succeded after 1. hour. Actually the problem is with my TP configuration. Monterey completed successfully but Ventura ending to reboot in panic although applied the configuration. But Monterey is qorking fine. Thank you.
Libsystem.b.dylib cannot be loaded, panic loop. Yes, all the usual suggestions tried, this TSC and specifying the processor profile as i7-6700K included. Intel processor actually, not AMD - this error is usually discussed on the net as specific to AMD processors lacking the AVX2 instruction set.
@@EpidemicTutorials-qh6de I don't have that much experience to share, finally. After more than a day of futile experimentation, I finally decided to leave VirtualBox. I could install macOS under Hyper-V without issues. And in hindsight, I'm very glad I did. MacOS under VB could never co-exist with other hypervisor solutions that I needed for other purposes in Windows, so I had to change it and reboot every time I needed to run anything on a virtual Mac. No more, everything works with the same setup now. Certainly, others might not experience the same problems I did but I really recommend to everyone to check out Hyper-V. I found it much more capable than the two well-known VM engines, actually.
reduce the cpu cores to 2, EFI Shell Troubleshooting: If you encounter an EFI shell prompt, type exit to exit the shell. You’ll be brought into an EFI text-mode GUI. Select “Boot Maintenance Manager” and then “Boot From File.” You should see two entries (PCI bus paths). Choose the appropriate one to continue the boot process24.
Hi @harsharaghu8004! Sorry to hear you’re experiencing a panic bootloop. Here are a few steps you can try to fix it: Check VirtualBox Settings: Ensure that your VirtualBox settings are correctly configured for macOS. This includes enabling EFI, setting the correct chipset, and allocating enough RAM and CPU cores. Update VirtualBox: Make sure you are using the latest version of VirtualBox and the Extension Pack. Reinstall macOS: Sometimes, a fresh installation can resolve persistent issues. Check Logs: Look at the VirtualBox logs for any specific error messages that might give more insight into the problem. If these steps don’t help, you might want to check out forums or communities dedicated to macOS on VirtualBox for more specific advice. Good luck!
You shouldn't get this error, this is not openCore! Please make sure to follow the steps correctly and download the required files from here or a trusted source
![Install MacOS 14 Sonoma on VirtualBox - Issue Fixed [2024]](http://i.ytimg.com/vi/VxRLEn60cEo/mqdefault.jpg)
Hello, I have an unusual problem here. Everything goes through as normal then as it boots into the macOS Ventura installation screen it goes blank and says 'System Rebooted after Panic'
I have made a video on that, check the video description
I’ve just switched to VMWare I couldn’t put up with the sh**
@@JustACar00001 Kesinlikle bende geçiyorum :D
@@EpidemicTutorials-qh6de Hi,
I get a message saying: "An error occurred preparing the software update"
After I click OK, it asks me to select the system I want to start up my computer. But then there's no options to chose below there.
How do I proceed? I was having the panic boot loop before.
Did not fixed for me. Reinstalled, still panic + reboots in loop. VirtualBox 7.0.18.
CPU?
@@EpidemicTutorials-qh6de Intel i7
I am still getting: This system was automatically rebooted after panic when trying to install macOS Sonoma
The "automatically rebooted after panic" error during macOS Sonoma installation on VirtualBox is a common issue. Here are some steps you can try to resolve it:
1. **Reduce CPU Cores**: Set the number of CPU cores to 2 or fewer. You can do this in the VirtualBox settings under **System > Processor**³.
2. **Use Correct Boot Flags**: Add the following boot flags to your VM configuration. Open a terminal and run:
```sh
VBoxManage setextradata "Your_VM_Name" "VBoxInternal/TM/TSCMode" "RealTSCOffset"
```
Replace `"Your_VM_Name"` with the actual name of your VM⁵.
3. **Update VirtualBox and Extensions**: Ensure you have the latest version of VirtualBox and the Extension Pack installed⁴.
4. **Check EFI Settings**: Make sure EFI is enabled in your VM settings. Go to **Settings > System > Motherboard** and check the **Enable EFI (special OSes only)** box¹.
5. **Adjust Memory and Graphics**: Sometimes, adjusting the memory and graphics settings can help. Try increasing the video memory to 128MB and ensuring you have at least 4GB of RAM allocated to the VM².
6. **Use Clover Configurator**: If you're using Clover as your bootloader, make sure your configuration is correct. You can use Clover Configurator to adjust settings and ensure compatibility¹.
If these steps don't resolve the issue, you might want to check out detailed video tutorials on RUclips, such as [this one](ruclips.net/video/iUyvW1dOo7k/видео.html) or [this one](ruclips.net/video/J5AsQJX28s4/видео.html) for more specific guidance¹².
Let me know if you need further assistance or if there's anything else I can help with!
This fixed my panic error using an AMD Ryzen box and MacOS 14. Thanks!
Ur welcome and thanks for the nice feedback :)
I found a solution for this, you can mask the amd to intel, with the following command
VBoxManage modifyvm "VM Name" --cpu-profile "Intel Core i7-6700K"
Of course, you can use other model of intel, but well, is your decision
para los que tengan problema "in memory panic stackshot succeeded" simplemente cambien procesadores a 1 y reinicien la VM y listo. funcional.
For those who have the problem "in memory panic stackshot succeeded" simply change processors to 1 and restart the VM and that's it. functional.
Thanks for sharing your experiance
Hay alggun botón especifico para reiniciar la VM? VM es virtual machine cierto?
I try this and the download goes on really well until the very end when it is about to finish downloading, and then it panics. Any solution?
This is the only solution for panic issue. Make sure to update everything and try again
yo did you manage to fix it?
any other fixes? I have the same problem and this doesn't work for me. Intel chip so it's not an AMD issue.
(I'm trying with MacOS 14 Sonoma but I tried with Monterey as well).
try installing it on vmware, I just posted a video yesterday about this.
my vm still bootloops, i ejected the iso, ran the command and reduced the cores to 1. any other ideas
not really, but make sure to update everything and try again
13700F, one core given to the VM. This did not fix the kernel panic loop after Sonoma install.
Make sure everything is updated, follow the tutorial again and if doesn't work please share any specific error so that I can help you
@@EpidemicTutorials-qh6de KP boot loop after the GUI portion of the install. 7.0.20 everything is updated. These guides (they're all basically the same) don't work on 13th gen. Lots of the same reports as I have. Not my first Mac OS install in VirtualBox. I tried running the Sonoma installer from my Mojave VM, but same thing, after the GUI part finishes it reboots and the progress bar runs for a while but eventually it enters a KP boot loop.
"This system was automatically rebooted after panic"
any recommendations for Vmware ?
Allocate only One CPU core
still throws panic errors... any fix ? any help ? atleast 2 or 3 other have asked the question about , repeated panics..
if you are using AMD and this video didn't fix you might need to install an older version of MacOS such as Montary.
@@EpidemicTutorials-qh6de nope, intel here, and i'll just need to give it a try with older OS's or move over to vmware
Hello, i have a bit of a different problem, my MacOS Ventura install after it is on the first part booting from the iso image, then it needs to restart but it just won't go to the next step with the apple logo, and it keeps booting from the iso image, fix?
It seems not. This problem exists all over the world.. I am the same.. I don’t know how you solved it..
@@c_3922 well i am on Linux and i didn't use VirtualBox, but i used Sosumi and ran MacOS Catalina from the program Sosumi
Eject the ISO file from settings/ storage and start the machine
Hi,
I get a message saying: "An error occurred preparing the software update"
After I click OK, it asks me to select the system I want to start up my computer. But then there's no options to chose below there.
How do I proceed? I was having the panic boot loop before.
make sure you have enough storage for your VM
error bdsdxe : failed to start boot0000
Ah, the infamous “error bdsdxe: failed to start boot0000” during macOS installation in VirtualBox-it’s like a digital hiccup that just won’t quit! But fear not, intrepid virtual explorer; we’ll get you out of that boot loop and back on the path to Mac-land. 🍎🌟
Here are a few steps to help you troubleshoot and break free from this loop:
1. Check Your Boot Order:
o Sometimes the boot order gets a little mixed up, like a deck of virtual cards.
o In your VM settings, make sure the virtual hard disk (where macOS is installed) is set as the first boot device.
o You don’t want it endlessly chasing its tail by trying to boot from other devices.
2. EFI Shell Escape:
o If you find yourself stuck in the EFI shell (like a digital castaway), try typing exit.
o This should take you back to the VirtualBox boot menu.
3. Manual Boot from File:
o From the boot menu, choose “Boot Maintenance Manager.”
o Then select “Boot From File.”
o Navigate to the location of your macOS boot file (usually System/Library/CoreServices/boot.efi).
o Run it like a digital conductor waving a baton: fs0:System/Library/CoreServices/boot.efi.
4. The Magic of setup.nsh:
o If you encounter messages about missing or unrecognized files (like “macOS Install DataLocked FilesBoot Filesboot.efi”), don’t panic!
o Run setup.nsh (yes, it’s like casting a spell in the digital realm).
o Then try booting again.
5. Community Wisdom:
o Fellow adventurers have likely faced similar challenges. Check forums and discussions related to macOS installations on VirtualBox.
o Sometimes they’ve discovered hidden treasure chests of solutions.
6. Patience and Persistence:
o Virtual machines can be moody. Be patient during the boot process-it might run disk checks and repairs.
o If all else fails, consider trying an older version of VirtualBox (sometimes stability varies across releases).
After installing, it reboots to macOS Update Assistant. Choose Startup Disk window is open, with the message "Select the system you want to use to start up your computer" and nothing follows. Only options are a gray "Restart..." button and the red close button on the upper left corner
this command: cd "C:\Program Files\Oracle\VirtualBox\"
VBoxManage setextradata "VM Name" "VBoxInternal/TM/TSCMode" "RealTSCOffset"
should fix the issue, plz check your machine settings and try agin
I keep on looping on kernel panic, even after applying all recommendations. I'll move onto VMWare now, but thanks a lot for all your efforts in helping people out there!
Hi @ecarran! I’m sorry to hear that you’re still facing kernel panic issues despite trying all the recommendations. Switching to VMWare sounds like a good plan. Thank you for your kind words and for giving it a shot with VirtualBox. If you need any help with VMWare or have any other questions, feel free to reach out. Good luck with your setup!
@@EpidemicTutorials-qh6de My VMWare virtual machine with MacOS is already up and running without any issue right now, thanks again.
Glad to hear that , sorry for late reply I had an accident and couldn't work on my channel for like two weeks
The second command causes me a big red error i dont understand why
please, share specific errors
thank you!!!
you're most welcome, thanks for subscribing to my channel
This didn't fix it for me for Sonoma. I'm using a Ryzen 5 5600X on the host.
Try a different CPU set , check the video description
@@EpidemicTutorials-qh6de I have this problem too. (Processor i5-13450HX) CPU sets dont helps
@@EpidemicTutorials-qh6de there isn't anything in the video description that explains how to switch to a different CPU set
you just need to replace the current CPU set on the command with another CPU from the list
@@EpidemicTutorials-qh6de How to determine the CPU set? I'm using Intel i7-1260P
Nice Tutorials, Thanks. But what about VBox guest Additions on MACOs Sonoma? 🤗
Coming soon
The boot loop issue fixed but a new issue arised. Stucked at less than a minute
Just leave it for an hour it should finish afterwards
@@EpidemicTutorials-qh6de Yes. Thanks for the reply. It did succeded after 1. hour. Actually the problem is with my TP configuration. Monterey completed successfully but Ventura ending to reboot in panic although applied the configuration. But Monterey is qorking fine. Thank you.
hi ! it still doesn't work for me even using this technique what can i do more ?
Share the situation and error codes so that i can help u bro
still doesn't work repeats installation over and over
This is the only fix to this problem, trying re configuring the machine and reinstall it maybe you forgot something
same in my case
Libsystem.b.dylib cannot be loaded, panic loop. Yes, all the usual suggestions tried, this TSC and specifying the processor profile as i7-6700K included. Intel processor actually, not AMD - this error is usually discussed on the net as specific to AMD processors lacking the AVX2 instruction set.
Sir this sound very convincing please share ur experience
@@EpidemicTutorials-qh6de I don't have that much experience to share, finally. After more than a day of futile experimentation, I finally decided to leave VirtualBox. I could install macOS under Hyper-V without issues. And in hindsight, I'm very glad I did. MacOS under VB could never co-exist with other hypervisor solutions that I needed for other purposes in Windows, so I had to change it and reboot every time I needed to run anything on a virtual Mac. No more, everything works with the same setup now. Certainly, others might not experience the same problems I did but I really recommend to everyone to check out Hyper-V. I found it much more capable than the two well-known VM engines, actually.
@@gabor7928 thanks for the information i must do s video on that
it still reboots in panic, sadly...
how did you fix it? I still have this error message
this is the only fix i could find sorry, make sure to get everything updated and start fresh
@@EpidemicTutorials-qh6de I tried it multiple times, but still reboots in panic...
@@mrs._catty did u make sure virtualization is enabled? Do u have AMD or Intel? Try allocating only one cpu core
@@EpidemicTutorials-qh6de I have Intel core, I have virtualization enabled, mb problem that I have laptop on windows 10?
i am using a linux computer and i knew that was not going to fix it for me
reduce the cpu cores to 2, EFI Shell Troubleshooting:
If you encounter an EFI shell prompt, type exit to exit the shell.
You’ll be brought into an EFI text-mode GUI.
Select “Boot Maintenance Manager” and then “Boot From File.”
You should see two entries (PCI bus paths). Choose the appropriate one to continue the boot process24.
guys try to use 1 cpu it fixed the issue for me
Thank you so much for your contributions
Thx
Ur welcome 🤗
Panic bootloop after tried everything. Video recording - ruclips.net/video/bz9_urHJ_yQ/видео.html
Hi @harsharaghu8004! Sorry to hear you’re experiencing a panic bootloop. Here are a few steps you can try to fix it:
Check VirtualBox Settings: Ensure that your VirtualBox settings are correctly configured for macOS. This includes enabling EFI, setting the correct chipset, and allocating enough RAM and CPU cores.
Update VirtualBox: Make sure you are using the latest version of VirtualBox and the Extension Pack.
Reinstall macOS: Sometimes, a fresh installation can resolve persistent issues.
Check Logs: Look at the VirtualBox logs for any specific error messages that might give more insight into the problem.
If these steps don’t help, you might want to check out forums or communities dedicated to macOS on VirtualBox for more specific advice. Good luck!
it still crushing (im with intel)
Crushing depends on your devices Specs, do u get any error codes or stop codes?
i have error: Couldn't alloc class "ApplekeyStoreTest"
ACPI: console relocated to 0xe00000000
You shouldn't get this error, this is not openCore! Please make sure to follow the steps correctly and download the required files from here or a trusted source