|
ESX 3.5 would be a good idea. With that you should be able to get the PCI id for the NIC / disk controller and that way we can see if ESX 3i will recognize it.
|
|
I have ESXi 3.5 U2 running now for a couple of months (started just after the time-bomb-bug) on my DELL Poweredge T105.
I wrote about it on my blog on http://blog.virtualarchitect.nl. I am not experiencing any problems with this version of ESX(i). I recognize the issue about the network and SATA controller being unavailable, but this only happens if you use an older version of ESX. Because the internal broadcom networkadapter is relatively new this device is not supported in older versions. I told the BIOS to boot from USB first (If I recall correct, this option is 'hidden' beneath the SATA option). I have made no modifications to the system other than adding extra memory which I ordered through a local computer store. So no disabling of devices etc. I use local storage at the moment with the SATA controller that's part of the standard configuration (no SAS -RAID controller). (update: changed url because blog moved to other url) Message was edited by: gklooste |
|
First of all it's important to understand that the chosen hardware is not on the HCL, so it's officially not supported. Having said that, I know that a lot of systems that are not on the list actually do work, with or without some modifications. I tend to keep my environment as close to the original version as possible. Using the T105 with Vmware ESXi is possible as I explained in previous replies and on my blog http://virtualarchitect.nl. Why would you not use ESXi booting from a USB device? The only thing you have to do is change the boot option in the BIOS to boot from USB (and of course create an USB stick with ESXi on it.
|