
Another way, if you still have the Big Sur installer on the disk, is manually creating another 12GB virtual disk and creating a Big Sur installer on it, then using that installer to fix the boot sequence.Īgain, the problem is probably very minor and I'm giving these hacky solutions so I don't have to look into, but it's probably the source of the issue and it's probably very simple to fix it. Select Boot From File and click You should see two entries in a list (they are cryptic looking PCI bus paths). Select Boot Maintenance Manager and click.

The proper solution would be fixing Big Sur's boot settings, or, if the VM has nothing on it, deleting the VM and making a new one, then upgrading to Big Sur when it's the only attached bootable disk so the boot sequence doesn't get complicated. Youll be brought into an EFI text-mode GUI.

Since Big Sur boots with the Catalina installer disk attached but fails if it's the only disk, the problem is definitely minor and probably somewhere in.
