[GH-ISSUE #37] vmware workstaton pro 16.2.3 macOS Ventura beta and it's stuck in a reboot loop ! #26

Closed
opened 2026-03-02 03:57:48 +03:00 by kerem · 11 comments
Owner

Originally created by @ybrc on GitHub (Jul 9, 2022).
Original GitHub issue: https://github.com/DrDonk/unlocker/issues/37

vmware.log
[Please attach as a file and not paste into the issue. Thanks.]

Originally created by @ybrc on GitHub (Jul 9, 2022). Original GitHub issue: https://github.com/DrDonk/unlocker/issues/37 [vmware.log](https://github.com/DrDonk/unlocker/files/9161173/vmware.log) [Please attach as a file and not paste into the issue. Thanks.]
kerem closed this issue 2026-03-02 03:57:48 +03:00
Author
Owner

@DrDonk commented on GitHub (Jul 9, 2022):

This is not something the unlocker can fix. Please check this out https://github.com/DrDonk/unlocker/issues/22#issuecomment-1152192394.

If that does not help it would require something from VMware.

<!-- gh-comment-id:1179581129 --> @DrDonk commented on GitHub (Jul 9, 2022): This is not something the unlocker can fix. Please check this out https://github.com/DrDonk/unlocker/issues/22#issuecomment-1152192394. If that does not help it would require something from VMware.
Author
Owner

@DrDonk commented on GitHub (Jul 10, 2022):

I have just read this https://communities.vmware.com/t5/VMware-Fusion-Discussions/macOS-13-Ventura-VM-Intel/m-p/2918070#M179012.

Potentially this means that Ventura will never be useable on anything other than macOS and Fusion. It look like the Apple Paravirtualized GPU is required and that is only available on a macOS host.

<!-- gh-comment-id:1179739191 --> @DrDonk commented on GitHub (Jul 10, 2022): I have just read this https://communities.vmware.com/t5/VMware-Fusion-Discussions/macOS-13-Ventura-VM-Intel/m-p/2918070#M179012. Potentially this means that Ventura will never be useable on anything other than macOS and Fusion. It look like the Apple Paravirtualized GPU is required and that is only available on a macOS host.
Author
Owner

@DrDonk commented on GitHub (Jul 10, 2022):

@ybrc Can you attach the vmware.log and the VMX file to this issue please

<!-- gh-comment-id:1179739410 --> @DrDonk commented on GitHub (Jul 10, 2022): @ybrc Can you attach the vmware.log and the VMX file to this issue please
Author
Owner

@DrDonk commented on GitHub (Jul 21, 2022):

Nothing in the log shows the error, and I suspect it is something VMware have to fix as also seems to be problems with Fusion on Apple hardware.

There is a new VMware tech preview dropping sometime soon. I will have another look at Ventura once that is available.

<!-- gh-comment-id:1191712935 --> @DrDonk commented on GitHub (Jul 21, 2022): Nothing in the log shows the error, and I suspect it is something VMware have to fix as also seems to be problems with Fusion on Apple hardware. There is a new VMware tech preview dropping sometime soon. I will have another look at Ventura once that is available.
Author
Owner

@DrDonk commented on GitHub (Jul 30, 2022):

VMware have released a new 22H2 Tech preview of Workstation. Can you try that with v4.2.2 of the unlocker please?

<!-- gh-comment-id:1200275646 --> @DrDonk commented on GitHub (Jul 30, 2022): VMware have released a new 22H2 Tech preview of Workstation. Can you try that with v4.2.2 of the unlocker please?
Author
Owner

@ybrc commented on GitHub (Aug 3, 2022):

VMware have released a new 22H2 Tech preview of Workstation. Can you try that with v4.2.2 of the unlocker please?

VMware® Workstation Technology Preview 22H2 Pro e.x.p build-20200310
Unlockerv4.2.2
Tested on macOS Monterey and everything is fine. Next, I decided to test macOS Ventura. Is there anything else I need to provide?

<!-- gh-comment-id:1203891215 --> @ybrc commented on GitHub (Aug 3, 2022): > VMware have released a new 22H2 Tech preview of Workstation. Can you try that with v4.2.2 of the unlocker please? VMware® Workstation Technology Preview 22H2 Pro e.x.p build-20200310 Unlockerv4.2.2 Tested on macOS Monterey and everything is fine. Next, I decided to test macOS Ventura. Is there anything else I need to provide?
Author
Owner

@DrDonk commented on GitHub (Aug 3, 2022):

Did the TP not work with Ventura?

<!-- gh-comment-id:1203911793 --> @DrDonk commented on GitHub (Aug 3, 2022): Did the TP not work with Ventura?
Author
Owner

@ghost commented on GitHub (Aug 3, 2022):

If Ventura requires Apple Paravirtualized GPU, maybe we build an emulator with GPU acceleration? I know it's hard, it's just in my dream, because I once discovered chinese iOS emulator called Heilei that support GPU acceleration

<!-- gh-comment-id:1204040322 --> @ghost commented on GitHub (Aug 3, 2022): If Ventura requires Apple Paravirtualized GPU, maybe we build an emulator with GPU acceleration? I know it's hard, it's just in my dream, because I once discovered chinese iOS emulator called Heilei that support GPU acceleration
Author
Owner

@DrDonk commented on GitHub (Aug 3, 2022):

The is nowhere to create a hook in Workstation for AppleGPU and the settings are missing from the code. The code also requires System Libraries from Apple and I cannot see anyway to emulate that.

It would be nice to have accelerated graphics but to be honest it is a bit hit and miss that it works in macOS guests running in Fusion.

<!-- gh-comment-id:1204089449 --> @DrDonk commented on GitHub (Aug 3, 2022): The is nowhere to create a hook in Workstation for AppleGPU and the settings are missing from the code. The code also requires System Libraries from Apple and I cannot see anyway to emulate that. It would be nice to have accelerated graphics but to be honest it is a bit hit and miss that it works in macOS guests running in Fusion.
Author
Owner

@DrDonk commented on GitHub (Aug 4, 2022):

OK I completely missed the reason I think your VM does not work. It's the virtual network adapter which need to be vmxnet3 and not e1000e, not the AppleGPU.

Attached is a modified VMX file I created from the vmware.log file. Try that by copying to the VM folder.
macOS 13.vmx.txt

(You will need to remove the .txt off the end and make sure it's called "macOS 13.vmx")

<!-- gh-comment-id:1205335390 --> @DrDonk commented on GitHub (Aug 4, 2022): OK I completely missed the reason I think your VM does not work. It's the virtual network adapter which need to be vmxnet3 and not e1000e, not the AppleGPU. Attached is a modified VMX file I created from the vmware.log file. Try that by copying to the VM folder. [macOS 13.vmx.txt](https://github.com/DrDonk/unlocker/files/9260564/macOS.13.vmx.txt) (You will need to remove the .txt off the end and make sure it's called "macOS 13.vmx")
Author
Owner

@DrDonk commented on GitHub (Aug 18, 2022):

No updates so closing!

<!-- gh-comment-id:1219360601 --> @DrDonk commented on GitHub (Aug 18, 2022): No updates so closing!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/unlocker#26
No description provided.