Closed mikob closed 3 years ago
It will be a struggle to upgrade from Big Sur from Catalina, since one uses HFS and the other uses APFS, you're better off creating a Big Sur, and just rsyncing the data across. You can use hfs progs to mount the old disk from the host, and then rsync it into the new container.
@sickcodes thanks for the quick response. This was my attempt at creating a Big Sur image from scratch. I didn't bring over the old image. The errors are after a fresh install :/
I tried it again this morning and wrote down my steps. Didn't use the naked image at all this time.
docker run --device /dev/kvm -p 50922:10022 -e "DISPLAY=${DISPLAY:-:0.0}" -v /tmp/.X11-unix:/tmp/.X11-unix -e GENERATE_UNIQUE=true -e MASTER_PLIST_URL=https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist -ti --name mac6 sickcodes/docker-osx:big-sur
Here the same aforementioned error appears.
@sickcodes I just tried the sickcodes/docker-osx:auto
image based on the comment here: https://github.com/sickcodes/Docker-OSX/pull/158#issuecomment-787060331 (auto-big-sur doesn't seem to exist) but the auto image has Catalina.
Can you confirm that you have the latest version? docker pull sickcodes/docker-osx:big-sur
I'm testing now
Got it working finally! The issue was virtlogd wasn't running. I copied and pasted the commands that included:
...
sudo systemctl enable --now virtlogd
...
So not sure exactly how it happened. Thanks for your attentiveness!
No worries!
I have the same issue at the moment, just updated arch linux, started libvirtd and virtlogd, /sys/module/kvm/parameters/ignore_msrs
set to Y, and loaded kvm, using big-sur. Do you have any tips for debugging this?
I had everything working before with Catalina and this docker image you provided, thank you! Unfortunately, I needed to upgrade to Big Sur to install the latest XCode and stay compatible. Using upgrade through the MacOS interface didn't seem to work, after restarting, it would still be on Catalina. So I pulled the latest image:
sickcodes/docker-osx:big-sur
(ee7fe01fa6e8) and the latest naked:sickcodes/docker-osx:naked
(45f7cd41be3b) and ran the fresh install on the former, and moved the new image to the latter. Now I can't boot after selecting the drive in the QEMU menu. QEMU is in an endless loop with logs that look like this:In QEMU:
I run the docker image this way:
docker run --privileged -p 8081:8081 -p 50922:10022 --ulimit memlock=-1:-1 -e "DISPLAY=${DISPLAY:-:0.0}" -v /tmp/.X11-unix:/tmp/.X11-unix -e GENERATE_UNIQUE=true -e MASTER_PLIST_URL=https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist -tid --name mac5 -e NOPICKER=true -e IMAGE_PATH=/image/mac_hdd_ng.img -v mac-img-2:/image sickcodes/docker-osx:naked
In docker logs:
OS related issued, please help us identify the issue by posting the output of this