Docker-OSX
Docker-OSX copied to clipboard
sickcodes
Big Sur: In memory panic stackshot succeeded
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
Linux xps-box 5.10.68-1-MANJARO #1 SMP PREEMPT Wed Sep 22 12:29:47 UTC 2021 x86_64 GNU/Linux
:0
1
NAME="Manjaro Linux"
PRETTY_NAME="Manjaro Linux"
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/luks-e41457f4-a9e3-4f31-87e4-8365507c3181 452G 268G 161G 63% /
QEMU emulator version 6.1.0
Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers
libvirtd (libvirt) 7.8.0
total used free shared buff/cache available
Mem: 15Gi 10Gi 299Mi 1.8Gi 4.0Gi 2.0Gi
Swap: 16Gi 4.5Gi 12Gi
8
16
crw-rw-rw- 1 root kvm 10, 232 Nov 13 13:51 /dev/kvm
total 0
drwxrwxrwt 2 root root 80 Oct 31 09:35 .
drwxrwxrwt 29 root root 800 Nov 13 14:33 ..
srwxr-xr-x 1 adi adi 0 Oct 31 09:35 X0
srwxr-xr-x 1 adi adi 0 Oct 31 09:35 X1
root 547362 0.1 0.2 2418796 37588 ? Ssl 13:37 0:06 /usr/bin/dockerd -H fd://
adi 698413 0.0 0.0 6496 2308 pts/4 S+ 14:36 0:00 grep dockerd
209c6b81bd47 sickcodes/docker-osx:big-sur "/bin/bash -c 'sudo …" 44 minutes ago Up 44 minutes 0.0.0.0:50923->10022/tcp, :::50923->10022/tcp festive_grothendieck
6895b58f973a sickcodes/docker-osx:latest "/bin/bash -c 'sudo …" 50 minutes ago Up 50 minutes 0.0.0.0:50922->10022/tcp, :::50922->10022/tcp charming_moser
kvm:x:992:adi
docker:x:963:adi
libvirt:x:960:adi
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
docker run -it \
--device /dev/kvm \
-p 50922:10022 \
-v /tmp/.X11-unix:/tmp/.X11-unix \
-e "DISPLAY=${DISPLAY:-:0.0}" \
sickcodes/docker-osx:big-sur
Any thoughts?
I have experienced this too, and I had to reboot the host. I want to diagnose further
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?
Quick update - I pulled your most recent Monterey image but the installation stops in the same place.
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.
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
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:monterey
EDIT: Found that only catalina work fine.
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
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.
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
Disabling "Enable Nested VT-x/AMD-V" option seems to help. I am running on Ryzen 5900HX
Disabling "Enable Nested VT-x/AMD-V" option seems to help. I am running on Ryzen 5900HX
i agree i disable that it works
its already disabled in mine
Can anyone help here?
Disabling "Enable Nested VT-x/AMD-V" option seems to help. I am running on Ryzen 5900HX
i agree i disable that it works
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.
I Reduce the processor from 4 CPU to 1 CPU and solve the problem.
Awesome, it worked. Thank you!
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
Je réduis le processeur de 4 CPU à 1 CPU et résous le problème.
super mais comment faire pour que la vm ne lague pas maintenant ? avec 1 cpu c'est vraiment compliqué
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
Awesome, the solution with only one processor worked. Thanks!
Is there a way to use more than one processor? Because it is very laggy!
