I tried with the original 2x2GiB memory modules. As expected, it made no difference: pink screen.
I also tried to pre-install ESXi 5.1 on USB key on another (older) MacMini and boot the new MacMini from that USB key. It booted up, but gave me the very same pink screen. That also was to be expected, but I wanted to make sure.
I hope that VMware is quickly taking on that case, because I suspect the same problems with all new Apple machines (iMac and MacPro). If that will be the case, there is no hardware for the VMware Macintosh support any more.
I smile about the fact, that VMware officially still only supports the Apple Xserve - a hardware, that's not produced since almost two years! So there's a great product - we have lots of customers using virtualized OsX - but no hardware to run it.
Hi ViennaAustria and saltmaster,
Thanks for letting us know about this problem – in pink text no less! Apologies for the trouble... There is obviously something about your new Apple hardware that we're not handling. I've filed an internal bug report so that our ESXi hardware folks will investigate the problem.
Here's a possible workaround...
Very early in the boot process, a prompt appears in the bottom-right corner of the screen to press Shift+O to edit boot options. At that time, press Shift+O and you'll get an editable line of text along the bottom of the screen with a cursor at the end. Add a single space followed by:
Then press the Enter key and the system will attempt boot.
I don't have access to the relevant hardware right away, so I haven't got the opportunity to test out the above... I thought it would be worthwhile to pass the information along promptly and hope that someone could give it a try and see if that is all that's needed to get ESXi to boot on this hardware.
I can confirm adding the boot option iovDisableIR=TRUE does do the trick. After adding and modifying the most recent tg3 drivers for the NIC I was able to get it up and running (have to add in the PCI device ID, looking at the drivers source code there is support for the specific revision it just isn't included on the PCI device mapping tables).
Thanks for the speedy help !!
Thank you for trying that out for us all, saltmaster, and reporting back so quickly with your detailed findings!
We'll keep investigating how to solve the problem properly here. Depending on the outcome, affected hosts will either need an Apple firmware update or an ESXi patch update to get things going smoothly.
@dariusd: I can also confirm that the boot option prevents ESXi 5.1 from crashing. Thank you very much! How to permanently add this boot option?
@saltmaster: can you please help me how to insert the new PCI device id into the device mapping tables? I use a customized image with the latest version of the net-tg3 offline bundle. That works with all the previous MacMini models, but not on the new 6,1.
@all: the Apple Tunderbolt Gigabit Ethernet adapter is NOT working. It worked on the previous MacMini model. What does "iovDisableIR=TRUE" do? Could that maybe affect the Thunderbolt Interface? It was an easy option to add a second network adapter to a MacMini (pitty, that there are no Thunderbolt hubs yet).
As I booted from the pre-installed USB key I saw a message "loading vmfs3 failed" on the yellow/grey ESXi screen. That could be, because I booted from USB and have no VMFS datastore on the Mac yet (the harddisk still contains OsX). Hopefully it's not another adaptation that is necessary for the new MacMini. Saltmaster, did you experience problems with VMFS?
On the installation media there is a file called: NET-TG3.V00
You will need to extract this and edit two files that relate to pci id mapping. The new MacMini's use a BROADCOM BCM57766 which have a device ID of 0x1686. If you copy the entries for say device ID 0x1688 and modify them to reflect the 0x1686 that will get it working.
The V00 file can be extracted using vmtar, followed by a normal tar. The easist way to go about this is to install the hypervisor in VMware Fusion (or if you have it running on another machine already use that). Activate SSH on the Hypervisor, remote in (copying NET-TG3.V00 over), extract the files, modify them and then perform the inverse of the extraction to recreate the NET-TG3.V00 file.
From memory it looked something like:
# vmtar -x NET-TG3.V00 -o NET-TG3.tar
# tar xvf NET-TG3.tar
edit the files
# rm NET-TG3.V00
# rm NET-TG3.tar
# tar cvf NET-TG3.tar etc usr
# vmtar -c NET-TG3.tar -o NET-TG3.V00
Copy the NET-TG3.V00 file onto the installation media removing the older version.
Once you have it installed on the MacMini you can use the following command on the host to have the iovDisableIR settings stick (enable SSH just to perform the following):
# esxcli system settings kernel set --setting=iovDisableIR -v TRUE
One thing, you may want to take a disk image of the installed version of MacOS X ML before playing around too much. I thought it would be easy to reinstall 10.8.2 on the machine after some testing, but that doesn't seem to be the case. I've tried installing from USB/SD card/NetBoot all of which fail (creating the USB/SD card using both DiskUtility/CCC). Internet Recovery also fails.
To that end could someone running Mac OS X on a MacMini 6,2 run the following command to get the Board ID (may just be a simple case of needing to add it into the installation media's allowed machines):
ioreg -lp IOService | grep board-id
Thanks. Installing MacOS X 10.8.2 using target disk mode on another Mac and then modifying "/System/Library/CoreServices/PlatformSupport.plist" got it booting again. After I got it booting I was able to apply: http://support.apple.com/kb/DL1603
my custom built mini is on it's way from China, glad to know ESXi will run, even if it needs some tweaks,
i wondered what storage options people where using, i need some sort of DAS rather than a NAS, and wondered what worked, i don't see any support for thunderbolt raid ?
also is DirectIO or TH supported ? (i guess i'll find out later in the week)
I was also wondering, if i boot from SD, can i create a datastore of the OSX disk, and access that as a vm - writing directly to the real disk ? - other vms would me installed on an external disk.
many thanks, Will