If your host computer is getting errors and stuck on the logo during installation, we recommend that you configure the virtual processor core count to an appropriate 1 and test it. Under normal conditions, a macOS virtual computer runs smoothly with a memory size of 4096 (4 GB).Īlso, set the number of 2 or 4 vCPUs for the macOS system to work more efficiently on the virtual computer. If your host RAM has a capacity of 16 GB, assign a RAM size of 4 GB or 8 GB in the Memory Size window. You should allocate RAM size and virtual processor to the virtual machine according to the hardware performance of your host computer. In the window that opens, go to the location where you downloaded the ISO file, select the relevant file and open it.Īfter following the basic steps, click Next to proceed to the next step. To add the Ventura image file to the virtual machine, select Other from the ISO Image drop-down menu. In the Version section, select which version of macOS you will install, and then click the Next button. In the Create Virtual Machine window, type the version of the macOS system in the Name field and select Mac OS X from the Type field. The ambiguity of that last statement is I did that awhile before writing this comment and I don’t recall what I booted into first, only that it worked and was not hard to figure out what to do at that point.After running the virtualization program, click the New button in the tool menu to create a new virtual computer for macOS Ventura. Installation will continue, or you will boot into the OS or get the Recovery Utilities menu (where macOS can be reinstalled from or Disk Utilities run). If the recovery partition isn’t present and valid, these instructions won’t work.Ĭlick the 2nd entry, you should see (and then click): If the 2nd partition isn’t the recovery partition, look under the paths in the list to see if one of them is it. The second PCI path is probably to the recovery partition, the one you need to boot from. The first PCI path in the list is probably the boot partition that doesn’t contain bootable firmware. You should see two entries in a list (they are cryptic looking PCI bus paths). Select Boot Maintenance Manager and click.

You’ll be brought into an EFI text-mode GUI. I was able to fix the UEFI problems as follows ( credit to techrechard website):

Vmbox mac os