In vSphere 5.0 and later, the LSI and HP provider VIBs are not included in the default VIBs. Therefore, if you are using an LSI or HP RAID controller card on your host with vSphere 5.0 or later, you will need to install an LSI or HP VIB before the associated RAID storage device will show up in your vCenter Server Inventory.
The cmdlet runs the standard validation tests on the image profile. If validation succeeds, the cmdlet returns a modified, validated image profile. If the VIB that you want to add depends on a different VIB, the cmdlet displays that information and includes the VIB that would resolve the dependency. If the acceptance level of the VIB that you want to add is lower than the image profile acceptance level, an error results. Change the acceptance level of the image profile to add the VIB.
See http://pubs.vmware.com/vsphere-50/topic/com.vmware.vsphere.install.doc_50/GUID-B81FE465-A43B-462D-BBBF-85B27F5BBAE8.html for more information about how to add a VIB to an image profile.
When you install several CIM provider VIBs on an ESXi system, you might find that the providers as a whole exceed the default capacity of the memory resource pool allocated for plug-ins. Therefore, if you experience memory contention after adding more than one CIM plug-in, you may need to adjust the memory pool on your ESXi server.
For more information about Resource Pool Allocation for CIM Plug-ins, see the Tech Note, “Dynamic Resource Pool Allocation for CIM Plug-ins“ on the CIM SMASH/Server Management API documentation page located
here: https://www.vmware.com/support/developer/cim-sdk/index.html.