Open jbramburek opened 1 month ago
I have no clue why this happens. Only solution I can offer right now is to use an older version, like Ventura.
I am also having this issue.
I have no clue why this happens. Only solution I can offer right now is to use an older version, like Ventura.
Also happened on ventura
Its not so useful to just hear "happens to me too", it would be better to include docker logfile like @jbramburek did.
That way we can try to track down under which circumstances this happens. For example, do you all have an "AMD Ryzen 5 4600G" processor like @jbramburek or do you all have a weird clocksource (@jbramburek has kvm-clock
which is very strange, like he uses nested virtualization?), etc. Only if we discover what you guys all share in common, we can figure out what is causing this.
@urfavteddybear So you get the same message:
unexpected clocksource: kvm-clock
?
Exactly. It happens on Sequoia, Sonoma, Ventura, and Monterey. I haven't tried Big Sur yet, though it seems fine when running on 1 CPU.
I created a new version now (v1.14) that will automaticly detect nested virtualization and restricts the container to a single core when the default of 2 was selected. To prevent this problem for new users.
But ofcourse this doesnt solve the root problem, that macOS crashes when using nested virtualization on AMD in combination with multiple cores.
However Im afraid I will not be able to solve it. Either it is a problem in macOS, or in OpenCore or in QEMU/KVM.
Is there any good reason why you run this container with nested virtualization? I never expected anyone to do so. Because if you already have a way to run VM's there seems no need for a container that can run a VM?
I am running this in a VM on my Proxmox server. I haven't really explored other options to get this os so far.
@jbramburek I would advice to install macOS directly in Proxmox then, instead of using this container. This project is more for people that do not have Proxmox but just Docker.
Somehow I can make it work on AMD EPYC 7443P but not with Ryzen series.
Operating system
Ubuntu 24.04
Description
Running docker image 1.10 (see https://github.com/dockur/macos/issues/83) with 1 CPU I can get Sonoma installed and it seems to work. Changing to 4 or 2 CPUs however makes the masOS crash on boot. After changing back to 1 CPU the system starts again. The bug report macOS generates is attached.
Docker compose
Docker log
docker compose logs
MasOS bug report
Screenshots (optional)
No response