Don't know how to create vib files, as far as I can tell it requires the DDK, which I don't have access to.

As for using the oem.tgz file on an already installed instance, upload and replace the oem.tgz somehow to the /bootbank and /bootbankalt folders in the esxi install. If you plug the esxi system drive directly into a Linux machine, these folders will show up as partitions "hypervisor1" and hypervisior2". Thats what I did actually while dev testing the driver(plug usb key into linux machine and replaced the oem.tgz file in hypervisor1 and 2 paritions).

Otherwise, the instructions at http://www.vm-help.com/esx40i/customize_oem_tgz.php should work for new installs.

[EDIT] If you enable SSH temporaly, you should be able to connect via SCP (using something like WinSCP) and upload the file(oem.tgz to bootbank and bootbankalt) that way! I just tried it myself and it worked!

Whoops, I added it to pci.id, but made a typo in the simple.map file.

I'll fix it and upload a new copy with fixed simple.map file so others don't need to fix it manually.

[EDIT] Fixed! Uploaded new oem.tgz file with the fixed simple.map, check my original post!

Wooohoo, after several hours of figuring this out. I have manged to get it to work!

What I did is boot ESXi with normal oem.tgz. Then copy simple.map and pci.ids to a separate folder in /bootbank

Then, boot a linux distro live CD. Copy the oem.tgz into the separate folder and make the necessary changes in there. Using the simple.map and pci.ids which you got and copied during the ESXi boot. Adding the .o file, etc.

After that, reboot into ESXi again. And replace the stock oem.tgz with the edited one from the separate directory and reboot again. After this, everything should work as intended.

Since I run from USB, I can use a seperate system to edit. All the scripts and other guides would NOT work for me with 4.1u1! No clue why. Also the default oem.tgz does not have a simple.map or pci.ids in there! You need to fetch it from a running system first.

Yes it's empty, you need a oem file from this or some other site or copy the files from a running system

Awesome! So you used my simple.map and pci.id from my oem.tgz file then? If you didn't, did you make sure to modify it to include the pci ids of your nic into them? This is important, otherwise esxi won't load the driver automatically since it won't detect the NIC!

Let me know if your esxi install detects the NIC, your post was a little confusing, and if so... Glad to hear you've got it working!

Ah, no. Using your oem.tgz resultated in my system losing my AHCI storage controller. I figure this is because you are not running 4.1u1 or your simple.map file is from a different/older version.

So I had to install a "virgin" system en get the original files and I editted those.

I did not need to add it to the pci.ids because the NIC is listed in there. Probably because of the recent version! So only simple.map and .o file, .xml file and .mf file.

As promised I did some iperf tests!

Server Windows 2k8 R2 vmxnet3 (using e1001 with 82579LM)
Client Windows 7 intel 82567V-2


So, as you can see this performs very well. Using 64KB blocks still gives you maximum bandwidth. Go lower then that and the bandwidth starts to drop a bit, but that isn't unusual.



This was a full-duplex test. It needs more then 64KB blocks to get the full bandwidth, but again, that is not unusual either.

So all is well according to these simple tests. I have started to use the NIC as the main NIC to see how well it behaves. If there is any trouble, I will let you know.

Thank you VERY much for this driver and all the help!

Ahhh, I'm actually using 4.1u1 as well actually, but you are correct, the simple.map file I'm using is from an earlier version. Information like this is great! Its not related to my driver, but I shall go and update the simple.map once again, ensuring that I use the 4.1u1 version, so that others don't encounter the same issue as you did.


Good to hear the drivers working well! Thank you for these tests!


You are most welcome! I'm going to go update the simple.map file(again ) now and re-upload the oem.tgz to my original post.

[EDIT] Updated! Uploaded new oem.tgz file with the updated simple.map, check my original post!

@Chilly Does your modified oem.tgz works for 82578DM as well? Also could you make a new oem.tgz with the latest e1000e-1.3.17 ( http://sourceforge.net/projects/e1000/ ) ?

Without editing the pci.id and simple.map file and whatnot, no it won't. As for the actual driver itself, I don't see why not. I have no way of testing it myself but... Try loading it(e1001) and let me know!

I'll look in to it. I'm quite busy right now, but if the changes from 10a - 17 aren't too extensive, maybe I could get something made and out this weekend.

Thx for the quick response Chilly. I will try your oem.tgz in weekend and hopefully i'll manage to get it running for my 82578DM(i'm really a begginer and try to figure all this things out).