Fix Boot loop System Panic macOS Installation on VirtualBox | 2024

Поделиться
HTML-код
  • Опубликовано: 11 сен 2024
  • New Video out there!: • 5 Awesome Ways to use ...
    Check out our new video on how to install macOS Big Sur on VirtualBox | all AMD CPUs are supported!: • Install MacOS Big Sur ...
    If you encountered any issues let me know in the comments: / @epidemictutorials-qh6de
    How to Install MacOS Ventura on VirtualBox: • Install MacOS 13 Ventu...
    How to Install MacOS Sonoma on VirtualBox: • Install MacOS 14 Sonom...
    How to Install MacOS Sonoma on VMware: • Install MacOS Sonoma o...
    Commands:
    cd "C:\Program Files\Oracle\VirtualBox\"
    VBoxManage setextradata "VM Name" "VBoxInternal/TM/TSCMode" "RealTSCOffset"
    Buy me a cup of coffee: buymeacoffee.c...

Комментарии • 101

  • @RossBeck
    @RossBeck 4 месяца назад +2

    This fixed my panic error using an AMD Ryzen box and MacOS 14. Thanks!

    • @EpidemicTutorials-qh6de
      @EpidemicTutorials-qh6de  4 месяца назад +1

      Ur welcome and thanks for the nice feedback :)

    • @gabrielchacon1896
      @gabrielchacon1896 3 месяца назад

      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

  • @ecarran
    @ecarran 25 дней назад +1

    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!

    • @EpidemicTutorials-qh6de
      @EpidemicTutorials-qh6de  17 дней назад +1

      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!

    • @ecarran
      @ecarran 17 дней назад

      @@EpidemicTutorials-qh6de My VMWare virtual machine with MacOS is already up and running without any issue right now, thanks again.

    • @EpidemicTutorials-qh6de
      @EpidemicTutorials-qh6de  17 дней назад +1

      Glad to hear that , sorry for late reply I had an accident and couldn't work on my channel for like two weeks

  • @piggy004
    @piggy004 5 месяцев назад +6

    It still doesn’t work for me. When I installed macOS 14 beta, it would keep panicking.

    • @EpidemicTutorials-qh6de
      @EpidemicTutorials-qh6de  4 месяца назад

      if you are using AMD try installing an older version of macos like montary

    • @piggy004
      @piggy004 4 месяца назад

      @@EpidemicTutorials-qh6de I have Intel Celeron N4000

    • @piggy004
      @piggy004 4 месяца назад

      @@EpidemicTutorials-qh6de And it might be AMD64 as it can run Java and others

    • @sr.morningstar97
      @sr.morningstar97 3 месяца назад

      you can solved?

  • @J4y_boi
    @J4y_boi 2 месяца назад +3

    my vm still bootloops, i ejected the iso, ran the command and reduced the cores to 1. any other ideas

  • @Turkey00001
    @Turkey00001 2 месяца назад +4

    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
      @EpidemicTutorials-qh6de  2 месяца назад +1

      I have made a video on that, check the video description

    • @Turkey00001
      @Turkey00001 2 месяца назад +1

      I’ve just switched to VMWare I couldn’t put up with the sh**

    • @MaydayAlish
      @MaydayAlish Месяц назад

      @@Turkey00001 Kesinlikle bende geçiyorum :D

    • @sebastianpineda1058
      @sebastianpineda1058 29 дней назад

      @@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.

  • @homeroaddams3434
    @homeroaddams3434 11 дней назад +1

    Nice Tutorials, Thanks. But what about VBox guest Additions on MACOs Sonoma? 🤗

  • @Arvy
    @Arvy Месяц назад +3

    Did not fixed for me. Reinstalled, still panic + reboots in loop. VirtualBox 7.0.18.

  • @Master-ExcelVBA
    @Master-ExcelVBA Месяц назад +2

    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.

  • @gj5866
    @gj5866 3 дня назад

    I am still getting: This system was automatically rebooted after panic when trying to install macOS Sonoma

  • @sebastianpineda1058
    @sebastianpineda1058 29 дней назад +1

    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.

  • @nafismahim6190
    @nafismahim6190 2 месяца назад +2

    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?

    • @EpidemicTutorials-qh6de
      @EpidemicTutorials-qh6de  2 месяца назад

      This is the only solution for panic issue. Make sure to update everything and try again

    • @brueing
      @brueing Месяц назад

      yo did you manage to fix it?

  • @rodrigobarbosa6381
    @rodrigobarbosa6381 10 дней назад

    thank you!!!

  • @VillageInn92
    @VillageInn92 3 месяца назад +1

    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

    • @EpidemicTutorials-qh6de
      @EpidemicTutorials-qh6de  3 месяца назад

      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

  • @CeGe000
    @CeGe000 4 месяца назад +2

    still throws panic errors... any fix ? any help ? atleast 2 or 3 other have asked the question about , repeated panics..

    • @EpidemicTutorials-qh6de
      @EpidemicTutorials-qh6de  4 месяца назад

      if you are using AMD and this video didn't fix you might need to install an older version of MacOS such as Montary.

    • @CeGe000
      @CeGe000 4 месяца назад +1

      @@EpidemicTutorials-qh6de nope, intel here, and i'll just need to give it a try with older OS's or move over to vmware

  • @user-kk1vt7qs1p
    @user-kk1vt7qs1p 4 месяца назад +2

    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?

    • @c_3922
      @c_3922 4 месяца назад +1

      It seems not. This problem exists all over the world.. I am the same.. I don’t know how you solved it..

    • @user-kk1vt7qs1p
      @user-kk1vt7qs1p 4 месяца назад

      @@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

    • @EpidemicTutorials-qh6de
      @EpidemicTutorials-qh6de  4 месяца назад +1

      Eject the ISO file from settings/ storage and start the machine

  • @anaismoutarlier3220
    @anaismoutarlier3220 4 месяца назад +2

    any other fixes? I have the same problem and this doesn't work for me. Intel chip so it's not an AMD issue.

    • @anaismoutarlier3220
      @anaismoutarlier3220 4 месяца назад +1

      (I'm trying with MacOS 14 Sonoma but I tried with Monterey as well).

    • @EpidemicTutorials-qh6de
      @EpidemicTutorials-qh6de  4 месяца назад

      try installing it on vmware, I just posted a video yesterday about this.

  • @eliogamer503
    @eliogamer503 3 месяца назад +1

    i have error: Couldn't alloc class "ApplekeyStoreTest"
    ACPI: console relocated to 0xe00000000

    • @EpidemicTutorials-qh6de
      @EpidemicTutorials-qh6de  3 месяца назад

      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

  • @rootbeer666
    @rootbeer666 11 дней назад +1

    13700F, one core given to the VM. This did not fix the kernel panic loop after Sonoma install.

    • @EpidemicTutorials-qh6de
      @EpidemicTutorials-qh6de  5 дней назад

      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

    • @rootbeer666
      @rootbeer666 5 дней назад

      @@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.

    • @rootbeer666
      @rootbeer666 5 дней назад

      "This system was automatically rebooted after panic"

  • @missya3047
    @missya3047 Месяц назад +1

    The second command causes me a big red error i dont understand why

  • @said_eng_fluent
    @said_eng_fluent 2 месяца назад +1

    Loop panic has been resolved, however I face another problem which is providing me option to install the os again

    • @EpidemicTutorials-qh6de
      @EpidemicTutorials-qh6de  2 месяца назад +2

      after installation open machine settings and eject the ISO file

    • @said_eng_fluent
      @said_eng_fluent 2 месяца назад

      @@EpidemicTutorials-qh6de thank you, sir. Will do it

  • @lesderid
    @lesderid 5 месяцев назад +1

    This didn't fix it for me for Sonoma. I'm using a Ryzen 5 5600X on the host.

    • @EpidemicTutorials-qh6de
      @EpidemicTutorials-qh6de  5 месяцев назад +1

      Try a different CPU set , check the video description

    • @ReturnMeVoid
      @ReturnMeVoid 5 месяцев назад

      @@EpidemicTutorials-qh6de I have this problem too. (Processor i5-13450HX) CPU sets dont helps

    • @NickHa
      @NickHa 5 месяцев назад +1

      @@EpidemicTutorials-qh6de there isn't anything in the video description that explains how to switch to a different CPU set

    • @EpidemicTutorials-qh6de
      @EpidemicTutorials-qh6de  5 месяцев назад

      you just need to replace the current CPU set on the command with another CPU from the list

    • @joyyang1215
      @joyyang1215 4 месяца назад +1

      @@EpidemicTutorials-qh6de How to determine the CPU set? I'm using Intel i7-1260P

  • @mrs._catty
    @mrs._catty 2 месяца назад +5

    it still reboots in panic, sadly...

    • @Carmon245
      @Carmon245 2 месяца назад

      how did you fix it? I still have this error message

    • @EpidemicTutorials-qh6de
      @EpidemicTutorials-qh6de  2 месяца назад

      this is the only fix i could find sorry, make sure to get everything updated and start fresh

    • @mrs._catty
      @mrs._catty 2 месяца назад

      @@EpidemicTutorials-qh6de I tried it multiple times, but still reboots in panic...

    • @EpidemicTutorials-qh6de
      @EpidemicTutorials-qh6de  2 месяца назад

      @@mrs._catty did u make sure virtualization is enabled? Do u have AMD or Intel? Try allocating only one cpu core

    • @mrs._catty
      @mrs._catty 2 месяца назад

      @@EpidemicTutorials-qh6de I have Intel core, I have virtualization enabled, mb problem that I have laptop on windows 10?

  • @sanhd7994
    @sanhd7994 Месяц назад +1

    error bdsdxe : failed to start boot0000

    • @EpidemicTutorials-qh6de
      @EpidemicTutorials-qh6de  Месяц назад

      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).

  • @sonytt3
    @sonytt3 4 месяца назад +1

    still doesn't work repeats installation over and over

    • @EpidemicTutorials-qh6de
      @EpidemicTutorials-qh6de  4 месяца назад

      This is the only fix to this problem, trying re configuring the machine and reinstall it maybe you forgot something

    • @said_eng_fluent
      @said_eng_fluent 2 месяца назад

      same in my case

  • @YOUTUBEREALONE
    @YOUTUBEREALONE 5 месяцев назад +2

    i am using a linux computer and i knew that was not going to fix it for me

    • @EpidemicTutorials-qh6de
      @EpidemicTutorials-qh6de  4 месяца назад

      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.

  • @robinaijaz3137
    @robinaijaz3137 2 месяца назад

    hi ! it still doesn't work for me even using this technique what can i do more ?

  • @malibu6443
    @malibu6443 2 месяца назад

    Thx

  • @harsharaghu8004
    @harsharaghu8004 24 дня назад +1

    Panic bootloop after tried everything. Video recording - ruclips.net/video/bz9_urHJ_yQ/видео.html

    • @EpidemicTutorials-qh6de
      @EpidemicTutorials-qh6de  17 дней назад

      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!

  • @user-ls9id2ki5n
    @user-ls9id2ki5n 3 месяца назад

    it still crushing (im with intel)

    • @EpidemicTutorials-qh6de
      @EpidemicTutorials-qh6de  3 месяца назад

      Crushing depends on your devices Specs, do u get any error codes or stop codes?

  • @said_eng_fluent
    @said_eng_fluent 2 месяца назад +1

    Whenever I remove the iso image after the successful installation (in order to avoid for reinstalling the macos), I came up with the following prompts below:
    nx_mount:1297: os.clone.dmg initializing cache w/hash_size_512 and cache size 2048
    nx_mount:1639: os.clone.dmg checkpoint search: largest xid 20, best xid 20 @ 9
    Any recommendations?

    • @EpidemicTutorials-qh6de
      @EpidemicTutorials-qh6de  2 месяца назад

      1. **Check Boot Order**:
      - Make sure that your virtual machine (VM) is set to boot from the correct source. Follow these steps:
      - Highlight your macOS VM in VirtualBox.
      - Click on the "Settings" cog.
      - Select "System" from the side menu.
      - Ensure that "Floppy" is unchecked in the "Boot Order" settings. This ensures that your VM boots from your macOS ISO image.
      - Set the "Base Memory" to a suitable level (e.g., 2048MB minimum) ².
      2. **Monitor System Resources**:
      - Ensure that your host system meets the necessary specifications for running macOS on VirtualBox:
      - At least 8GB RAM (preferably 16GB or more).
      - A processor with at least four cores.
      - Sufficient free disk space (at least 50GB) ¹.
      3. **Update VirtualBox and Extension Pack**:
      - Make sure you're using the latest version of VirtualBox and have installed the VirtualBox Extension Pack. The Extension Pack provides additional functionality, including USB support ¹.
      4. **Check Installation Media**:
      - Verify that your macOS ISO file is intact and compatible with your VirtualBox version.
      - If you created the ISO file from macOS installation files, ensure it was done correctly.
      5. **Monitor Installation Progress**:
      - Sometimes the installation process may appear to stall, especially during the final stages. Be patient and allow it to complete.
      - If it consistently freezes at the same point, consider creating a new VM and reinstalling macOS.

    • @said_eng_fluent
      @said_eng_fluent 2 месяца назад

      @@EpidemicTutorials-qh6de even though I fail every time to install macos, it gave me real experience. Challenges are bonuses in my case, thanks!

    • @EpidemicTutorials-qh6de
      @EpidemicTutorials-qh6de  Месяц назад

      What happened?

    • @said_eng_fluent
      @said_eng_fluent Месяц назад

      @@EpidemicTutorials-qh6de A friend of mine gave me his macbook temporarily, and I had managed update to sonoma.