I also built a macOS VM in Virtualbox about a year ago to see if our server products were workable on macOS (they had been in the past, but a lot has changed, and none of us have Macs to test with). I have no desire to own a Mac, and don't like macOS, but it's the only way to develop for iOS. I built a couple of different Hackintosh setups when I wanted to experiment with developing for iOS a netbook specced similarly to the original Air, and a desktop roughly specced like a high end Mac Pro of the time with a 290 GPU. Even with video drivers, it might glitch up every once in a while. Audio is a bit finicky, it'll go in and out. Onboard wifi / bluetooth might not work either, you'll probably need a third party adapter. The time to tinker around with it just wasn't worth it for me.Īs the author stated, a lot of functionality doesn't work out of the box. It was definitely fun as a pet project, but I've learned my lesson. After fiddling around for 5 minutes (if I'm lucky) to an average of 30 minutes, by trying to boot into recovery mode / different configurations, I'd be able to get back into the OS. I would reboot the computer and it would get stuck on the bootloader. The second and probably most frustrating them about the hackintosh was when it spontaneously stopped working. This meant doing several days of research / debugging, getting all the right software to update versus clicking one button and knowing it'll work. Not being able to do patch updates was fine, but XCode and a number of software always needed the latest OS. Having done a hackintosh myself, I'll chime in and say the cost of upkeep wasn't worth it in the long run.

Arch linux macbook el capitan