VMware ESX 6.5 – How to Resolve Driver Incompatibility Issues in vSphere Update Manager (VUM) When Updating Host Drives

Blog Written by Jason White
Champion Solutions Group Professional Services Engineer

After you assign a driver baseline to a host and scan for updates you will get a Compliance status of Incompatible. This is due to older drivers that are still on the host. You will need to remove the older drivers in order to install the new driver.

This is an example of an incompatible QLogic driver.

To get a list of the incompatible drivers highlight the baseline you are working with.

In the bottom pane you will see driver info with a status of conflict

Click on Show Details

This will open a second window with the info needed.

Under Compliance Status you will see the existing drivers that are conflicting with the new driver you are trying to install.

Document the drivers with the conflict.
You will need this information later to remove the conflicted drivers.

To remove the old driver, you will need to do this through CLI using SSH

You will need to ensure that SSH is enabled on the host

Using your choice of SSH client login to the host using root

You will need to verify that the device you are trying to upgrade the driver for is not using the driver that is listed as the conflict. In our example we are updating the Qlogic 25G NIC’s.

Run this command to get the list of NIC’s on the host.

# esxcli network nic list


In our example we are going to look at vmnic2 since it is one of the Qlogic 25G NIC’s.
Run this command to get detailed info on vmnic2
# esxcli network nic get -n vmnic2

Advertised Auto Negotiation: true
Advertised Link Modes: 10000None/Full, 25000None/Full, 40000None/Full, 50000None/Full, 100000None/Full, Auto
Auto Negotiation: false
Cable Type: DA
Current Message Level:
Driver Info:
Bus Info: 0000:0d:00:0
Driver: qedentv
Firmware Version: mfw storm
Link Detected: false
Link Status: Down
Name: vmnic2
PHYAddress: 0
Pause Autonegotiate: true
Pause RX: true
Pause TX: true
Supported Ports: DA
Supports Auto Negotiation: true
Supports Pause: true
Supports Wakeon: false
Transceiver: external
Virtual Address: 00:50:56:53:79:d8
Wakeon: None

In the output above you see the NIC is loaded with version

Now you need to look for the QLogic drivers that are loaded on this host.

Run the following command to get this info.
# esxcli software vib list |grep qe

qedentv      QLC      VMwareCertified 2019-02-08
qedrntv   QLC       VMwareCertified 2019-02-08
scsi-qedil    QLC       VMwareCertified 2019-02-08

In this instance you will see there are similar Qlogic drivers and the scsi driver listed as one of the conflicts. The one with the conflict is and the driver that is loaded is
Now we need remove the conflicted qedrntv and scsi-qedil drivers.

Run the following command to get the driver info for the conflicted driver.
# esxcli software vib remove –vibname qedrntv

Once the driver is removed you will get the following results.

Removal Result
Message: Operation finished successfully.
Reboot Required: false
VIBs Installed:
VIBs Removed: QLC_bootbank_qedrntv_3.
VIBs Skipped:

Since there is no reboot required you can continue to remove the second conflicted driver.

# esxcli software vib remove –vibname scsi-qedil

Once the driver is removed you will get the following results.
Removal Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed:
VIBs Removed: QLC_bootbank_scsi-qedil_1.0.19.0-1OEM.600.0.0.2494585
VIBs Skipped:

In this instance a reboot is required.
Issue the reboot command
Once the host has rebooted you can run the software list command to verify that both the drivers have been removed.
Log back into the host once it has rebooted.
Run the following command to verify the drivers have been removed
# esxcli software vib list |grep qe
qedentv       QLC       VMwareCertified 2019-02-08

You can see that only the running version of the driver is installed.
Go back to vCenter VUM and run another scan
You will now see that the baseline went from incompatible to Non-Compliant


From this point you can do a Remediate on the baseline and install the new driver.
Once the driver has been installed and the server reboots you can run another scan on the host and your driver should now be in a compliant state.


Data Protection and Disaster Recovery Combine to Meet Banking Needs


Sorry, the comment form is closed at this time.