Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

macOS 14 Sonoma on Unsupported Macs Thread

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
deeveedee said:
@Sven G and @MacinMan I'm not sure if I'm allowed to say this and if I'm not, MacRumor's admins are free to delete this...

Acidanthera, the folks behind Open Core, provide kexts for patching macOS so that it runs in a Hyper-V VM. I haven't used the solution, but I've seen others who are quite happy. This might be another option for you.

EDIT: Version 0.9.4 of the Acidanthera solution was the first to provide Hyper-V VM support for Sonoma. Acidanthera has released version 0.9.6.
Click to expand...
That's good to know, I'll look into that. I don't see anything wrong with your post. These threads are targeted toward running newer versions of macOS on older Macs Apple has dropped support for. Open Core Legacy Patcher is just ONE solution for this. VMs are another.
 
@MacinMan I agree that it's a great post. But I think running macOS in a Hyper-V VM violates Apple's EULA.

EDIT: Hyper-V is a Microsoft Type-1 hypervisor running VMs on 'generic' Intel hardware. Apple's EULA only allows macOS VMs to run in a Type-2 hypervisor where macOS is the host OS running on a genuine Apple Mac.
 
Last edited:
Sonoma Beta3 installed OTA on iMac 13,2 (without issues) on an internal (fusion) and an external (SSD) drives.
Used OCLP 1.1n

Installation of Sonoma Beta3 on a MacBook Pro 5,2, however, failed after the first reboot following "preparation stage" of an OTA update. Progress bar freezes immediately after reboot. OCLP 1,1n used in all cases.
I installed Sonoma Beta3 on an external SSD (Samsung shield T7) using iMac 13,2 (see above), but patched the drive with OCLP set for MacBook Pro 5,2. Connected external drive to MacBook directly to machine's USB port, and separately, via a USB hub, in both instances progress bar froze immediately after it became visible.
Post restart (into well functioning Sonoma Beta1 installation) a panic report was generated.

I noticed another poster had similar experience, though on a different machine; see post 2253 on this page.


panic(cpu 1 caller 0xffffff800bf890e3): Kernel trap at 0xffffff800e4fdef1, type 14=page fault, registers:


CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x0000000010828000, CR4: 0x00000000000026e0


RAX: 0x0000000004000000, RBX: 0xffffff8bf522ac00, RCX: 0xffffff800bc54b18, RDX: 0x0000000000000001


RSP: 0xffffffaaafa5bbf0, RBP: 0xffffffaaafa5bc60, RSI: 0xffffff800cca5338, RDI: 0x0000000000000000


R8: 0x00000000000c000c, R9: 0x000000000000000c, R10: 0x00000000150352cb, R11: 0x1000443891f78043


R12: 0xffffff800cca5338, R13: 0xffffff90c1e34800, R14: 0x00000000e00002f0, R15: 0x0000000000000001


RFL: 0x0000000000010297, RIP: 0xffffff800e4fdef1, CS: 0x0000000000000008, SS: 0x0000000000000000


Fault CR2: 0x0000000000000000, Error code: 0x0000000000000000, Fault CPU: 0x1, PL: 0, VF: 1





Panicked task 0xffffff8bf529b008: 102 threads: pid 0: kernel_task


Backtrace (CPU 1), panicked thread: 0xffffff9a5b0040c8, Frame : Return Address


0xffffffaaafa5b570 : 0xffffff800be3ada1 mach_kernel : _handle_debugger_trap + 0x4b1


0xffffffaaafa5b5c0 : 0xffffff800bf994f0 mach_kernel : _kdp_i386_trap + 0x110


0xffffffaaafa5b600 : 0xffffff800bf88c3c mach_kernel : _kernel_trap + 0x55c


0xffffffaaafa5b680 : 0xffffff800bdd7971 mach_kernel : _return_from_trap + 0xc1


0xffffffaaafa5b6a0 : 0xffffff800be3b08d mach_kernel : _DebuggerTrapWithState + 0x5d


0xffffffaaafa5b790 : 0xffffff800be3a733 mach_kernel : _panic_trap_to_debugger + 0x1e3


0xffffffaaafa5b7f0 : 0xffffff800c5da24b mach_kernel : _panic + 0x84


0xffffffaaafa5b8e0 : 0xffffff800bf890e3 mach_kernel : _sync_iss_to_iks + 0x2c3


0xffffffaaafa5ba60 : 0xffffff800bf88dc7 mach_kernel : _kernel_trap + 0x6e7


0xffffffaaafa5bae0 : 0xffffff800bdd7971 mach_kernel : _return_from_trap + 0xc1


0xffffffaaafa5bb00 : 0xffffff800e4fdef1 com.apple.iokit.IOUSBHostFamily : __ZN16AppleUSBHostPort15setPortLocationEj + 0xb5


0xffffffaaafa5bc60 : 0xffffff800fc8811b com.apple.driver.usb.AppleUSBOHCI : __ZN16AppleUSBOHCIPort24portsCreatedMessageGatedEv + 0x17


0xffffffaaafa5bc80 : 0xffffff800e4fb894 com.apple.iokit.IOUSBHostFamily : __ZN16AppleUSBHostPort5startEP9IOService + 0x180


0xffffffaaafa5bd30 : 0xffffff800fc85784 com.apple.driver.usb.AppleUSBOHCI : __ZN16AppleUSBOHCIPort5startEP9IOService + 0x8a


0xffffffaaafa5bd80 : 0xffffff800fcb52d8 com.apple.driver.usb.AppleUSBOHCIPCI : __ZN15AppleUSBOHCIPCI11createPortsEv + 0x1e4


0xffffffaaafa5bdf0 : 0xffffff800e4f39c5 com.apple.iokit.IOUSBHostFamily : __ZN22AppleUSBHostController31controllerRegisteredGatedPhase1Ev + 0x27b


0xffffffaaafa5be20 : 0xffffff800c511318 mach_kernel : __ZN13IOCommandGate9runActionEPFiP8OSObjectPvS2_S2_S2_ES2_S2_S2_S2_ + 0xa8


0xffffffaaafa5be80 : 0xffffff800e4f36f3 com.apple.iokit.IOUSBHostFamily : __ZN22AppleUSBHostController30controllerRegisteredThreadCallEP11thread_call + 0x31


0xffffffaaafa5bea0 : 0xffffff800be94ad8 mach_kernel : _thread_call_delayed_timer + 0x508


0xffffffaaafa5bee0 : 0xffffff800be95b68 mach_kernel : _thread_call_delayed_timer + 0x1598


0xffffffaaafa5bfa0 : 0xffffff800bdd719e mach_kernel : _call_continuation + 0x2e


Kernel Extensions in backtrace:


com.apple.iokit.IOUSBHostFamily(1.2)[EBBE93B4-5667-3BC4-BC71-6C694409CFB6]@0xffffff800e4e0000->0xffffff800e558fff


dependency: com.apple.driver.AppleBusPowerController(1.0)[CE07B87D-8655-34ED-B009-ADE4D2194529]@0xffffff800d156000->0xffffff800d159fff


dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[C9234674-F244-3A8E-A378-654FDF80C336]@0xffffff800d46c000->0xffffff800d4a2fff


dependency: com.apple.driver.AppleSMC(3.1.9)[452EA208-4E08-3D68-A294-1C0DC5323BAE]@0xffffff800d554000->0xffffff800d56ffff


dependency: com.apple.driver.usb.AppleUSBCommon(1.0)[62DBDC1B-3512-3B81-8627-3CFAC56298FE]@0xffffff800d746000->0xffffff800d749fff


dependency: com.apple.driver.AppleUSBHostMergeProperties(1.2)[173405AF-478F-36CA-A81F-4B35867CB0C8]@0xffffff800e5ba000->0xffffff800e5bafff


dependency: com.apple.iokit.IOACPIFamily(1.4)[04DDFFBA-0499-3590-B6C5-C40851E28B4F]@0xffffff800dcb4000->0xffffff800dcb5fff


com.apple.driver.usb.AppleUSBOHCI(1.2)[90AC6B50-1DC1-3440-B8D0-11466325AAAE]@0xffffff800fc76000->0xffffff800fca7fff


dependency: com.apple.driver.usb.AppleUSBCommon(1.0)[62DBDC1B-3512-3B81-8627-3CFAC56298FE]@0xffffff800d746000->0xffffff800d749fff


dependency: com.apple.driver.usb.AppleUSBEHCI(1.2)[16CE5E0E-354E-30ED-AE54-4C614B0FBAB3]@0xffffff800e570000->0xffffff800e59cfff


dependency: com.apple.iokit.IOUSBHostFamily(1.2)[EBBE93B4-5667-3BC4-BC71-6C694409CFB6]@0xffffff800e4e0000->0xffffff800e558fff


com.apple.driver.usb.AppleUSBOHCIPCI(1.2)[04914014-B9B8-3A3C-8BBE-9A79B1F5A837]@0xffffff800fcb3000->0xffffff800fcc0fff


dependency: com.apple.driver.usb.AppleUSBCommon(1.0)[62DBDC1B-3512-3B81-8627-3CFAC56298FE]@0xffffff800d746000->0xffffff800d749fff


dependency: com.apple.driver.usb.AppleUSBEHCI(1.2)[16CE5E0E-354E-30ED-AE54-4C614B0FBAB3]@0xffffff800e570000->0xffffff800e59cfff


dependency: com.apple.driver.usb.AppleUSBOHCI(1.2)[90AC6B50-1DC1-3440-B8D0-11466325AAAE]@0xffffff800fc76000->0xffffff800fca7fff


dependency: com.apple.iokit.IOACPIFamily(1.4)[04DDFFBA-0499-3590-B6C5-C40851E28B4F]@0xffffff800dcb4000->0xffffff800dcb5fff


dependency: com.apple.iokit.IOPCIFamily(2.9)[58F0CC2D-E636-31B4-8532-BEF00812195A]@0xffffff800e121000->0xffffff800e152fff


dependency: com.apple.iokit.IOUSBHostFamily(1.2)[EBBE93B4-5667-3BC4-BC71-6C694409CFB6]@0xffffff800e4e0000->0xffffff800e558fff





Process name corresponding to current thread (0xffffff9a5b0040c8): kernel_task


Boot args: keepsyms=1 debug=0x100 -lilubetaall -btlfxallowanyaddr ipc_control_port_options=0 -nokcmismatchpanic -disable_sidecar_mac





Mac OS version:


Not yet set





Kernel version:


Darwin Kernel Version 23.1.0: Tue Oct 3 22:41:14 PDT 2023; root:xnu-10002.41.8~15/RELEASE_X86_64


Kernel UUID:


KernelCache base: 0xffffff800bc00000


Kernel slide: 0x000000000bae0000


Kernel text base: 0xffffff800bce0000


__HIB text base: 0xffffff800bb00000


System model name: MacBookPro5,2 (Mac-F2268EC8)


System shutdown begun: NO


Panic diags file unavailable, panic occurred prior to initialization


Hibernation exit count: 0





System uptime in nanoseconds: 3208670860


Last Sleep: absolute base_tsc base_nano


Uptime : 0x00000000bf407aa2


Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000


Wake : 0x0000000000000000 0x00000017bad2d491 0x0000000000000000


Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space


Zone info:


Zone map: 0xffffff80c149c000 - 0xffffffa0c149c000


. PGZ : 0xffffff80c149c000 - 0xffffff80c249d000


. VM : 0xffffff80c249d000 - 0xffffff858ef03000


. RO : 0xffffff858ef03000 - 0xffffff87287cf000


. GEN0 : 0xffffff87287cf000 - 0xffffff8bf5235000


. GEN1 : 0xffffff8bf5235000 - 0xffffff90c1c9b000


. GEN2 : 0xffffff90c1c9b000 - 0xffffff958e701000


. GEN3 : 0xffffff958e701000 - 0xffffff9a5b168000


. DATA : 0xffffff9a5b168000 - 0xffffffa0c149c000


Metadata: 0xffffff807fc8c000 - 0xffffff809fc8c000


Bitmaps : 0xffffff809fc8c000 - 0xffffff80a148c000


Extra : 0 - 0

[/spoiler}
 
Sonoma is running fine on OCLP, but I need to boot into safe mode to reset the login password. Each time I do so (by pressing shift+enter at the boot loader), the progress bar stops at halfway. Is there another way into safe mode?
 
deeveedee said:
I think this question is about 60% on-topic, 40% off-topic...

Apple has been sending occasional notices about their "Cloud-based XCode." I don't know enough about it and haven't used it yet, but it appears to me as though Apple Developers will have access to the latest XCode without the latest macOS. Does anyone have experience with Apple's Cloud-based XCode to know if it is a suitable replacement for XCode running in Sonoma?

If we have access to the latest XCode without needing the latest macOS, this could significantly influence macOS upgrade decisions (e.g., I might decide to stay on Monterey if I can still use the latest XCode).
Click to expand...
It’s not a full Xcode in the cloud, you don’t have the ide, the simulators.
It’s just CI integration for build pipelines and collaborative development
Not a replacement for Xcode
 
  • Like
Reactions: deeveedee and perez987
kurtster said:
Sonoma is running fine on OCLP, but I need to boot into safe mode to reset the login password. Each time I do so (by pressing shift+enter at the boot loader), the progress bar stops at halfway. Is there another way into safe mode?
Click to expand...
I don't think you "need to boot into safe mode to reset the login password".
System Settings - Users and Groups - click on the "i" next to your admin account,
should see a place where you can change the password
 
  • Like
Reactions: K two
Hello, I noticed the installation in the startup options of a line containing a person's name (mychaluk?).
Is this normal?
 
philk34 said:
Hello, I noticed the installation in the startup options of a line containing a person's name (mychaluk?).
Is this normal?
Click to expand...
Mykola Grymalyuk…? He’s the lead developer of OCLP; and here’s his very interesting blog, BTW:

Mykola’s blog

Blog dedicated to my rambles, including reverse engineering macOS internals, OS modding and documenting my cursed work.
khronokernel.github.io
 
  • Like
Reactions: Mockletoy and olad
philk34 said:
Hello, I noticed the installation in the startup options of a line containing a person's name (mychaluk?).
Is this normal?
Click to expand...

Some of us have been using OCLP long enough that this seems normal to us. Devs should probably change ownership of that startup process (and any messaging associated with the startup process) from Mykola to Open Core Legacy Patcher.
 
Last edited:
Upgraded the drive in my mid 2014 MacBook Pro no issues using the usb creator for Sonoma 14.1 and installing on the new drive .
 
@deeveedee thought you would like to see this, I got Ventura running in a VMWare Fusion 13 Pro VM on a late 2015 iMac with 3D acceleration working. Followed VMWare's instructions and added the two lines to the vmx file and here's the result! :)
Screen Shot 2023-10-12 at 10.46.06 AM.png
 
  • Like
Reactions: perez987, Rorg, rehkram and 2 others
MacinMan said:
@deeveedee thought you would like to see this, I got Ventura running in a VMWare Fusion 13 Pro VM on a late 2015 iMac with 3D acceleration working. Followed VMWare's instructions and added the two lines to the vmx file and here's the result! :)
Click to expand...
Nice! What's the Host macOS version running on your iMac?

EDIT: Forgive a naive question from one who doesn't run VMWare in macOS - is it reasonable to expect that someday, a Mac running Monterey as the Host OS will be able to run Sonoma in a VMWare VM?

EDIT2: and if so, would Sonoma be running 'natively' in the VM without OCLP patching?
 
Last edited:
deeveedee said:
Nice! What's the Host macOS version running on your iMac?

EDIT: Forgive a naive question from one who doesn't run VMWare in macOS - is it reasonable to expect that someday, a Mac running Monterey as the Host OS will be able to run Sonoma in a VMWare VM?

EDIT2: and if so, would Sonoma be running 'natively' in the VM without OCLP patching?
Click to expand...
I could try Sonoma, but right now this version of VMWare only officially supports up to Ventura, so it might work, but unofficially. Yes I'm running Monterey as the host. It's the last supported version for this iMac 17,1. I'm going to be testing this to see if a VM with the Apple GPU flag passed is more stable than OCLP. It is an apple supported way, so if nothing more you could run the current os alongside the last native supported OS this way as long as your OS is Big Sur, or later to support the 3D acceleration support. Also, you currently have to modify the ethernet adapter referenced in the vmx file as well or you will get a bootloop of kernel panics.

Here are the two links for instructions to get this working:

Enable 3D acceleration in MacOS 11 (Big Sur) virtual machines

kb.vmware.com kb.vmware.com

macOS Ventura VM looping in VMWare Fusion 13 (Intel) | Fusion

Hi,I am using VMWare Fusion 13 on an Intel Mac running macOS Ventura. I am able to install macOS Ventura as VM but after installation the VM keeps restarting. A
communities.vmware.com

I suggest you test it out, might give you more piece of mind doing it this way over OLCP since no wifi drivers have to be patched, or other security measures broken.

EDIT 1 changed my to you as that was a typo.
 
  • Like
Reactions: perez987 and deeveedee
rbart said:
Is it fast enough to be usable ?
Last time I have tried it was super slow
Click to expand...
Once I enabled the Apple GPU it got really fast. at least for a VM, you'd have to follow the instructions and judge for yourself. It also depends on your RAM. I have 32 GB installed because I had VMs in mind when buying this iMac. The other thing is, is judging by your comments in various posts, I may have a slightly more powerful variant of the iMac 17,1 than you. I think you have the 1 TB Fusion drive, and I have the 2, but it also has a slightly faster CPU, and GPU. It was the top tier you could buy off the shelf without going custom. From your descriptions of your it sounds like you have the entry level, and I tried that one first and found it too slow, so returned it and got this one.
If I'm incorrect about which model you have, I apologize, I'm just going by what you have said in the past, and what I remember about the different configurations for this iMac.
 
Last edited:
I will try.
So basically, On Monterey, you install Big Sur as guest in VM Fusion 13, you enable GPU acceleration and upgrade directly to Ventura ?
 
Last edited:
rbart said:
I will try.
SO basically, On Monterey, you install Big Sur as guest in VM Fusion 13, you enable GPU acceleration and upgrade directly to Ventura ?
Click to expand...
yes, but DON'T forget the network adapter change to the vmx file, or you'll end up with a boot loop. instructions in the links You can do what I did install big sur, upgrade, then shut down after the install is done and then make the changes.
EDIT 2, also install vmware tools before upgrading, it will help speed things up, you could try the GPU step for big sur, and you might have a nicer experience, but the ethernet adapter is a MUST for Ventura to run.
 
@MacinMan @rbart My preference would have been to run VMWare ESXi (Type 1 Hypervisor) to host macOS VMs. VMWare has discontinued support for ESXi on Intel Mac and has no plans for ESXi on Apple Silicon. I am using only Type 1 hypervisors (VMWare and Microsoft) and find them to yield virtually the same performance as running the OS on bare metal - very impressive. I would expect that performance in a Type 2 hypervisor (like Fusion) would suffer.

This is getting off-topic (even for me). Is there a MacRumors thread for discussing virtualization of macOS?
 
  • Like
Reactions: K two
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back