I haven't seen anyone, but other PEs have been fine - http://www.vm-help.com/Whitebox_HCL.php. The main thing is the storage controller and NICs - do you know the specfic models that your system has?
PERC 3/Di for the (RAID) storage controller, I'm not positive on the NIC. I believe it's Intel-based and built onto the motherboard, so I don't imagine a problem there.
The PERC 3/Di is a supported controller - http://www.vmware.com/pdf/vi35_io_guide.pdf and you'll likely be fine with the NICs.
Thanks for your help, Dave. I can now confirm everything works fine with my Dell PE2500. This is a dual 1400MHz (PIII) server using a PERC 3/Di. The PS/2 keyboard is picked up properly throughout the setup and on the console. After entering the license key, I did have to reboot the server once in order to pick up the 2nd processor as licensed.
That's good to hear. I think you win the prize for the oldest server running ESXi. I have an IBM x335 in the basement (single 2.6 GHz Xeon) that's running ESXi after the upgrade from ESX 3.0.2 last night.
If I'm going for a prize, I have a Compaq Proliant 6000 at work that I'm almost ready to retire. Dual 400MHz Xeon with a Compaq SmartArray controller. I'll have to report back how that one goes.
I've got ESXi 3.5 update 3 running on my PowerEdge 2500SC.
I have a PERC 3/Di which didn't work initially but after hearing that it could be done I updated the firmware from 2.5.0 to 2.8.1 and then the ESXi installer was able to see the logical drive.
The processors, which are 1.0GHz Xeons, detect on the console as "AABC" and within the VI client as "%01%01%02%03" but it still seems to be working OK.
Thanks!
How did you update the firmware for the PERC 3 Di controller? From the Windows mode?
My PERC 3 Di is not being recognised in BIOS. Because this machine is quite old could it be related to the battery for RADI?
Thanks,
Tom