search

DrDonk / unlocker

VMware macOS utilities
MIT License
3.23k stars 450 forks source link

Keep rebooting on macOS Ventur #45

Closed remy727 closed 2 years ago

remy727 commented 2 years ago

I upgraded to macOS Ventura recently. After upgrading, I applied patches to VMware. But I am getting this error. Screenshot_1

DrDonk commented 2 years ago

It's a known problem with no fix currently.

DrDonk commented 2 years ago

Can you attach your VMX file and the vmware.log file to the issue, please?

nathanaelytj commented 2 years ago

Here is the VMX and LOG files. Some path is redacted from log file.

vmware.zip

DrDonk commented 2 years ago

I took a look but there is nothing obvious in the files, but I did not know that you were running on an AMD processor. It may well be Ventura has additonal sepecific requirements on the Intel CPUs it supports causing the boot loop. I think we are going to have to wait and see what the Hackintosh community come up with for Ryzen and AMD. It may then be possible to addd more CPUID changes, but at this stage there are no guarantees.

jeroencoolen commented 2 years ago

Replace ethernet0.virtualDev = "e1000e" with ethernet0.virtualDev = "vmxnet3" in vmx file. Boots perfectly.

DrDonk commented 2 years ago

It is already set to vmxnet3 so is something else.

DrDonk commented 2 years ago

I've added this page to explain how to capture debug output. https://github.com/DrDonk/unlocker/wiki/Debugging-macOS-Guests

You may want to try it and post the output.

AdrianEddy commented 2 years ago

I have the same issue, fresh installation of Ventura, here's the serial log: Ventura vmware workstation log.zip

DrDonk commented 2 years ago

@AdrianEddy Thanks for that could you run it again but leave the smcdebug=0xff parameter off the boot flags, please? I'm trying to distinguish between an SMC error or the library not being found.

Reason: tried: '/usr/lib/libSystem.B.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/usr/lib/libSystem.B.dylib' (no such file), '/usr/lib/libSystem.B.dylib' (no such file, no dyld cache)

Also is this a vanilla macOS installer, built from macOS download?

AdrianEddy commented 2 years ago

log.zip Yes, it's a fresh vanilla installation via bootable iso created from official macOS Ventura installer, downloaded on another mac from App Store and created using Install macOS Ventura.app/Contents/Resources/createinstallmedia. Installer ran successfully and installation went as expected. Installer rebooted a few times but then got stuck in the boot loop. Exactly the same happened after updating Monterey to Ventura via standard system update from previously working Monterey on VMware Workstation

DrDonk commented 2 years ago

Great thanks for helping out. I may need a bit of time to look through it. I assume Monterey ran fine on this host machine.

AdrianEddy commented 2 years ago

Yes, no issues with Monterey. Feel free to ask for any other logs or debugging, I'll be happy to help

DrDonk commented 2 years ago

@AdrianEddy Can we continue this https://github.com/DrDonk/unlocker/issues/33?notification_referrer_id=NT_kwDOAA1FpLEzODg4MTQ4MjY3Ojg2OTc5Ng&notifications_query=is%3Aunread#issuecomment-1307475635

Looks like same panic for multiple users.

DrDonk commented 2 years ago

Actually I have separated this into new issue:

https://github.com/DrDonk/unlocker/issues/47#issue-1440512657

EmilAlipiev commented 1 year ago

@DrDonk sorry asking you here. you replied me on the other thread "Create a Monterey VM attach the Ventura VM and copy data across." what do you exactly mean by that? I have created a Monterey VM but I cannot acces to Ventura VM, it gives me the error messages as on this issue. So is it not recoverable and i cannot get the data from the VM?

Mr-Smu commented 1 year ago

This helped me with Ventura on ESXi. Add to *.vmx file or via advanced settings.

hw.model.reflectHost = "FALSE" hw.model = "MacMini8,1" serialNumber.reflectHost = "FALSE" serialNumber = "000000000000"

Tested on NUC10i5 and MacMini7,1 with ESX 7U3g.