mirror of
https://github.com/sickcodes/Docker-OSX.git
synced 2026-01-13 22:03:28 +01:00
Sonoma won't work #546
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 @tyu1996 on GitHub (Nov 15, 2023).
So after the failed attempt to install Ventura (it just doesn't work even I followed #571), but I successfully installed the Monterey followed the issue mentioned. Installed Sonoma update from App Store, now it becomes an unending reboot loop.
Am going to re-install Sonoma from its recovery boot, will tell again if it works.
(I'm using Win 11 WSL2 Ubuntu Jammy for docker)
Edit: Returned a failed installation.
@sickcodes commented on GitHub (Nov 16, 2023):
Working on it rn
@RichardFevrier commented on GitHub (Nov 23, 2023):
Any way we can help to debug/dissect this problem @sickcodes ? (process, specific tools..)
@RichardFevrier commented on GitHub (Nov 23, 2023):
Here are some logs just in case.
@khmyznikov commented on GitHub (Nov 23, 2023):
@RichardFevrier I have the exact same issue with original OSX-KVM project
Same for Ventura/Sonoma
@RichardFevrier commented on GitHub (Nov 24, 2023):
Related to #714
@khmyznikov commented on GitHub (Nov 24, 2023):
Folks, try to install Big Sur first, then update to Sonoma, and change
-cpu Penrynto-cpu host@Heryk13 commented on GitHub (Nov 25, 2023):
i tried but when it asks for reboot the installation is where it fails, i tried changing the --restart flag too when running docker but no luck, tried --restart unless-stopped but it started restarting every 10 - 15 minutes even doing nothing and don't know why.
@guimox commented on GitHub (Nov 25, 2023):
I have this exact same problem when trying to install Sonoma in the OSX-KVM project from Kholia.
@voidarclabs commented on GitHub (Nov 27, 2023):
I've also had this issue. The Ventura installer fails to copy
bootbase.efiand crashes, Sonoma from the app store and from a recovery installer causes a bootloop regardless, and there aren't any current fixes. Having messed around with macOS in VMware for a while now, the bootlooping behaviour can be replicated by installing macOS 13 < and rebooting. From what research I've done, the reason that Ventura and above don't work for some is due to hardware limitations on Ryzen CPUs specifically, and is unavoidable save for some CPUID magic that we're unaware of. The issue most likely stems from the fact that Ventura supports M series chips as well as x86, and if there were some way to replicate an M1 CPUID that it would subvert the problem. Something to look into?@Heryk13 commented on GitHub (Nov 29, 2023):
wow it makes sense, my computer cpu is ryzen 7 5700U
@bluesailor45 commented on GitHub (Dec 1, 2023):
I do not think its related only to Ryzen processors. I have the same issue on my Intel Core i7-13700K processor
@HDK101 commented on GitHub (Dec 5, 2023):
I guess no one found a fix for this
@khmyznikov commented on GitHub (Dec 6, 2023):
For me
-cpu hostdid the trick, but need to install Big Sur first. I have 10 gen i7@Gucan commented on GitHub (Dec 6, 2023):
There are two problems with installing Sonoma.
First, you need to change the -cpu parameter to host, otherwise it will restart indefinitely when you try to start it after installation.
Second, during online installation, I don’t know why the recovery environment will try to download the installation resources of the arm series, resulting in an error that it cannot be found. bootbase.efi, just execute the following command after the disk tool formats the partition.
@ShiftHackZ commented on GitHub (Dec 7, 2023):
I can confirm this works. Just did a fresh install of Sonoma using this method with kholia/OSX-KVM.
@yaakovfeldman commented on GitHub (Dec 10, 2023):
This worked for me as well, using OSX-KVM. But using docker-osx is there anyway to override the cpu type?
Also Sonoma in OSX-KVM was much much slower and laggier than Ventura in docker-osx, on the same host and with the same resources - have others found this as well?
@bluesailor45 commented on GitHub (Dec 22, 2023):
I was able to install Ventura with OSX-KVM procedure after changing in the OpenCore-Boot.sh file to the '-cpu host' parameter. However I do not know how to change the -cpu parameter in the docker procedure (sickcodes/docker-OSX). In addition I do not understand how to execute the commands recommended after the disk format tool, as I understand this is the disk format tool within the MacOS Install.
Is anybod pleased to explain the exact procedures using the sickcodes/docker-OSX procedures?
@yaakovfeldman commented on GitHub (Dec 23, 2023):
To execute the commands just open Terminal, which is a menu option within the install environment.
To change the cpu parameter would probably involve rebuilding the dockerfile as it doesn’t seem to be exposed as configurable, although I assume @sickcodes will eventually update it as they are apparently working on support.
@bluesailor45 commented on GitHub (Dec 24, 2023):
I was able to install Ventura with sickcodes/docker-OSX only adding the "-e CORES=4 " to the docker coomand:
docker run -it
--device /dev/kvm
-p 50922:10022
-v /tmp/.X11-unix:/tmp/.X11-unix
-e "DISPLAY=${DISPLAY:-:0.0}"
-e GENERATE_UNIQUE=true
-e CORES=4
-e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist'
sickcodes/docker-osx:ventura
after several 'restarts' in the install process it finally installed OK. Only two problems as so far:
@ndrewh commented on GitHub (Jan 13, 2024):
fwiw, i was able to install sonoma using the sonoma branch (you may need to rebuild container to get latest OSX-KVM which appears to contain some important changes?).
I did need one change, courtesy of the venerable notes.md in OSX-KVM.
@awsms commented on GitHub (Jan 30, 2024):
I have to limit my Sonoma VM to a single CPU core/thread, otherwise it will freeze during boot. Wondering if someone else has the same issue.
@RichardFevrier commented on GitHub (Jan 30, 2024):
Nope 8 cores 2 threads for each.
@awsms commented on GitHub (Jan 31, 2024):
Same issue here:
https://github.com/sickcodes/Docker-OSX/issues/380#issuecomment-1505166214
Big Sur works fine for me though, only Sonoma requires this workaround (my CPU is a Ryzen 5 5600H)
@dumabg commented on GitHub (Feb 20, 2024):
On docker run, I put -e CPU=Haswell-noTSX and it works:
I don't need to do the mentioned by Gucan (mkdir ...) https://github.com/sickcodes/Docker-OSX/issues/715#issuecomment-1843299658
@andrewcharnley commented on GitHub (Feb 24, 2024):
I can also confirm doing the
-e CPU=Haswell-noTSXflag works. I have a Ryzen 5 5600G.I found pacman to be a major blocker to building the DockerFile and had to add the following to retry packages
So far Sonoma is installing well.
@mihalycsaba commented on GitHub (Mar 8, 2024):
Bit offtopic, but can you use Xcode with Sonoma? I still couldn't install it, getting all kind of weird errors with the installation. For example I don't have input if I use Haswell-noTSX on amd 5600g
@dumabg commented on GitHub (Mar 8, 2024):
Yes.
@mihalycsaba commented on GitHub (Mar 8, 2024):
I have managed to install Sonoma with Haswell-noTSX but keyboard and mouse input doesn't work.
@Lorena301 commented on GitHub (Mar 8, 2024):
Hi! I had the same problem. Have you been able to solve it?
@dmelo commented on GitHub (Mar 9, 2024):
I was able to get sonoma, after upgrading from Big Sur. But I'm having the same problem as @Lorena301 . The interface is not responding to mouse and keyboard. Any clue?
My CPU is an AMD Ryzen 7 3800X.
@skug67 commented on GitHub (Mar 24, 2024):
Same problem (no mouse/keyboard response) here.
@sickcodes commented on GitHub (Apr 8, 2024):
I've added Sonoma today, just pushing it to DockerHub as we speak.
@sickcodes commented on GitHub (Apr 8, 2024):
The mouse and keyboard issue was resolved here:
a208578bf0replaced
with
@awsms commented on GitHub (Apr 8, 2024):
Still having the issue where I can't boot to Sonoma unless I'm only giving a single CPU core to the VM. :(
@dmelo commented on GitHub (Apr 15, 2024):
@yaakovfeldman , have you managed to make Sonoma faster? I'm experiencing the same issue here.
@matias-tecnosoul commented on GitHub (Apr 29, 2024):
same here, sonoma very slow
@demian-mint commented on GitHub (Jun 3, 2024):
I tried updating Big sur to sonoma but it still reboots endlessly
@anas-baadshah commented on GitHub (Oct 27, 2024):
Any updates, anyone able to use Somona yet? We have managed to install the Sonoma but its keep opening the EFI disk rather than the boot volume we create. Its keep loading indefinitely. Any helps?