Return to Answer

added 5 characters in body

Source Link

edited Jan 9, 2021 at 19:51

I found a fix! In one Virtualbox Forum a user suggests to run the command VBoxManage modifyvm "High Sierra" --cpu-profile "Intel Core i7-6700K"

I replaced High Sierra with my VM name and the VM booted to the installation after seecting the boot.efi file! It took a long time, but I will update this when thenow have a working Mac VM finishes installing.! =)

I found a fix! In one Virtualbox Forum a user suggests to run the command VBoxManage modifyvm "High Sierra" --cpu-profile "Intel Core i7-6700K"

I replaced High Sierra with my VM name and the VM booted to the installation after seecting the boot.efi file! I will update this when the VM finishes installing.

I found a fix! In one Virtualbox Forum a user suggests to run the command VBoxManage modifyvm "High Sierra" --cpu-profile "Intel Core i7-6700K"

I replaced High Sierra with my VM name and the VM booted to the installation after seecting the boot.efi file! It took a long time, but I now have a working Mac VM! =)

Source Link

created Jan 9, 2021 at 19:02

jerbear4328

I found a fix! In one Virtualbox Forum a user suggests to run the command VBoxManage modifyvm "High Sierra" --cpu-profile "Intel Core i7-6700K"

I replaced High Sierra with my VM name and the VM booted to the installation after seecting the boot.efi file! I will update this when the VM finishes installing.