VMware ESXi 5 whitebox NIC support

I tested the following NICs in my VMware ESXi 5 whitebox server at home:

NIC Recognized by VMware ESXi 5 Listed in ESXi 5 as
Intel PRO/1000GT Desktop Adapter PCI Yes

Intel 82541PI Gigabit Ethernet Controller

Realtek RTL 8111E Yes Realtek 8168 Gigabit Ethernet
Intel Gigabit CT Desktop Adapter PCI-e Yes Intel Corporation 82574L
Intel 82579 Gigabit LAN controller No

You need the make a customized ESXi 5 ISO or VIB file.

This is a not supported configuration!

Intel Corporation 82579V 

or

Intel Corporation 82579LM

To add the Intel 82579 chipset, create a customized ESXi 5 ISO.  This is very simple because some people have already done the hard work.

Here are the steps:

1. Download ESXi-Customizer (create by Andreas Peetz) found here.

2. Download the driver (created by Chilly) found here.

3. Start the ESXi-Customizer and follow the 3 steps:

2011-12-04 17h03_20

And your ready to install the customized VMware ESXi 5 ISO. The ISO supports the Intel 82579V and 82579LM NIC(s) found on many whitebox motherboards.  Possible future updated version(s) of the driver can be found in the following post.

Be Sociable, Share!

25 Responses to VMware ESXi 5 whitebox NIC support

  • Erik Bussink says:

    Note that with the Realtek 8111E you cannot enable Jumbo traffic (MTU 9000) but you can increase the MTU to 1524 for vCD-NI support.

  • Tom Miller says:

    Thanks for the info. This is great news. My whiteboard has the 82579 NIC. I’ll use this process to get it to work.

  • Saurav Das says:

    I tried out the patched Esx 5.0 it works fine.I tested the system on s1200bts motherboard with xeon 1240 processor and 8 GB memory. While the original ESX iso installation did not recognize the 82579 onboard NIC, the patched version is working fine, I have test run it continously for 10 days without any abnormal server performance or errors. It is resonable to say that the patch is a stable release (at least initial tests confirm this). A big thank you to the Beerens. And I hope this review helps others using this patch.

  • RAJESH KUMAR CHATURVEDI says:

    I am also have same issue, Try to customize iso with 82579V driver for ESXi 5.0 but customizer asks for .tgz or.vib files but driver is not downloaded is not in supported format.

    Please suggest me How to proceed?

  • RAJESH KUMAR CHATURVEDI says:

    Driver downloaded is not in supported format.. & unable to customize…
    Please suggest me…
    Thanks in advance…

  • Ivo Beerens says:

    @RAJESH Did you downloaded the *.TGZ driver from step 2?

  • Phil Ross says:

    The file created by Chilly comes in .tar format. Just rename to .tgz. Works like a charm on my box. Thank´s all.

  • Otto says:

    Thanks guys, will try this now on the whitebox to check and will update!

  • Otto says:

    Perfect! Thanks for the awesome work!

  • Hans says:

    Does not work at all!
    Making of new ISO work’s fine but still No Network Driver when installing.

  • narba says:

    I have a nic of realtek pice gbe family, i tried installing esx 3.5 but it shows lvmdriver failed to load, so now gonna try esxi 5. So will this customizing work on my specified nic….pls helpout

    Thanks in advance

  • Salil says:

    Folks, I tried the above solution. This time I got ESXi 5 installed however after the reboot, I get an error saying “cannot find boot device”.
    Anyone come across this.
    Here are the specs of my whitebox ESXi 5 server
    Intel desktop motherboard with the Intel 82579 Gigabit LAN controller
    16Gb RAM
    2 x 1TB SATA drive

  • Confused says:

    Hello
    You said that intel 82541PI can be used with esxi 5 but I am having issues with it.The thing is kernel can see it and lspci shows it but its not available on gui. Mind you I did migrate from esx 4.1 to esxi 5 and whole process went fine but as I said one nic that I mentioned cant be used a all. Can this be fixed (adding drivers) and how?

  • Stephan says:

    Thanks a lot! Worked perfect!
    @Salil: Regarding the boot problem: I enabled UEFI boot mode in BIOS, then it worked.

  • Please help me, I exec script and obtain the follow message:

    FATAL ERROR: Error extracting the original ISO file

  • hzgmax says:

    I can NOT download the “http://dl.dropbox.com/u/27246203/E1001E.tgz”, because I am living in PRC, would you please send me the E1001E.tgz to me: hzgmax@21cn.com. Thank you very much!

  • Arindam Adak says:

    Hi Ivo,
    Thanks a ton…
    I am having a server with s1200bts motherboard & despite all efforts, I was not able to use one of the on board NIC. With this solution I have both the NIC active & working good. Everything went on smooth! Thanks a lot!

    Arindam

  • iarp says:

    ASUS P8Z68-V PRO/GEN3 that runs Intel 82579 network.

    This solution worked for me, thank-you.

  • Turkey says:

    thank you. it is realy good. thank you for this solution

  • James says:

    Brilliant, thank you so much. This worked a treat. I’d been looking for ages for a solution and was tearing my hair out!

  • Dermot says:

    Does this ESXi Customizer work for ESXi 4.1 also?

  • Jakub Rybář says:

    Ivo, how have you turned on working Patsburg 6 Port SATA AHCI controller on ESXi 5.0? Do you use it in AHCI mode or should it work also for RAID mode? Thanks!

  • curtis goble says:

    I am getting
    FATAL ERROR: rror creating the customized ISO file!

    and I downloaded the driver in step 2 and renamed it to .tgz

  • Joe says:

    All seems to go well, but then upon reboot, I get “no boot device found”. What is interesting is that if I hit F10 to force the BIOS to use a specific boot device, the disk drive is listed, and it boots. But it seems to not have any idea how to boot from the disk drive if left on its own.

    Not that useful for a backroom server with no keyboard/monitor :-)

    Im running ESXi on a DH67CF motherboard with BIOS 0132. VMware 5.0.0 Update 1.

    Any ideas anyone?

  • Joe says:

    All seems to go well during the ESXi install, but then upon reboot, I get “no boot device found”. What is interesting is that if I hit F10 to force the BIOS to use a specific boot device, the disk drive is listed, and it boots. But it seems to not have any idea how to boot from the disk drive if left on its own.

    Not that useful for a backroom server with no keyboard/monitor :-)

    Im running ESXi on a DH67CF motherboard with BIOS 0132. VMware 5.0.0 Update 1.

    Any ideas anyone?

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre lang="" line="" escaped="" highlight="">