Not-so-general guide for achieving a physical boot Mac from a virtualized Mac… admittedly very dense with my own details, yet the core idea is simply this:
Boot into a Mac VM and from there, install OS X to your physical drive.
KVM OSX Guest 10.11 (El Capitan) with Clover. Some notes about this approach: An OSX Installer USB drive for Install OS X El Capitan is created. Clover is then installed on the USB drive. Clover Configurator is then run on the USB drive. The USB drive contents are copied to the VM host. VNC is used to connect to the guest UI. Realtek ALC AppleHDA Audio Patch Methods v2 – select one. RealtekALC/patch in place – new script detects the codec and patches the native AppleHDA.kext for ALC onboard audio. Run the same script to restore audio after Software Update. Piker-Alpha AppleHDA8series – i nstalls an audio support kext for ALC onboard audio.
It works and it’s potentially easier than the well worn USB approach… after tons of reading I wonder why we don’t see this approach get any airplay.
This guide assumes you’ve already got a WinPC that you want to boot into a Mac sometimes… to keep the lingo crisp, let’s call your existing Windows install “WinPhys”, along with MacPhys and MacVirt… so we use WinPhys to run MacVirt which installs MacPhys… and then we can actually flip around and run WinPhys VIRTUALLY under Mac virtualization tools, pretty meta.
Of particular note is the “MBR trick” to get around Windows (10) blocking boot sector mods, required for installing the Clover bootloader installation.
Software versions only listed for reference as of this build, not crucial unless noted.
Major Parallels/Fusion VM performance fix!! – the nutshell is apparently the xhci stuff has a major impact… i had mine disabled but then didn’t have xhci manual mode selected
nor the GenericUsbXhci.kext loaded (see El Capitan update under Software Bits 8.4) and after doing both of those my Parallels 10 performance was respectable…prior to that all Windows VM spinups were major slow and obviously just hammering the first core from Activity Monitor, afterwards all cores jump around randomly.
Bootcamp under Parallels, fix “missing operating system” – first shutdown the Bootcamp guest VM so you can make configuration edits, then “Edit Partitions” and for me, my little recovery partition wasn’t selected vs the main Windows OS partition, just had to select it (in addition) and restart.
Updating OSX <=> Nvidia drivers – SEE THIS POST – the Nvidia “web drivers” are rather obnoxiously hard wired to each specific OSX point release (e.g. just going from 10.12.5 to 10.12.6)… so the first boot right after an upgrade requires special attention because the previously installed driver is no longer compatible… the main thing to be aware of is temporarily adding nv_disable=1 to your boot args via the Clover “options” page, which gets you back into a working low res desktop where you can follow the Nvidia driver automatic update process…
Using MacPro6,1 for your SMBIOS requires a special patch – see Fix#4
I’ve come to understand that iMac14,1 is one of the more forgiving choices… Apple is changing the USB game a lot starting with El Capitan… they are restricting USB ports depending your SMBIOS machine… reportedly iMac14,x does not currently (v10.11.2) receive any restrictions on the USB 2.0 side (EHCI)… i can report at least all my USB2.0 devices operate (Logitech Z305 speaker, Logitech C910 webcam, Logitech Anywhere receiver)
starting from a completely bare drive – just format it as GPT Journaled with a single partition via DiskUtil – this will create an unavoidable ~200MB EFI partition which is good for clover
Yosemite installer or Recovery script will add “Recovery HD” partition – however, i don’t particularly see the need for Recovery mode vs booting into full OSX VM for any troubleshooting
on the VM image i had major kernal_task CPU crunches that would storm in and bring everything to a stand still… guessing thru googling that some IO kext is getting hung up… i disabled sleep and this issue no longer occurred, no big surprise.
easy success with Migration Assistant restoring from Time Machine backup after booting into a fresh OSX install makes this my preferred approach – see “Time Machine saving to Windows share” under Misc tweaks below.
Under OS X 10.11 El Capitan and beyond, SIP presents a new challenge to hacking kexts (good ref)
defaults write com.apple.DiskUtility DUDebugMenuEnabled 1
(sorry screenshots lost to the sands of time)
First off, Happy St. Patricks Day!
It has been a question that many Hackintoshers have been trying to solve since the release of the Yosemite betas last year. How do we get iMessages to work? Many have tried and many have failed. What has seemed to lack is a good comprehensive guide covering a wide range of scenarios.
This guide over at Tonymacx86 is a pretty detailed resources and should help you get your setup going. You are best to use the Clover Bootloader as is seems to handle the manual values as well as NVRAM much better then Chimera/Chameleon. I will note the chapter I followed for each setting in my setup.
Anytime I would try to sign in to Messages, I would get the “An error occurred during activation. Try again.” message. This was good news for me since I just had to make sure Clover had the right serial numbers and so on. Some situations will still require you to call in to Apple to have them whitelist your serial and some other values. For my situation, all I needed to make sure I had valid was:
I also made sure that all of my configs for iMessage and iCloud were deleted prior to doing anything as to make sure I started as fresh as possible. (Chapter 3.3)
Note on the SmUUID. It is better to generate a unique SmUUID and not assume that your motherboards will work with Apple’s servers. Just run uuidgen from the terminal 4 or 5 times and use that value in Clover Configurator. Also make sure, as is detailed in chapter 3.2, that your ethernet and wifi are labeled as enX and showing as Built-In for this to work right.
Once all of these were set up with correct values, I did need to change my Apple ID password. Once reset, I was able to login and send/receive iMessages once again. Once you have correct values, you will want to always use these with your particular motherboard/cpu combination as to not blacklist that system in the future as long as Apple does not change their verification process again.
And finally, a big shout out to jaymonkey who has spent countless hours keeping his guide up to date. Without his collection of information, iMessages would not be functioning on Yosemite Hackintoshes.