vmdk is set up or where it came from so I can't really help you from that step. Boot device has Clover -> Clover fakes a Mac -> OS X starts thinking its a mac.BIOS/EFI in the VM looks for boot device.So simply put, the boot order on the VM is the following: What Clover EFI does is mimick what Apple wants to see.
Mac's being Apple, they are particular in the instructions and look for specific things. The only difference in PC or a MAC is the EFI.
On both Mac and PCs (modern), the boot order is the following: You may in that case need to edit the VM and tweak various settings in the VM settings to make it work better in respect to your Windows HOST computer (i.e. It sounds like you straight downloaded a premade 'hackintosh' or virualbox VM image for a Mac. vmdk is the file that represents a physical hard drive, since nothing is physical. In a physical machine, a hard drive is a 3.5" or 2.5" rectangular box with platters (or SSD) inside. In a VM, everything is virtualized into signals or files in respect to physical hardware and signals on a tangible computer. They like to use "multibeast" instead of Clover. TonyMacX86 is a great resource and other solutions.
I'll post an image of the error soon currently reproducing it as I deleted the files for the Virtual machine accidently. Supports Hyper-V (which I had turned on in the BIOS, Because, you know, one of the first things people do with a new laptop is edit the BIOS ) Manufactured by Lenovo, Model #720-13IKB.Pen and touch support with 10 touch points (anyway I can use that somehow in the macOS VM?).MacOS Sierra download I used on both Link removed, as that could send a copyright strike my way. I am still very open to others answers though. Problem is, the installation is not going smoothly as it had on VirtualBox VM space on my MacBook Air Early 2014 running seems really good at Macs and the like, so I suppose he could help. I'm trying to use MacOS (Sierra) in a VM space on my Windows Lenovo laptop using VirtualBox app.
0 kommentar(er)
