macOS Ventura 13 bootloop (Library not loaded: /usr/lib/libSystem.B.dylib)

[Soberia]

Windows 11 (Build 25227)
VMware Workstation Pro 16.2.4 (Build 20089737)

2022-10-29T00:41:19.897Z Wa(03) vcpu-0 DarwinPanic: panic(cpu 0 caller 0xffffff802870a796):  initproc failed to start -- exit reason namespace 6 subcode 0x1 description: Library not loaded: /usr/lib/libSystem.B.dylib
2022-10-29T00:41:19.918Z In(05) vcpu-0 Chipset: The guest has requested that the virtual machine be hard reset.

[vakibear]

I hope it is normal soon…

[DrDonk]

Just a quick post about what is known about this. If you have a pre-Kaby Lake CPU then there is no way to patch a fix into VMware as Apple dropped support for older CPUs.

The issue is missing AVX 2.0 instructions on those CPUs. dortania/OpenCore-Legacy-Patcher#998

[jfauss]

Exactly the same error reported by Soberia but on vcpu-3
2023-02-24T17:16:40.156Z Wa(03) vcpu-3 DarwinPanic: panic(cpu 3 caller 0xffffff800d10a046): initproc failed to start -- exit reason namespace 6 subcode 0x1 description: Library not loaded: /usr/lib/libSystem.B.dylib
Tested with vmware workstation pro 16.2.2 and 17.0.1 with unlock 4.2.5 and AMD Ryzen 7 5700G and Ventura 13.2.1
I saw "macOS Ventura Testing #47" done by DrDonk on github.
Finding no solution for this problem with AMD new processor supporting AVX2.
All old macos like Monterey, BigSur, Catalina, Mojave, HighSierra, Sierra are running well with 17.0.1/16.2.2 with unlock 4.2.5 or 3.0 with this AMD having in .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"
smc.version = "0"
ethernet0.virtualDev = "vmxnet3"
hw.model = "iMac20,2"
board-id = "Mac-AF89B6D9451A490B"
board-id.reflectHost = "TRUE"

[jfauss]

Evenif creating a new vm with a Ventura 13.2.1 iso or upgrading a Monterey vm. Same infinite loop with

[moekhalil]

Same issue here.

VMware® Workstation 17 Pro | 17.0.1 build-21139696
AMD 3900X | Windows 11

Tried Ventura 13.1 and 13.2 with three different methods:

1. New machine, clean install with stock ISOs. Install goes well. Reboot. | RESULT: Infinite loop.
2. Export a working 13.1 VM on from Parallels macOS. convert to VMDK and importing | RESULT: Infinite loop.
3. Export a working 13.1 VMWare Workstation from a Windows Intel machine, | RESULT: Infinite loop.

vmware-0.log reports:

 Wa(03) vcpu-1 DarwinPanic: panic(cpu* 1):  initproc failed to start -- exit
               reason:  namespace 6 subcode 0x1 
               description: Library not loaded: /usr/lib/libSystem.B.dylib
 In(05) vcpu-1 Chipset: The guest has requested that the virtual machine be hard reset.
 In(05) vcpu-0 DEVICE: Resetting device 'ALL'.

*Same error shows up with various cpu's. Cpu 0, 1, 2, 3.

[m4heshd]

This absolutely sucks. Such a painful way to give up.

[dpa99c]

I'm encountering this issue after updating a macOS VM from 12.6.4 to 13.3.1:

2023-04-17T07:15:22.342Z Wa(03) vcpu-0 DarwinPanic: panic(cpu 0 caller 0xffffff8006d283fe):  initproc failed to start -- exit reason namespace 6 subcode 0x1 description: Library not loaded: /usr/lib/libSystem.B.dylib
2023-04-17T07:15:22.346Z In(05) vcpu-0 CPU reset: soft (mode HV)
2023-04-17T07:15:22.346Z In(05) vcpu-1 CPU reset: soft (mode HV)
2023-04-17T07:15:22.346Z In(05) vcpu-2 CPU reset: soft (mode HV)
2023-04-17T07:15:22.346Z In(05) vcpu-3 CPU reset: soft (mode HV)

However my CPU is a modern Intel i5-11600KF (11th Gen "Rocket Lake")

OSX 12.6.4 (and previous versions) worked fine on this machine.

Windows 10
VMware Workstation 17 Pro v17.0.0
Unlocker v4.2.6

vmx: OSX.vmx.txt

Any ideas?

[teknixstuff]

Same issue after upgrading from Monterey to Ventura.

2023-04-20T09:29:23.545Z Wa(03) vcpu-1 DarwinPanic: panic(cpu 1 caller 0xffffff80067283fe):  initproc failed to start -- exit reason namespace 6 subcode 0x1 description: Library not loaded: /usr/lib/libSystem.B.dylib
2023-04-20T09:29:23.548Z In(05) vcpu-1 Chipset: The guest has requested that the virtual machine be hard reset.

VMware Workstation 17 Pro v17.0.1 build-21139696 (Tried both normal and KVM mode, planning to use KVM mode once all is working.)
Windows 10 LTSC Enterprise 1809

CPU

AMD Ryzen 9 5900HX with Radeon Graphics 

Base speed:	3.29 GHz
Sockets:	1
Cores:	8
Logical processors:	16
Virtualisation:	Enabled
L1 cache:	512 KB
L2 cache:	4.0 MB
L3 cache:	16.0 MB

Utilisation	11%
Speed	3.16 GHz
Up time	0:03:10:20
Processes	200
Threads	2700
Handles	78192

GPU 0

AMD Radeon(TM) Graphics

Driver version:	31.0.14037.1007
Driver date:	Sun, 5 Mar 2023
DirectX version:	12 (FL 12.1)
Physical location:	PCI bus 5, device 0, function 0

Utilisation	1%
Dedicated GPU memory	258/512 MB
Shared GPU memory	0.1/7.7 GB
GPU Memory	0.4/8.2 GB

GPU 1 (nVidia) missing on host, IDK when that started.

[teknixstuff]

Might the CPUID in the .vmx be specifying that AVX2 isn't available or something?

[teknixstuff]

If so, a different CPUID should make it work. Unfortunatly, IDK what CPUID might work.

[teknixstuff]

Maybe OpenCore Legacy Patcher would fix it, but IDK how to install OCLP on VMWare, or if that's even a good idea at all.

[dpa99c]

I'm encountering this issue after updating a macOS VM from 12.6.4 to 13.3.1:

2023-04-17T07:15:22.342Z Wa(03) vcpu-0 DarwinPanic: panic(cpu 0 caller 0xffffff8006d283fe):  initproc failed to start -- exit reason namespace 6 subcode 0x1 description: Library not loaded: /usr/lib/libSystem.B.dylib
2023-04-17T07:15:22.346Z In(05) vcpu-0 CPU reset: soft (mode HV)
2023-04-17T07:15:22.346Z In(05) vcpu-1 CPU reset: soft (mode HV)
2023-04-17T07:15:22.346Z In(05) vcpu-2 CPU reset: soft (mode HV)
2023-04-17T07:15:22.346Z In(05) vcpu-3 CPU reset: soft (mode HV)

However my CPU is a modern Intel i5-11600KF (11th Gen "Rocket Lake")

OSX 12.6.4 (and previous versions) worked fine on this machine.

Windows 10 VMware Workstation 17 Pro v17.0.0 Unlocker v4.2.6

vmx: OSX.vmx.txt

Any ideas?

I was able to get a macOS Ventura 13.3.1 VM working by creating a new VM:

• Used mist-cli on VM running macOS 12.6.4 to download and create a 13.3.1 ISO
• Created new VM using it in VMWare Workstation

However as mentioned above, I'm using an Intel CPU so this may not work for those with AMD.

[EngMarc]

I've been working for about 7-10 days trying to get OpenCore 1.01 to install Ventura on an imac 21.5" from around 2011 (A1311 as far as I can tell). It's pretty stock CPU and upgraded RAM and SSD. The install runs fairly well but it repeatedly goes into a bootloop with the hazard circle-line symbol. Going back and to pick the OpenCore, seems to repeat everything over again and again (like 4-5 times). I'm not sure if this is a bug in OpenCore or the variation on this model of iMac?

I've

1. cleared NVRAM, repeated install
2. bless on the EFI
3. format the HD in APFS and started over
4. held down command-option-R to try to recover - only get spinning globe
5. last time did startup and it seems to boot but still seems unpredictable

I did the installs on a macmini 7,1 and MacBookPro 13,3 with OpenCore v6 without any problems at all! So not sure it isn't the v1.0.1 OpenCore or the iMac?

[moekhalil]

@EngMarc

I've been working for about 7-10 days trying to get OpenCore 1.01 to install Ventura on an imac 21.5" from around 2011 (A1311 as far as I can tell). It's pretty stock CPU and upgraded RAM and SSD. The install runs fairly well but it repeatedly goes into a bootloop with the hazard circle-line symbol. Going back and to pick the OpenCore, seems to repeat everything over again and again (like 4-5 times). I'm not sure if this is a bug in OpenCore or the variation on this model of iMac?

I've

1. cleared NVRAM, repeated install
2. bless on the EFI
3. format the HD in APFS and started over
4. held down command-option-R to try to recover - only get spinning globe
5. last time did startup and it seems to boot but still seems unpredictable

I did the installs on a macmini 7,1 and MacBookPro 13,3 with OpenCore v6 without any problems at all! So not sure it isn't the v1.0.1 OpenCore or the iMac?

This thread/issue is opened in regard to "auto-unlocker", a project relating to unlocking VMWare to allow one to install MacOS on a VMWare virtual machine (no relation or requirement to Opencore).

You seem to be using bare metal/hardware, not VMWare and not paolo's auto-unlocker.
This is not the right project. OpenCore is a separate project, you can try you issue on an OpenCore discussions forum.

sidenote: It seems you are using Mac hardware, so you should be using OpenCore Legacy Patcher not just standalone OpenCore.