Will it work on a AMD chip ?

[RajdeepVerma]

Will it work on a AMD chip ?
I have Ryzen 5 4600H, i have seen macos running tricking hardly work with AMD cpu ?

[Qonfused]

Yes, this works on AMD CPUs as well. You'll want to check out #5 and use the AMD kernel patch linked in the post. It's explained in the Dortania guide as well -- you'll want to follow the same process for patching AMD CPUs.

[RajdeepVerma]

Thank you so much for your quick response.

[Ryan-kopp]

I am trying to get this to run on Server 2025 with Hyper-V on an AMD Ryzen CPU. I am a little confused on Step 5 and how to modify the config.Plist and add the patches.plist

[Qonfused]

The OpenCore log contains EDK2 mneumonics which are in general hard to decipher, but in this case the relevant line is this one:

105:573 00:579 AAPL: #[EB.MM.AKM|!] Err(0xE) <- EB.MM.MKP

You're facing the same error as #44 where too little memory is allocated to the VM. Any macOS version since Big Sur in my experience will require at least 6-8 GB of memory (at least for the installer).

I did also notice that two kernel patches aren't being applied, though the patches themselves look correct.

04:905 102:768 OC: Kernel patcher result 9 for kernel (algrey | _cpuid_set_generic_info | Remove wrmsr(0x8B) | 10.13+) - Not Found
104:993 00:088 OC: Kernel patcher result 10 for kernel (algrey | _cpuid_set_generic_info | Replace rdmsr(0x8B) with constant 186 | 10.13+) - Not Found

For now I'd retry with a higher amount of RAM and try to get a screenshot/video of where it gets stuck (assuming it gets further into the installer).

[Ryan-kopp]

Thanks @Qonfused, I meant to bump up the VM memory to 8GB but forgot to go back on update it. I updated it and as you said it got further in the boot process. Attached is new log file and screen shot where it gets stuck. It seems to hang there should it continue and exit out into a reboot?

opencore-2025-06-11-063317.txt

[Qonfused]

It should continue after that point.

The #[EB|LOG:EXITBS:START] line means OpenCore has finally handed off to the installer (so subsequent logs on screen will be from the macOS/installer boot.efi). It's also worth pointing out that anything further won't be displayed in the log file (since we're no longer in OpenCore), though you can record/screenshot any points afterwards.

I'm mainly worried about these two lines, which seems to indicate some kind of error with runtime relocation of firmware code/data lines during the boot transition (from OpenCore into the installer).

#[EB.RH.LRH|P!] Err(0x3) <- EB.LD.LR
#[EB.BST.FBS|!] Err(0x3) <- EB.RH.LRH

The main thing that comes to mind is secure boot (double check this is disabled in VM settings), though it could still be caused from the two MSR patches failing to apply. In any case, what is causing this is not entirely clear.

Assuming you've applied the debugging config.plist settings from #11 (reply in thread), do you get anything further (not present in the OpenCore log) or does it immediately reboot/hang?

[Ryan-kopp]

[Ryan-kopp]

It just hangs at that screen, is there anything missing from here?