sofakng, on Sep 11 2011, 03:59 AM, said:
I was also going to ask how this worked, but really I'm just wondering if this might affect the stability of the ESXi host.
Does this patch the VMX binaries used by the entire system, or does it only patch binaries that the OS X host would use?
EDIT: Also, I'm having a problem installing Snow Leopard. I've patched my ESXi 5.0 system, rebooted, and created an "Apple OS X 10.6 (64-bit)" guest operating system. I'm using the host CD-ROM drive.
When the guest os boots, it boots my retail Snow Leopard DVD and I see the Apple logo, but then a second or two later I see a blinking cursor and the system reboots over and over...
It is a system wide patch, but can easily be removed. The patch will not alter anything for any other guest VMs and when remved the system is completely put back to the installed version as everything used RAM disks in ESXi. Basically the patch allows the SMC controller and MAC OS X checks to pass without any other CD etc., and is the equivalent to the code path inside VMware Fusion.
I understand your dilema and I would say to anyone who wants to use Mac OS X or any form of productive use buy a Mac or virtualize on a VMware approved platform such as Mac and Fusion or Xserve and ESXi. On that last note I see no code that checks for Xserve, and booting ESXi on my Macbook Pro showed all the ESXi Apple drivers correctly loaded.
For SL what is the CPU in the host and what version of SL? Do not forget that early SL version cannot support later CPUS e.g. Sandy Bridge until 10.6.7.