Adding Realtek drivers to an Auto Deploy 5.5 image

[dbutch1976]

http://www.vladan.fr/realtek-8169-nics-not-detected-under-esxi-5-5/

Hi guys,

In my home lab I have two identical machines which have an on-board Realtek nic and an Intel 1000 nic.  Since upgrading to vSphere 5.5 the Realtek Nic has stopped working.  I understand that this nic is no longer supported by VMware, however I also understand that is still possible to add the drivers to a custom image and this should work.  All the details on this issue and the .vib files required can be found in the attached link.

My question is this:

I want to add the .vib files to my image, but my understanding is that I require either a software depot in the form of a URL, or I need an offline bundle in the form of a .zip file.  This has got me a little confused.  I can't simply add the .vib file directly?  If not, how do I create an offline bundle?  Is there already an online software depot form which I can download the .vib??

Am I able to create an offline bundle simply by zipping the .vib files??  Sorry if I'm making this unnecessarily complex, I thought I could just add the .vib to the image via powerCLI.

Thanks.

[crawfordm]

This article talks about how to create the custom ISO and add the driver to it - How to use vSphere Image Builder to create a custom ISO - VirtualizeTips | VirtualizeTips

Please do not forget to mark helpful and correct answers.

[crawfordm]

Just download the offline bundle from the VMware website and use image builder to add the driver -

[dbutch1976]

This looks promising to me, but I still don't understand why the commands ALWAYS seem to specify .zip files.  Can't you work with the .vib files directly?

Add-EsxSoftwareDepot C:imagedriversname_of_VIB_file.zip

Also, I don't think creating an .iso is going to help me here.  I'm trying to create an image for use with auto deploy, can I take a customized .iso image and use it to create an image for use with Auto Deploy?

[crawfordm]

This article talks about how to convert the .vib to a .zip - http://wahlnetwork.com/2014/03/03/creating-vum-friendly-esxi-images-home-lab-supermicro-servers/

Just download the vibt2zip program and follow the instructions.

Follow this article to show you how to prep your custom image for autodeploy - http://www.yellow-bricks.com/2011/08/25/using-vsphere-5-auto-deploy-in-your-home-lab/

[dbutch1976 · Accepted solution]

Hi crawfordm,

Thanks for all your help, I definately could not have done this if you hadn't pointed me in the right direction.  Using the links you provided I was able to perform the entire fix from within PowerCLI, I'm going to include the commands I used below so that anyone having a similar issue can fix it the same way.  I didn't get a chance to use the .vib to .zip converter tool, but that definately looks like a valid way to approach this also.

Here are the PowerCLI commands:

Set-ExecutionPolicy Unrestricted
#Get the old version of esxi 5.1 which has the realtek drivers.
Add-EsxSoftwareDepot https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
Export-EsxImageProfile -ImageProfile "ESXi-5.1.0-20140604001-standard" -ExportToBundle -FilePath c:\depot\ESXi-5.1.zip

#Get the most recent version of esxi 5.5

Export-EsxImageProfile -ImageProfile "ESXi-5.5.0-20140604001-standard" -ExportToBundle -FilePath c:\depot\ESXi-5.5.0-20140604001-standard.zip
#Close and reopen PowerCLI

#Add all required software depots, esxi 5.1, esxi 5.5, and for HA add your local vCenter

Add-EsxSoftwareDepot c:\depot\ESXi-5.1.zip

Add-EsxSoftwareDepot C:\depot\ESXi-5.5.0-20140604001-standard.zip
#Clone the 5.5 profile to make a new one which we can customize
New-EsxImageProfile –CloneProfile ESXi-5.5.0-20140604001-standard –Name PHADREAL_ESXi-5.5.0-20140604001-standard -Vendor PHYSICAL
#The image does not have HA by default add the vCenters HA depot and the local depot
Add-EsxSoftwareDepot Http://PRODVC.MYDOMAIN.local:80/vsphere-HA-depot
Add-EsxSoftwarePackage –ImageProfile PHADREAL_ESXi-5.5.0-20140604001-standard –SoftwarePackage vmware-fdm
Add-EsxSoftwarePackage –ImageProfile PHADREAL_ESXi-5.5.0-20140604001-standard –SoftwarePackage net-r8168
Add-EsxSoftwarePackage –ImageProfile PHADREAL_ESXi-5.5.0-20140604001-standard –SoftwarePackage net-r8169
Export-EsxImageProfile PHADREAL_ESXi-5.5.0-20140604001-standard -ExportToBundle -Filepath 'C:\depot\PHADREAL_ESXi-5.5.0-20140604001-standard.zip' -NoSignatureCheck
#Close and reopen PowerCLI

Connect-VIServer -Server PRODVC.MYDOMAIN.local -User MYDOMAIN\ADMINISTRATOR -Password MYPASSWORD
Add-EsxSoftwareDepot C:\depot\PHADREAL_ESXi-5.5.0-20140604001-standard.zip
#If you have previously configured autodeploy rules, you will need to remove them, as I did below:
Remove-DeployRule -DeployRule InitialBoot -delete
Remove-DeployRule -DeployRule PHYSIMAGE -delete
Remove-DeployRule -DeployRule PHADCLUS -delete
Remove-DeployRule -DeployRule PHADPROFILE -delete
New-DeployRule –Name “PHYSIMAGE” –Item “PHADREAL_ESXi-5.5.0-20140604001-standard” -Pattern "ipv4=192.168.1.16,192.168.1.17"
New-DeployRule –Name “PHADCLUS” –Item “C1” -Pattern "ipv4=192.168.1.16,192.168.1.17"
New-DeployRule –Name “PHADPROFILE” –Item “PHAD” -Pattern "ipv4=192.168.1.16,192.168.1.17"
Add-DeployRule “PHYSIMAGE”
Add-DeployRule “PHADCLUS"
Add-DeployRule “PHADPROFILE”
Test-DeployRuleSetCompliance -VMhost phad.MYDOMAIN.local
Test-DeployRuleSetCompliance -VMhost w81.MYDOMAIN.local
Apply-ESXImageProfile "PHADREAL_ESXi-5.5.0-20140604001-standard" phad.MYDOMAIN.local
Apply-ESXImageProfile "PHADREAL_ESXi-5.5.0-20140604001-standard" w81.MYDOMAIN.local