Highlighted
Contributor
Contributor

Broadcom Driver VIB Injection Fails

Jump to solution

I am having a problem injecting the new Broadcom NetXtreme II vib (BCM-NetXtremeII-5.0-offline_bundle-940344.zip) into a custom ISO using VMware's Image Builder. I am hoping that someone here may be able to help me figure out why the driver injection fails. During the actual injection, I get the following error within PowerCLI.

Add VIB net-cnic 1.74.04.v50.1-1OEM.500.0.0.472560Add-EsxSoftwarePackage :
VIB VMware_bootbank_scsi-bnx2i_1.9.1d.v50.1-5vmw.510.0.0.799733
requires com.broadcom.cnic-9.2.1.0, but the requirement cannot be satisfied
within the ImageProfile. However, additional VIB(s)
VMware_bootbank_net-cnic_1.10.2j.v50.7-3vmw.510.0.0.799733
from depot can satisfy this requirement.
At C:\esxi\customizer.ps1:65 char:25
+         Add-EsxSoftwarePackage <<<<  -SoftwarePackage $vib -ImageProfile
$MyProfile | Out-Null
    + CategoryInfo          : InvalidData: (VMware.ImageBuilder.Types.
ImageProfile:ImageProfile) [Add-EsxSoftwarePackage], Exception
    + FullyQualifiedErrorId : EsxImageProfileValidationError,VMware.ImageBuilder.
Commands.AddProfilePackage
Add-EsxSoftwarePackage : VIB
Broadcom_bootbank_net-cnic_1.74.04.v50.1-1OEM.500.0.0.472560
requires com.broadcom.cnic_register-9.2.0.0, but the requirement cannot be
satisfied within the ImageProfile. However, additional VIB(s)
Broadcom_bootbank_misc-cnic-register_1.72.1.v50.2-1OEM.500.0.0.472560,
VMware_bootbank_misc-cnic-register_1.1-1vmw.500.0.0.469512 from depot
can satisfy this requirement.
At C:\esxi\customizer.ps1:65 char:25
+         Add-EsxSoftwarePackage <<<<  -SoftwarePackage $vib -ImageProfile
$MyProfile | Out-Null
    + CategoryInfo          : InvalidData: (VMware.ImageBuilder.Types.
ImageProfile:ImageProfile) [Add-EsxSoftwarePackage], Exception
    + FullyQualifiedErrorId : EsxImageProfileValidationError,VMware.
ImageBuilder.Commands.AddProfilePackage

I am using Andreas Peetz (ESXi-Customizer@v-front.de) script to build the custom ISO, but I get the same error when I manually run the commands individually (Add-EsxSoftwarePackage -SoftwarePackage "C:\repository\BCM-NetXtremeII-5.0-offline_bundle-940344.zip" -ImageProfile $MyProfile).

Apparently, the VIB has a dependency (com.broadcom.cnic-9.2.1.0) that doesn't seem to exist. When I checked out the XML file for the Broadcom vib, and for VMware's Base Image, they both have the same dependency.

The base image (ESXi-5.1.0-20121204001-standard) will not install Broadcom Drivers for the built-in BCM57800 CNA in a Dell PowerEdge R620, and the custom image won't take the Broadcom Drivers VIB due to the dependency issue.

Has anyone else seen this? If so, how did you fix it?

I've attached a copy of the script I use.

0 Kudos
1 Solution

Accepted Solutions
Highlighted
User Moderator
User Moderator

Please use the latest version of the ESXi-Customizer-PS script from http://esxi-customizer.googlecode.com.

It uses -force to ignore forward looking dependencies and should fix your issue.

- Andreas

Twitter: @VFrontDe, @ESXiPatches | https://esxi-patches.v-front.de | https://vibsdepot.v-front.de

View solution in original post

0 Kudos
6 Replies
Highlighted
Expert
Expert

Have you tried -Force parameter to Add-EsxSoftwarePackage ?

--- @blog https://grzegorzkulikowski.info
0 Kudos
Highlighted
User Moderator
User Moderator

Please use the latest version of the ESXi-Customizer-PS script from http://esxi-customizer.googlecode.com.

It uses -force to ignore forward looking dependencies and should fix your issue.

- Andreas

Twitter: @VFrontDe, @ESXiPatches | https://esxi-patches.v-front.de | https://vibsdepot.v-front.de

View solution in original post

0 Kudos
Highlighted
Contributor
Contributor

The "-force" switch worked without a hitch. I appreciate your help.

0 Kudos
Highlighted
Enthusiast
Enthusiast

If you put all the VIB-Names into one command separated with comma, then it's working fine without the -force switch.

Add-EsxSoftwarePackage -ImageProfile <Profile> -SoftwarePackage misc-cnic-register,net-cnic,net-bnx2x,scsi-bnx2i,net-bnx2

For me it worked this way. If I try to import one by one, then I receive the same dependency error.

0 Kudos
Highlighted
Contributor
Contributor

Yes, you are right, if one adds the drivers in just one line, it works just fine... Thanks a lot!

0 Kudos
Highlighted
Enthusiast
Enthusiast

-force worked for me also.

Thanks!

0 Kudos