I don't think the ASUS M3N78-VM has a Realtek nic, because it's a Nivdia Nforce board. It probably has a Realtek PHY and a Nvidia mac and uses the for forcedeth.o driver included in ESXi.

In the posted simple.map from Dave there are no Realtek entries (vendor id 10ec)

Actually... "Nothing new for adaptec" isn't quite true. New, but not improved.

ESXi 4.0 has removed support for the 78xx-chipset (Adaptec 2940 non-LVD/U2) that some of us have been using to drive our backup tapedrives.

//Svein

Good point. A list of what has been dropped between ESXi 3.5 and 4.0 can be found here - http://www.vm-help.com/esx40i/Hardware_ ... emoved.php

Thank you for the files and all the information!

I got a "working" Image, the Controller is detected as hba1 now in lspci -v.

But in vSphere Client, i can't see the controller and it's attached disks.

Any ideas?



Addiditional Information:
I was confused about the compatibility to some USB-Sticks. A slow one maybe is not able to find the boot partition on the second boot (first boot is okay with a fresh image). Only the fast one can boot multiple times......

For USB sticks you'll want to use USB 2.0 certified sticks. As to the controller issue, what PCI id is it coming up with? Are there any errors in /var/log/messages?

Hi Dave,

both sticks I used are usb2.0 compatible, but the slow one is very cheap quality !

I didn't get an acces with ssh, so i made a foto of the commands:
less /var/log/messages | grep vmhb0 --> outputs related to the correct detected PATA Controller

and

less /var/log/messages | grep vmhb1 --> outputs related to the not connected SATA Controller

You can see, that there are 3 more entrys made by the PATA Controller.

I tried some ESXCFG-* commands, but i got not really any good information whats bad on the current config.

If you run lspci -p is a module listed for the controller?

David, you have the right idea, but alas a bug tiptoed in when you made your list of things no longer supported.

For instance:
ESXi 3.5 Used to have the AIc7xxx to sopport the 72xx, 78xx and 79xx chipsets, which you correctly states is wrong.

However not all the cards that were supported by this are now discontinued.

VMWare ESXi 4.0 has the AIC79xx to support the ... 79xx chipsets, which can be found in all the Ultra2 and up cards(2940u2w 29160 29320, atleast some 39xx cards)

I'm starting to think we need to pool resources here, to get our support.

Has it been verified with 100% certainity that ESXi4 too uses a customized oem.tgz?

//Svein

I used the ubuntu 64 bit edition to get to verify if the drivers for my installation were available, and my realtek 8169 nic was recognized as well as my 3com e100 nic.

Can anyone point out what I can do to get this recognized so I don't get the message

Failed to load lvmdriver

and can finally have ESXi 4.0 installed.

Need to get my lab up asap

AMD Phenom 9750
Gigabyte GA-MA770-UD3
4GB RAM
2x 500GB Western Digital HD

Well as I understand if you edit syslilnux file and add a oem file in the root of the and in the dd file it should use it.

My script support that. Haven't got around to add so you can edit and add ssh / ftp etc from start. I can't find the damn inetd.conf file in the dd. I'm thinking of
getting it from a already installed ESXi4. I haven't enabled ssh on mine to do that.

If there is someone who has done that and could post the inetd.conf on the forum I could add the "extra" part the script.

rgd Daniel