When the host is in Maintenance Mode, right click the ESXi and select Power > Reboot to reboot the host. To avoid misconfiguration in the vCenter Server Inventory if something goes wrong during the driver removal, enable the option Move powered off and suspended virtual machines to other hosts in the cluster. Right click the host to reboot and select Maintenance Mode > Entrer Maintenance Mode. To complete the driver removal procedure, you need to reboot the host. The net-mst package can be safely removed from the system through the command: Looking at the drivers displayed, Mellanox driver is not in use by any NIC. Now run the following command to check drivers used on your network interfaces: The net-mst is the VIB package containing the Mellox driver. Run the following command to check in which VIB package Mellanox driver resides:

SSH the first host affected by VIBs conflict and enter the correct credentials.

Select any Startup Policy (we just need to access the host temporarily) and click Start to enable SSH. Select SSH from the list and click Options. Click Properties in the top right of the screen to enable SSH. Go to Configuration tab and select Security Profile in the Software section. To discover where this driver is used, we need to SSH the affected hosts and use esxcli commands.ĭisabled by default, the SSH service must be enabled in the ESXi host 5.5 using the vSphere Thin Client. Remove the conflicting VIBs or use Image Builder to create a custom upgrade ISO image that contains the newer versions of the conflicting VIBs, and try to upgrade again. The upgrade contains the following set of conflicting VIBs: When the Scan for Updates procedure is run from the Update Manager tab, processed hosts are reported as Incompatible showing the error: During the Scan for Updates process of ESXi hosts to upgrade from 5.5 to 6.5, VMware Update Manager displays an incompatibility error due to conflicting VIBs using the HPE image.

Vmware image builder