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.
Run mac os on virtualbox windows#
Parallels and UTM also support other OSs that run on ARM including Windows but not macOS. To run a virtual machine on Apple Silicon currently Parallels, UTM and Docker support Linux ARM VMs. The second PCI path is probably to the recovery partition, the one you need to boot from. VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product. 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. 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. cd 'C:Program FilesOracleVirtualBox' VBoxManage modifyvm 'macos' -cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff VBoxManage setextradata 'macos. 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). You’ll be brought into an EFI text-mode GUI. The below instructions have worked for some users, but the developer of the script above has warned that some of these commands are unnecessary and may cause more issues than they solve.
I was able to fix the UEFI problems as follows ( credit to techrechard website):