I have been doing a lot of ESXi 4.1 to 5 upgrades of late and every time I tried using vCenter Update Manager I would get an incompatible driver warning for these 2 ESXi 4.1 driver packages
The vSphere 5 Update Manager release notes mentions this and states that to workaround this simply check the box to remove third-party software that is incompatible. http://www.vmware.com/support/vsphere5/doc/vsphere-update-manager-50-release-notes.html#upgrade
Here is the section from the release notes:
“Compliance status is Incompatible and remediation fails for ESX 4.1 Update 1 hosts when you scan or remediate the hosts against an ESXi 5.0 upgrade baseline
When you perform an upgrade scan of ESX 4.1 Update 1 hosts against an ESXi 5.0 upgrade baseline, the compliance status might be Incompatible. The remediation of ESX 4.1 Update 1 hosts against an ESXi 5.0 upgrade baseline might fail. The scan and remediation problems are caused by third-party drivers in the ESX 4.1 Update 1 installation. After an upgrade scan of hosts, more information about third-party software is provided in the conflict details for the upgrade baseline.
Workaround: Two different types of drivers might cause the problems.
- Async drivers, for example oem-vmware-esx-drivers-scsi-3w-9xxx.
The vendor will release drivers asynchronously for ESXi 5.0, and the drivers will be made available in the VMware patch depot. If you require those drivers, you must download them, use Image Builder CLI to build a custom ESXi image that contains them, and remediate against the custom image. Without the ESXi 5.0 drivers, pertinent hardware devices might stop functioning.
- Deprecated drivers, for example oem-vmware-esx-drivers-net-vxge.
The driver is discontinued in ESXi 5.0 because the pertinent hardware is discontinued. In the Update Manager Remediate wizard, on the ESXi 5.x Upgrade page, click Remove installed third-party software that is incompatible with the upgrade, and continue with the remediation. You should be aware of the functional implications of third-party software removal, because pertinent hardware devices might stop functioning.”
This workaround has not worked for me and I have been force to boot from the ESXi 5 ISO and choose Force Upgrade during setup. This method works but requires more steps and doesn’t allow for streamlined upgrades with VUM.
I imagine that the VMware suggested workaround doesn’t work because those 2 driver packages are part of ESXi 4.1 and not classified as “third-party”
I found another workaround for this that will allow the remediation to complete.
- Place the ESXi host into maintenance mode
- SSH into the ESXi 4.1 host and run this command to get a list of all software packages
- “esxupdate query –a”
- From the list copy the bulletin IDs of the incompatible drivers.
- Run these commands to remove them
- “esxupdate -b ESXi410-201101224-UG remove”
- “esxupdate -b ESXi410-201101223-UG remove”
- Reboot the host
- After reboot scan the host again with VUM and you shouldn’t have any incompatible packages.
- Remediate the host and then go to the next one and do the same.