mirror of
https://github.com/DrDonk/unlocker.git
synced 2026-04-26 06:06:01 +03:00
[GH-ISSUE #33] Test using AMD Ryzen CPU #24
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/unlocker#24
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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 @DrDonk on GitHub (Jun 27, 2022).
Original GitHub issue: https://github.com/DrDonk/unlocker/issues/33
I recently tested the unlocker on my son's AMD Ryzen based laptop (thanks Dan), and looking for others to try it out using a vanilla macOS installation, not one with an AMD kernel or patches. The unlocker cannot patch this but we can recommend settings for the VMX file that allows macOS to run on recent AMD CPUs
The CPU spec was: AMD Ryzen 3 3200U with Radeon Vega Mobile Gfx @ 2.60 Ghz
It ran when the following lines were added to the VMX file:
UPDATE
You must have Hyper-V disabled on Windows or VMware falls back to a mode called ULM. CPUID masking is not available in ULM mode as it is pushed to Windows for the low level VMX/SVM operations. You can see if VMware is in ULM mode on Hyper_V by searching the guest's vmware.log file for these 2 lines:
vmx IOPL_Init: Hyper-V detected by CPUIDMonitor Mode: ULMHere is a link to a Microsoft artcile on disabling Hyper-V.
https://docs.microsoft.com/en-us/troubleshoot/windows-client/application-management/virtualization-apps-not-work-with-hyper-v
Editing the VMX file
be displayed by VMware.
So looking for others to try this out and report back here with any details on success or failure.
@nykiez commented on GitHub (Jun 29, 2022):
Result: SUCCESS
CPU spec: AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx 2.00 GHZ
Guest OS: macOS 12.4
STEPS:
@DrDonk commented on GitHub (Jun 29, 2022):
Good catch on the vhv and vpmc flags which would not work on AMD. So that means we cannot have nested virtualisation or virtual performance counters, but they are usually not enabled unless really needed.
@Avasam commented on GitHub (Jul 24, 2022):
AMD Ryzen 5 2600
Installing macOS 11
In previous installs on VMWare 15 with a different unlocker I had to add a bunch more settings.
All I had to do here was add the aforementioned CPU mask
I was also able to transfer my previous VM by copying over the vmx content (with cpu mask) of a new machine (and updating the name).
@DrDonk commented on GitHub (Jul 25, 2022):
Thanks for letting me know.
@morphine00 commented on GitHub (Aug 15, 2022):
Result: Fail
CPU: Ryzen 9 5900X
VMware version: 16.2.4; using unlocker 4.2.2
Host OS: Windows 11
Guest OS: macOS Monterey 13
The guest OS doesn't even get to show me the Apple logo. I get a "Failed to start the virtual machine." Tried with both the
vhvandvmpcflags set toTRUEorFALSE, no difference. I can post logs or thevmxfile, just let me know what you need.@DrDonk commented on GitHub (Aug 16, 2022):
Thanks for the post. Can you attach the vmx and vmware.log file to a post please? It's tricky to see what works and does not on AMD, but I will see if there is anything obvious.
@morphine00 commented on GitHub (Aug 16, 2022):
Here you go. For the record, if I don't have the
cpuid...lines in the VMX file, then the VM starts up, I get an Apple logo, but then it the CPU is halted.macOS 13 .vmx.txt
vmware.log
@DrDonk commented on GitHub (Aug 17, 2022):
I think it could be because you have Hyper-V enabled and VMware falls back to a mode called ULM. I believe CPUID masking is not available in that mode as it is pushed to Windows for the low level VMX/SVM operations.
Can you try disabling Hyper-V and trying again?
https://docs.microsoft.com/en-us/troubleshoot/windows-client/application-management/virtualization-apps-not-work-with-hyper-v
@morphine00 commented on GitHub (Aug 17, 2022):
I have success to report with the above configuration (macOS Monterey, VMWare 16.x, Windows 11, Ryzen 9 5900X), finally
The road to getting there was not easy, though. It was very difficult to completely disable Hyper-V in Windows 11. Here are the steps I took, and to be completely honest, I don't know which combination worked. The last thing I did was
bcdedit /set hypervisorlaunchtype offbut I don't know that was enough or if the other steps were required.To check whether Hyper-V is truly disabled, run
msinfo32and the very last line should NOT read "A hypervisor has been detected..." You should instead see 4 lines of information about Hyper-V features -- yes, that's misleading, but that's what you should see..Windows Features ->
Disable Hyper-V
Disable Windows Hypervisor Platform
Disable WSL
Set Credential Guard Off: from info in Microsoft's website, find the HCVI Readiness Tool, save it to disk, and run
DG_Readiness_Tool.ps1 -Disable -AutoRebootSettings -> Core Isolation -> Memory Integrity is Off
Open an elevated Command Prompt,
bcdedit /set hypervisorlaunchtype off@DrDonk commented on GitHub (Aug 17, 2022):
Good news. I know switching off Hyper-V can be a problem.
I will update the issue and the readme file.
Thanks for the testing and the feedback.
@morphine00 commented on GitHub (Aug 17, 2022):
No problem. If you need me to do further testing, I can.
On Wed, Aug 17, 2022, 21:20 David Parsons @.***> wrote:
@DrDonk commented on GitHub (Aug 18, 2022):
@morphine00 Could you send me a vmare.log file from the workign guest please? I'm just checking on what CPUID masks are actually doing at runtime and it's logged in vmware.log.
Thanks
@morphine00 commented on GitHub (Aug 18, 2022):
There you go.
vmware.log
@DrDonk commented on GitHub (Aug 18, 2022):
Thanks
@morphine00 commented on GitHub (Aug 18, 2022):
For the record, the VMWare Tools also installed just fine via the standard VMWare menus. Don't know if that was relevant to this issue or not.
@DrDonk commented on GitHub (Aug 18, 2022):
AFAIK The tools should work just fine for Intel and AMD, but good to have it confirmed again.
@balix18 commented on GitHub (Aug 20, 2022):
Result: Success
CPU: Ryzen 9 5800X
VMware Player version: 16.2.4; using unlocker 4.2.2
Host OS: Windows 10 (21H2)
Guest OS: macOS Monterey 12.5.1
At first I was also getting "Failed to start the virtual machine." error, like @morphine00 did, then I disabled hyperv via:
Open an elevated Command Prompt,
bcdedit /set hypervisorlaunchtype offWindows Features ->
Disable Hyper-V
Disable Windows Hypervisor Platform
Disable WSL
@Codling commented on GitHub (Aug 22, 2022):
Result: Fail
CPU: Ryzen 9 5950X
VMware version: 16.2.4; using Unlocker 4.2.2
Host OS: Windows 11 22H2
Guest OS: macOS Ventura 13.0 Beta 5
Monterey works like a charm, I don't understand what's wrong with Ventura.
Hyper-V is disabled, but it doesn't fix the bootloop. :/
macOS.vmx.txt
vmware.log
@morphine00 commented on GitHub (Aug 22, 2022):
You have
vhv.enable = "TRUE", you sure this should be on?@Codling commented on GitHub (Aug 22, 2022):
I tried with
vhv.enable = "FALSE", but it doesn't work either.@DrDonk commented on GitHub (Aug 22, 2022):
Currently not supported by VMware. There is one possible change as there have been reports of network adapter issues.
Edit VMX file and change
ethernet0.virtualDev = "e1000e"
to
ethernet0.virtualDev = "vmxnet3"
@Codling commented on GitHub (Aug 22, 2022):
Unfortunately, I also tried this one, with no luck.
@DrDonk commented on GitHub (Aug 22, 2022):
Ventura is hard resetting the CPU. No way I can see to sort that out. There are issues on Fusion as well.
New version of Fusion and Workstation on the way which may support Ventura but be aware VMware are dropping support for future macOS versions.
@DrDonk commented on GitHub (Aug 23, 2022):
@Codling I think that VMware is masking out the AVX2 capability flag in the guest, and that is a new hard requirement of Ventura. I may be able to change the cpuid masks to force AVX2. However some bits cannot be passed thru and I'm going to have to check that out.
@Codling commented on GitHub (Aug 25, 2022):
Thank you, @DrDonk! Can't wait to test this out. :)
@DrDonk commented on GitHub (Aug 27, 2022):
@Codling I'm struggling with this and not sure if I have it figured out. Can you try Monterey out on your machine?
If you can please set the guest to output debug log using the steps from:
https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-A438B4FE-8499-454C-BBDE-9299FCDFB455.html
That gives a complete cpuid dump and differences report. You could also do that on the Ventura guest as well.
I am going to be offline for 3 days so there's no rush, and don't worry if you are not able to do this. It may be worth waiting until Ventura and the next version of VMware products ships.
@bodeg commented on GitHub (Sep 2, 2022):
CPU: AMD Ryzen 9 4900H with Radeon
VMware version: 16.2.3
Unlocker 4.2.2
Host OS: Windows 10 Pro
Guest OS: macOS Ventura 13.0 Beta 3
Result: Fail
boot loop - also fail with VirtualBox.
Guest OS: macOS Monterey 12.0.1
Result: Success
@DrDonk commented on GitHub (Sep 3, 2022):
Thanks for the feedback. At this point I don't see a way of getting Ventura running. Looks like it needs something changing in the VMware core. Newer versions of products coming but as you may ahve seen VMware said wouldn't support future macOS versions. That may change but we will have to start getting used to the fact that Intel Mac is going and the journey is ccoming to an end.
@JamisonMurphy commented on GitHub (Oct 9, 2022):
The VM reboot when i try to use xcode's simulator. My CPU is amd R7 5800h (legion r9000p).
this is error log and vmx file:
vmx.txt
error-mac.txt
@DrDonk commented on GitHub (Oct 9, 2022):
That is an invalid opcode panic and there is nothing I can do in VMware and the unlocker to fix this. Looks like there is code being called with Intel only opcode embedded in the executable, possibly in CoreCrypto. Best suggestion is to ask what to do in a forum that supports AMD Hackintoshes.
I will add note that Xcode Simulator does not work.
@DrDonk commented on GitHub (Oct 12, 2022):
@chengzi-niude I wonder if this is related to https://forums.macrumors.com/threads/monterand-probably-the-start-of-an-ongoing-saga.2320479/page-4?post=31125212#post-31125212
@JamisonMurphy commented on GitHub (Oct 13, 2022):
thank you,i will try it
@z16166 commented on GitHub (Nov 3, 2022):
It's working! thanks!
AMD 3700X + Nvidia 2060S, unlocker 4.2.3, vmware workstation 16.2.4 for windows, Big Sur and Monterey.
@DrDonk commented on GitHub (Nov 6, 2022):
I am getting reports of issues with Ventura on AMD CPUs. Has anyone tested this and if so can you report whether it works or not?
@z16166 commented on GitHub (Nov 8, 2022):
A few minutes ago, I tested Ventura 13.0 (22A380) with my settings(AMD 3700X + Nvidia 2060S, unlocker 4.2.3, vmware workstation 16.2.4 for windows), it can't boot, error message is "Your computer restarted because a problem. Press any key or wait a few seconds to continue starting up".
full debug log attached.
There is a panic for SMC.
2022-11-08T06:20:50.689Z Wa(03) vmx smc: Index 432: Inconsistent read information.
2022-11-08T06:20:50.689Z Cr(01) vmx PANIC: ASSERT bora\devices\misc\appleSMC.c:599
2022-11-08T06:20:50.689Z In(05) vmx MKSGrab: MKS release: start, unlocked, nesting 0
2022-11-08T06:20:50.689Z In(05) vmx CoreDump_CoreDump: faking exception to get context
vmware.zip
@DrDonk commented on GitHub (Nov 8, 2022):
@z16166
Interesting. I think there are multiple issues happening with Ventura.
ethernet0.virtualDev = "e1000e"to
ethernet0.virtualDev = "vmxnet3"I am going to write a note on how to capture macOS debug output via virtual serial port. May find something of use in that log.
So can you do 2 tests for me please? Do each one separately so can test each setting.
ethernet0.virtualDev = "e1000e"to
ethernet0.virtualDev = "vmxnet3"smc.version = "0"@DrDonk commented on GitHub (Nov 8, 2022):
Here's the notes on capturing debug info.
https://github.com/DrDonk/unlocker/wiki/Debugging-macOS-Guests
@z16166 commented on GitHub (Nov 8, 2022):
Pity that I can't set vmx.buildType to "debug", because vmware will always core-dumped before booting to firmware.
So I changed vmx.buildType to "stats". Here are logs for above 2 conditions.
smc.version.0.zip
vmxnet3.zip
@DrDonk commented on GitHub (Nov 8, 2022):
Thanks to several people helping out and the cause seems to be a missing dyld cache for the processor being used:
Not sure where we go from here, and I suspect this will also affect older Interl CPUs.
@DrDonk commented on GitHub (Nov 8, 2022):
I am going to track this in a separate issue https://github.com/DrDonk/unlocker/issues/47#issue-1440512657
@jerrywoo96 commented on GitHub (Nov 19, 2022):
I'm using a Ryzen 9 5950X
I have tested this long ago testing various configurations and reading through the vmware logs and cpuid wikipedia.
Since i need to use WSL, disabling the hypervisor is not an option for me.
So i started testing various vmx configurations.
Here's my findings.
To Add:
To Add if missing or Replace if not 16:
virtualHW.version = "16"cpuid.0.eax and cpuid.1.ebx is not needed.
I've also upgraded the cpu model from 55 (Bay Trail) to 58 (Ivy Bridge). Any models higher than Ivy Bridge (>58) is not working.
This is working for monterey and big sur, and if i remember correctly, with hypervisor enabled the last time i used it.
Not working on Ventura, constant reboots.
Currently my hypervisor is not working now as my hypervisor network adapters is bugged.
Do test if running this with hypervisor on is still working or not, as i'm unable to test now.
@tristan-k commented on GitHub (Nov 20, 2022):
@jerrywoo96 I tried your settings but if I try to select the VM in VMware I'll get an error saying
Error while opening the virtual machine: Internal error.These are my settings.@jerrywoo96 commented on GitHub (Nov 20, 2022):
This line is missing
virtualHW.version = "16"@tristan-k commented on GitHub (Nov 20, 2022):
Thanks. Now it's booting fine. The VM is very slow and sluggish. I'm running this on a Ryzen 6800U.
@jerrywoo96 commented on GitHub (Nov 20, 2022):
you can fix it by installing the VMware Tools.
Also are you running windows with hypervisor enabled?
@tristan-k commented on GitHub (Nov 21, 2022):
I already installed the VMware Tools but performance did not increase significantly. Yes, I need to use WSL as well. So Hypervisor is enabled.
@morphine00 commented on GitHub (Nov 21, 2022):
@jerrywoo96 thanks so much for your investigation. Now I can use macOS without having to disable the hypervisor and rebooting the machine. Performance is fairly slow but it's good enough for casual testing. Thanks!
@hamsandvich commented on GitHub (Nov 22, 2022):
CPU: Ryzen 9 5950X
VMware Player version: 16.2.4; using unlocker 4.2.2
Host OS: Windows 11 (22H2)
Guest OS: macOS BigSur(11.6)
"Failed to start the virtual machine." error, like @morphine00 and did, then I disabled hyperv via:
But im still not able to get passed Failed to start the virtual machine.
It will only give that error if i have this in the VMX
cpuid.0.eax = "0000:0000:0000:0000:0000:0000:0000:1011"
cpuid.0.ebx = "0111:0101:0110:1110:0110:0101:0100:0111"
cpuid.0.ecx = "0110:1100:0110:0101:0111:0100:0110:1110"
cpuid.0.edx = "0100:1001:0110:0101:0110:1110:0110:1001"
cpuid.1.eax = "0000:0000:0000:0001:0000:0110:0111:0001"
cpuid.1.ebx = "0000:0010:0000:0001:0000:1000:0000:0000"
cpuid.1.ecx = "1000:0010:1001:1000:0010:0010:0000:0011"
cpuid.1.edx = "0000:0111:1000:1011:1111:1011:1111:1111"
If i remove the masking it gives me the Guest os disable the CPU
if anyone has ideas that would be helpful 🙇♂️
vmware.log
macOS 11.1.txt
@jerrywoo96 commented on GitHub (Nov 23, 2022):
remove all your current cpuids, add this.
change
virtualHW.version = "18"tovirtualHW.version = "16"@DrDonk commented on GitHub (Nov 23, 2022):
@hamsandvich You are still using Hyper-V as the the vmware.log shows that ULM is still being used. Please disable Hyper-V, it is the only consistent way to make his work.
(See https://github.com/DrDonk/unlocker/blob/main/TROUBLESHOOTING.md)
The current best settings for AMD are:
@DrDonk commented on GitHub (Nov 25, 2022):
@jerrywoo96 Thanks for the CPUID masks. I'll add the as alternatives to what I have already listed. Just FYI if you continue with Hyper-V enabled it will be slower than using VMware hypervisor and a limited set CPUID bits can be set. For example CPU vendor is not overwritten in the guest.
I'm now going to shut this issue.