Ga door naar hoofdinhoud

Apple's operating system for its Mac desktop and portable computers.

72 Vragen Bekijk alle

Running MacOS in a virtual machine (VM) on a Windows Syst?

Block Image

I'm trying to use MacOS (Sierra) in a VM space on my Windows Lenovo laptop using VirtualBox app.

Problem is, the installation is not going smoothly as it had on VirtualBox VM space on my MacBook Air Early 2014 running Windows.

@mayer seems really good at Macs and the like, so I suppose he could help. I am still very open to others answers though.

MacOS Sierra download I used on both Link removed, as that could send a copyright strike my way. Sorry for any inconveniences.

Guide I used for both


Laptop Specs:

Windows Laptop

  • Windows 10 Home 64bit
  • 8GB RAM
  • Pen and touch support with 10 touch points (anyway I can use that somehow in the macOS VM?)
  • Intel Core i5-8250U CPU at 1.6GHz
  • Manufactured by Lenovo, Model #720-13IKB

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 [sarcasm])

Macbook Air

Specs: MacBook Air (13-inch, Early 2014)

  • 13”
  • 1.4GHz
  • 128GB


I'll post an image of the error soon currently reproducing it as I deleted the files for the Virtual machine accidently.

Beantwoord! Bekijk het antwoord Dit probleem heb ik ook

Is dit een goede vraag?

Score 0
Voeg een opmerking toe

3 Antwoorden

Gekozen oplossing

Use clover to install the custom KEXTs.

Also try the free VMWare Player. I've always found it to work best on Windows.

Was dit antwoord nuttig?

Score 5

6 opmerkingen:

I'm confused on the clover bit. will this effect the host or the guest?


Jeez @avanteguarde, you make me feel like a noob. Next thing I'll be asking you why I can only use 6GB out of 8GB on my RCA voyager.


Vmware. I remember looking into that... I didn't get it because it was paid.


@pccheese I try to stay away from the RCA voyager questions. :-)

@captainsnowball the "VMWare Player" is free for personal use. They don't mention the fact that you can create VMs with it but that feature is there. :-)

"Clover" is an artificial Mac EFI Bios. It is going to part of the "guest". Windows is always the "host". So if you have a real Installer in ISO format, it will boot it and let you install it. Then I believe there is a way to install the proper KEXT to the system folder so that you can have better performance.


So I should get a .iso (a or an? a dot iso or an iso?) file instead of my .vmdk?

@pccheese Looks like neither of us are interested in voyager. to many "forgot activation code" stuff


1 commentaar meer tonen

Voeg een opmerking toe

TonyMacX86 is a great resource and other solutions.

They like to use "multibeast" instead of Clover.

In a VM, everything is virtualized into signals or files in respect to physical hardware and signals on a tangible computer. In a physical machine, a hard drive is a 3.5" or 2.5" rectangular box with platters (or SSD) inside.

On Virtualbox, a .vmdk is the file that represents a physical hard drive, since nothing is physical.

It sounds like you straight downloaded a premade 'hackintosh' or virualbox VM image for a Mac.

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. increase RAM?).

On both Mac and PCs (modern), the boot order is the following:

• user turns on the computer providing power

• BIOS (or EFI) checks for security, hardware confirmation, and starts to load the OS from the hard drive (or USB or CD/DVD)

The only difference in PC or a MAC is the EFI. Mac's being Apple, they are particular in the instructions and look for specific things. What Clover EFI does is mimick what Apple wants to see.

So simply put, the boot order on the VM is the following:

• user turns on the VM

• BIOS/EFI in the VM looks for boot device

• Boot device has Clover --> Clover fakes a Mac --> OS X starts thinking its a mac

I'm not sure how your .vmdk is set up or where it came from so I can't really help you from that step.

What I can tell you, is if you do have a working Mac with installers of anything except High Sierra (haven't figured that one out yet because of a mandatory FW upgrade), you can create your own VM and start from scratch and you can figure out and learn what exactly is going on.

• Create an installer via normal OS X instructions on the Mac

• Follow this to make it PC bootable

• With this you should be able to create a blank VM and install OS X from scratch like a normal Mac

Was dit antwoord nuttig?

Score 3

5 opmerkingen:

Everthing on that website has a face I guess? Well still functional stuff


LOL, sorry, I honestly don't know why there are googly eyes on all their icons.


Do you have a Copy of the Mac OS I need to get from a mac? (My mac is running windows, But also I don't have any of these issues using a virtual machine running Mac OS on my MacBook air... it just runs.)


There is no way I could get it to you. My upload is 0.25mpbs upload.


Thanks for such great information!


Voeg een opmerking toe

I have almost the same computer settings, but my virtual box works fine without any problems. I think that you need to change something, namely this detail: vmware port group. I once met a similar situation with my friend, and almost the same thing happened with his Mac. That's when he started using the vmware port group. He told me about it after fixing the problem, but it turned out to be very interesting, so I began to study it in more detail. I hope this will be useful to you

Was dit antwoord nuttig?

Score 0
Voeg een opmerking toe

Voeg je antwoord toe

Aiden zal eeuwig dankbaar zijn.

Afgelopen 24 uren: 1

Afgelopen 7 dagen: 1

Afgelopen 30 dagen: 14

Altijd: 23,248