Unable to queue the task to helper world (No free handles) error while NIC stuck in link down state.

Products

• VMware vSphere ESXi

Issue/Introduction

• NIC status showing as Down in the vSphere Client.
• Alarm may show network redundancy lost.
• Qedentv driver in use.
• May also correlate to a recent physical hardware change on the NIC or supporting infrastructure
• Vmkernel.log shows repeating pattern of the below multiple times per second, never completing link state negotiation:
  
  2026-05-01T09:16:41.097Z In(182) vmkernel: cpu47:2098037)[qedentv_schedule_work:7296(vmnic0)]Unable to queue the task to helper world.(No free handles)
2026-05-01T09:16:41.214Z In(182) vmkernel: cpu47:2098037)qedentv: OSAL_LINK_UPDATE:1329: NIC Link is up. vmnicX
2026-05-01T09:16:41.225Z In(182) vmkernel: cpu47:2098037)qedentv: OSAL_LINK_UPDATE:1318: NIC Link is down. vmnicX

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

 

Environment

• VMware ESXi

Cause

This issue is caused by rapid link flapping which exhausts the helper world handles available to the qedentv driver. Once these handles are exhausted, the driver cannot process the Link State changes, leaving the interface in a down state.

Resolution

To restore connectivity, you must manually toggle the NIC state:

1. Log in to the ESXi host via SSH or Console.
2. Bring the affected NIC down by running the following command:
   • esxcli network nic down -n vmnicX
     (Replace vmnicX with your specific NIC identifier)
3. Bring the NIC back up:
   • esxcli network nic up -n vmnicX
4. Verify the link status is now stable:
   • esxcli network nic list

If a manual reset of the NIC does not bring it back to a healthy state it is likely required to engage the hardware vendor for further assistance.

Additional Information

Subscribe to this knowledge article to get updates on this issue.