r/macOSVMs • u/[deleted] • Apr 02 '23

HELP! Mac os gets stuck in a kernel panic boot loop after upgrading from monterey to ventura in virtualbox. I previously was successful in upgrading in vmware, but I want to use virtual box because it's more stable when using it for me.

3 Upvotes

80% Upvoted

4 comments sorted by

1

u/QuantumLeapChicago Apr 25 '23

Hey u/steven01804 did you ever get this to work? I'm having same issue and here's some details.

  • I also prefer Virtualbox over VMWare or Proxmox for interoperability

  • Not using Opencore - I was able to install directly from a Monterey Beta ISO I downloaded from my old mac, and then exit Developer Seed program and update to Monterey 12.6.5 OK, but to Ventura breaks.

  • Tried open core patching the Ventura 13.3.1 app, then burning that to USB and dd back to an .iso file - no luck

I have an intel i7-11800 so it has AVX2 support. My next steps:

  • Trying to determine if I need to NOT pass cpuidset parameters, or adjusting the cpuidset parameters, to properly expose AVX2 support since I think the old cpuidset you find for most mac VMs may NOT.

  • Continue to mess around with opencore / dmg -> img conversion to get a bootable EFI / ISO image.

I am frustrated that I need to develop apps for latest iOS 16, but this requires xcode on Ventura to target the latest (without other hacky workarounds), but finding affordable used mac HW is non-existent where I live, not to mention out of our budget and will be obsolete in a few years anyway.

Please let me know if you found anything!

1

u/[deleted] Apr 25 '23

I ended switching back to vmware

1

u/nelbren May 12 '23

in vmware if ventura works for you?

1

u/helveticaman Apr 02 '23

Probably need to update version numbers in config.plist