Turns out that a VirtualBox EFI virtual machine CAN boot Clover with my Mac drive. I don't know what that means. And it is certainly a broken, clover, with no config file read correctly. I think this because the theme is "embedded" instead of any of the ones I have picked, and none of the other options I set in the condif work either.
It is so frustrating that Clover USED to work fine on the UD7. THIS NOT SUPPOSED TO BE THE HARD PART.

I still hve not opened the case yet, but I think it is a GPT/parition/filesystem/EFI data problem, not a Motherboard/Firmware problem. The evidence is that when I disconnect all the other drives, I see the UEFI: label for the Mac drive, and can selet it for boot. but then I get the no-media message instead of Clover.

Using the downloaded Clover r1943 did not work, so I am going to build a new custom Clover 1945. I don't expect that to make the ESP on the Mac drive be recognized either, but opening the case is so much work, ANY software solution is worth a try.

It is very annoying to take such a big step backward, considering that I previously had Clover running successfully.

This is possibly an undocumented limitation of the UD7, or the Chipset, or the controller, where only some ports of some SATA controllers are recognized as bootable UEFI devices. However, the Mac drive is on the same SATA controller as the Windows boot drive, and disconnecting the Windows drive does not help.

The Mac drive is currently on Bus Number 5, Target Id 0 Lun 0. The “Friendly name” is ATA ST1000DM003-1CH1 SCSI Disk Device. The SATA controller is Intel C600 Series Chipset SATA RAID Controller.

Dang.
Suddenly, the UD7 will not boot off of the ESP partition. It worked a few weeks ago, when the drive was on a differnt port. I hope I dont have to open the case and switch SATA ports or something. I'll look again in the mobo GUI for relevent settings.
That did not work.
 I'll reinstall Clover 1913, and if no luck, I'll open the case.
Opening the case is a big deal on this machine. The mass is at least 34 kilos (75 lbs)  and must be deinstalled from a custom self, and hoisted onto a workbench. The drive "works" fine, so it is an unpleasant surprise to find it will  not boot in the current config.

I am hopeful that A post on InsanlyMac will give me a good start, because currently it hangs soon after the MAC Framework is initialized.

Accordingly, I am going to look for:

• AHCIPortInjector.kext 
• FakeSMC.kext
• NullCPU.kext
• intel e1000 lan kext 
• SleepEnabler.kext

Basic info.

The Black Haqintosh is a super-premium custom hardware Macintosh project. The hardware is 6 core, watercooled, and tri-SLI. If  I can get it running, it could be one of the fastest macs in the world.
This blog is a diary of my attempts to configure it.

Here is the hardware for my hackintosh attempt:

SYSTEM: CPU: Intel Core i7 3960X @3.3GHz
Motherboard: Gigabyte GA-x79-UD7 (UEFI 10)
RAM: R-Skillz RIPJAWS 16GB DDR3 1600Mhz
Video:NVIDIA 680 GTX
Audio: Creative SB X-Fi

Sata drive 2 is dedicated to the hacintosh, I call it the Mac drive. I have a working OSX 10.8 VirtualBox vm, I use it to work on the Mac drive. I access the Mac drive my using VIrtualBox's raw host drive facility.

I will boot from an EFI system partition (ESP). OSX 10.8 will be installed on the second partition, labeled EXECUTOR. Bootloader is Clover, I built from source, Version 2, revision 1913. I used the clover installer on the ESP.

I have installed the GA-x79-UD7 DSDT.aml into EFI/CLOVER/ACPI/patched, My config.plist is mostly defaults, I may need to hack many attributes, especially the FixDsdtMask. This is all opaque at the moment.