![]() ![]() And please don't go applying Hackintosh tactics when you don't need them. VBoxManage modifyvm "macOS High Sierra" -cpuidremoveallBTW, if you cloned the VM from a 10.12 guest, you should also do the same for the 10.12 guest, just remember to change the VM name in the commands above ("macOS High Sierra"). VBoxManage setextradata "macOS High Sierra" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" ![]() VBoxManage setextradata "macOS High Sierra" "VBoxInternal/Devices/smc/0/Config/DeviceKey" VBoxManage setextradata "macOS High Sierra" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" VBoxManage setextradata "macOS High Sierra" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" That file is formatted as Mac Os Journal Extended. My original VMware hard disk file that was not booting was still connect, and I transferred all my settings to the new Mac OS High Sierra file that is on the page here. During setup I selected transfer from other mac. Any window opens pretty slowly, even though the host or guest CPUs are not solicited that much. What I did to fix Problem 12 was to use the High Sierra file from this page. VBoxManage setextradata "macOS High Sierra" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" Now the 10.13.6, created from the full installer, does work, but feels very sluggish. Please remove them by issuing the following commands, while the VM is completely shut down, not paused or saved:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |