I've installed ESXi 4.0 onto one of the "known good" whiteboxes, an Asus M3N78-VM (bought because it was on said HCL whitelist). At first, it wouldn't load ESXi whatsoever. Surprisingly, upgrading the BIOS (it came with 1009, upgraded to current 1013) and suddenly ESXi worked fine. Next, it took some rather noob troubleshooting but I got the custom "oem.tgz" (found here) into the USB-installed thumb drive of the ESXi install, and then past the PSOD issues due to the file being in the wrong location. I've now gotten ESXi to boot up and function normally (and even see both the built-in Realtek PHY gigabit adapter, and the add-on Intel GT gigabit adapter).
(Just in case anyone wants to say this, I do know about the VMware HCL, and I have checked other entries here & elsewhere for the M3N78 and its variants in regards to ESXi. I wasn't sure how to search for this type of incident, outside of the actual model info.)
The problem, now, is with the storage controller. It ... appears that it's being loaded as follows:
00:09.00 10de:0ad4 1043:82f2 5/ 5/0x69 A V vmhba1
But any time I go into "Add a device\LUN", absolutely NOTHING shows up. I've tried a previously-Linux-formatted drive (former Untangle box's 40GB WDC WD400 drive), and a brand-new unformatted drive (1TB WDC WD1001FALS drive). Nothing shows-up in the vSphere Client whatsoever. So, what am I doing?
Contents of "lspci -p":
~ # lspci -p
Bus:Sl.F Vend:Dvid Subv:Subd ISA/irq/Vec P M Module Name
Spawned bus
00:00.00 10de:0754 1043:82f2 V
00:01.00 10de:075c 1043:82f2 V
00:01.01 10de:0752 1043:82f2 10/ / A V
00:01.02 10de:0751 1043:82f2 V
00:01.03 10de:0753 1043:82f2 7/ 7/0x69 B V
00:01.04 10de:0568 1043:82f2 V
00:02.00 10de:077b 1043:82f2 15/ 15/0x69 A V usb-ohci
00:02.01 10de:077c 1043:82f2 11/ 11/0x69 B V ehci-hcd
00:04.00 10de:077d 1043:82f2 10/ 10/0x69 A V usb-ohci
00:04.01 10de:077e 1043:82f2 10/ 10/0x69 B V ehci-hcd
00:06.00 10de:0759 1043:82f2 255/ / @ V
00:08.00 10de:075a 0000:0000 V
001
00:09.00 10de:0ad4 1043:82f2 5/ 5/0x69 A V vmhba1
00:10.00 10de:0760 1043:82f2 11/ 11/0x69 A V forcedeth vmnic0
00:11.00 10de:0569 0000:0000 V
002
00:16.00 10de:0778 0000:0000 10/ 10/0x71 A V
003
00:18.00 10de:075b 0000:0000 11/ 11/0x71 A V
004
00:24.00 1022:1100 0000:0000 V
00:24.01 1022:1101 0000:0000 V
00:24.02 1022:1102 0000:0000 V
00:24.03 1022:1103 0000:0000 V
01:06.00 8086:100e 8086:002e 15/ 15/0x71 A V e1000 vmnic1
02:00.00 10de:0849 1043:82f2 15/ 15/0x69 A V
Contents of "fdisk -l":
~ # fdisk -l
Disk /dev/disks/mpx.vmhba32:C0:T0:L0: 1008 MB, 1008991744 bytes
64 heads, 32 sectors/track, 962 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Device Boot Start End Blocks Id System
/dev/disks/mpx.vmhba32:C0:T0:L0p1 5 900 917504 5 Extended
/dev/disks/mpx.vmhba32:C0:T0:L0p4 * 1 4 4080 4 FAT16 <32M
/dev/disks/mpx.vmhba32:C0:T0:L0p5 5 254 255984 6 FAT16
/dev/disks/mpx.vmhba32:C0:T0:L0p6 255 504 255984 6 FAT16
/dev/disks/mpx.vmhba32:C0:T0:L0p7 505 614 112624 fc VMKcore
/dev/disks/mpx.vmhba32:C0:T0:L0p8 615 900 292848 6 FAT16
Partition table entries are not in disk order
Please, someone point out my (I'm guessing) totally NOOB moment here. I swear I've done this right, but I can see I haven't or else it'd work.