mirror of
https://github.com/sickcodes/Docker-OSX.git
synced 2026-01-11 21:10:25 +01:00
Big Sur: In memory panic stackshot succeeded #272
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @adieyal on GitHub (Nov 13, 2021).
I am able to get Catalina running but not Big Sur. After running the docker command, I see the bootloader, but when I select macOS Base System, the process gets stuck on In memory panic stackshot succeeded.
OS related issued, please help us identify the issue by posting the output of this
uname -a
; echo "${DISPLAY}"
; echo 1 | sudo tee /sys/module/kvm/parameters/ignore_msrs
; grep NAME /etc/os-release
; df -h .
; qemu-system-x86_64 --version
; libvirtd --version
; free -mh
; nproc
; egrep -c '(svm|vmx)' /proc/cpuinfo
; ls -lha /dev/kvm
; ls -lha /tmp/.X11-unix/
; ps aux | grep dockerd
; docker ps | grep osx
; grep "docker|kvm|virt" /etc/group
I've gone through the troubleshooting section in README. I also haven't seen this problem mentioned in any of the issues.
This is the command that I have been using
Any thoughts?
@adieyal commented on GitHub (Nov 13, 2021):
I just tried Monterey with the same outcome.
@sickcodes commented on GitHub (Nov 14, 2021):
I have experienced this too, and I had to reboot the host. I want to diagnose further
@adieyal commented on GitHub (Nov 14, 2021):
I rebooted and the installation process starts, it now gets stuck just before the installation wizard begins.

Not sure what to try next - I couldn't find a github issue that matches the problem any suggestions for what I should try next?
@sickcodes commented on GitHub (Nov 14, 2021):
I'm uploading and testing all new images today
@adieyal commented on GitHub (Nov 15, 2021):
Quick update - I pulled your most recent Monterey image but the installation stops in the same place.
@sickcodes commented on GitHub (Nov 15, 2021):
Do any other images work?
@adieyal commented on GitHub (Nov 16, 2021):
I just tried the Big Sur image on my AMD cpu and it works fine. I previously couldn't get any of the images working on that machine.
@sickcodes commented on GitHub (Nov 17, 2021):
Alright let me try all of them (full install) takes a while as you can imagine, I would like to get to the bottom of this
@adieyal commented on GitHub (Nov 18, 2021):
Let me know if you need me to test anything.
@MikeCoder96 commented on GitHub (Nov 19, 2021):
I'm experiencing a similar problem. When i start MacOS Base System first time it arrive here:


and restart.
After I get it:
Resetting the NVRAM seem to fix the problem in the last picture and continue to monterey but sometimes I got a reboot when i start erasing disk and sometime I got reboot when start loading the menu.
I have a I7 9750H, and this is the command I use
docker run -it --device /dev/kvm -p 922:10022 -e RAM=8 -e CORES=4 -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY:-:0.0}" -e GENERATE_UNIQUE=true -e AUDIO_DRIVER=alsa -e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' sickcodes/docker-osx:montereyEDIT: Found that only catalina work fine.
@sickcodes commented on GitHub (Nov 28, 2021):
Try this
-e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/lts/config-custom.plist'This is the previous commit before I synced with Kholia's new plist
I will give it a try right now
@MikeCoder96 commented on GitHub (Nov 29, 2021):
Seem to not boot.

@sickcodes commented on GitHub (Nov 30, 2021):
Reproduced, digging deeper. It was working last night 😂
@MikeCoder96 commented on GitHub (Dec 1, 2021):
https://github.com/reenigneorcim/SurPlus can be this a solution?
@Dewald928 commented on GitHub (Dec 10, 2021):
Mine was working fine with my docker data on the local drive. But then I moved my docker-data to an external drive, then I started getting this issue too.
@byrizki commented on GitHub (Apr 8, 2022):
any update on this? I have same issue, but it's randomly happened, sometimes it can go to apple logo, and install page but then it's reboot again. Big sur and below are working, only monterey I can't make boot
@JezausTevas commented on GitHub (Apr 26, 2022):
Disabling "Enable Nested VT-x/AMD-V" option seems to help. I am running on Ryzen 5900HX
@stevelam20 commented on GitHub (Jun 8, 2022):
i agree i disable that it works
@Saadhya commented on GitHub (Mar 10, 2023):
its already disabled in mine

Can anyone help here?
@niljoy commented on GitHub (Apr 8, 2023):
I have faced the same problem when booting memory panic stackshot succeeded...... then I simply disabled nested vt/amd-v from virtual box settings..... and it worked for me perfectly for me. Mac os ventura booted successfully.
@Zts0hg commented on GitHub (Apr 12, 2023):
I Reduce the processor from 4 CPU to 1 CPU and solve the problem.
@gthaka commented on GitHub (Oct 6, 2023):
@Zts0hg solution worked for me for Ventura. Thanks
@walterwootz commented on GitHub (Nov 29, 2023):
Awesome, it worked. Thank you!
@abuu-u commented on GitHub (Dec 24, 2023):
disabling c-state in bios helped me as suggested here: https://www.nicksherlock.com/2022/10/installing-macos-13-ventura-on-proxmox/comment-page-1/#comment-55532
@jules5509 commented on GitHub (Jan 6, 2024):
super mais comment faire pour que la vm ne lague pas maintenant ? avec 1 cpu c'est vraiment compliqué
@Collin8000 commented on GitHub (Feb 6, 2024):
Im still having this issue, any fixes? Im on ubuntu 22.04, tried ventura, monterrey, no avail. Might try to pre installed catalina but im wanting to run xocde, only a single gpu. Using a lenovo thinkpad t14 gen with amd ryzen 7 pro 4750U. Its using qemu and kvm, how do are you supposed to run virtualbox and why would you be doing so
@valimaties commented on GitHub (Feb 8, 2024):
Awesome, the solution with only one processor worked. Thanks!
Is there a way to use more than one processor? Because it is very laggy!
@Oopsys commented on GitHub (Feb 9, 2024):
Great It works with one CPU
@irludure commented on GitHub (Feb 27, 2024):
@Zts0hg solution worked perfectly for me
@awsms commented on GitHub (Mar 28, 2024):
No one found an alternative to limiting the whole OS to a single CPU core?
@JezausTevas commented on GitHub (Mar 28, 2024):
Nope, does not work with ryzen multithreading
@abuu-u commented on GitHub (Mar 28, 2024):
have you checked this ? worked for me
@awsms commented on GitHub (Mar 28, 2024):
Yep, didn't work unfortunately
@abdoulayeba5 commented on GitHub (Apr 18, 2024):
oh thanks it work for me too
@JAicewizard commented on GitHub (Jun 1, 2024):
Hello @Collin8000 (and others), I have ~the exact same laptop and for me what fixed it was updating bios. I was at 1.05, and updating t0 1.47 fixed this issue for me. I gave up on this docker version long ago, and started trying the one without docker. WIth some more persistence I fixed the issue using just qemu, so im sure it might fix the issue with qemu-in-docker as well.
@thegamerguy2021 commented on GitHub (Oct 26, 2024):
How do u do that?
@thegamerguy2021 commented on GitHub (Oct 26, 2024):
I'm having this same problem on trying to Install macOS Monterey on my brother's HP Envy x360 15-u110dx laptop from 2014 with a Intel Haswell processor.
Any fix?
@valimaties commented on GitHub (Oct 26, 2024):
As I see, your option is already disabled.
@thegamerguy2021 commented on GitHub (Oct 26, 2024):
I got past this error by using boot-arg cpus=1 to make the computer only use one core of processer.
@Arcmyx commented on GitHub (Dec 17, 2025):
I'm installing a Sonoma on VirtualBox and set CPUs to just 1, and it fixed the issue.