Hyper-V 2025 + SET Team: Intel E610-XT4 limited to 4 Queue Pairs per vPort (Event ID 280)

Question

Hi all,

We’re facing a consistent issue on a Windows Server 2025 host using Hyper-V with Switch Embedded Teaming (SET) and Intel E610-XT4 for OCP 3.0 NICs (8 total). Firmware is NVM 1.33 (1.21), and the driver is from Intel Ethernet Adapter Complete Driver Pack 30.1.1.

Problem:

As soon as VMs are created, Event ID 280 appears in the Hyper-V-VmSwitch log:

“VMS Utilization Plan Vport QueuePairs adjusted from requested number (16) to actual (4).

The number requested exceeds the maximum QPs per VPort supported by physical NIC.”

This occurs regardless of VM count or host load. The E610-XT4 cards report:

• VMQ enabled
• 16 RSS queues
• SR-IOV supported (62 VFs)

But Hyper-V always limits IOVQueuePairs to 4 per vPort, unless we force it to a lower value.

We also see Event ID 285 frequently:

“V-Switch operation OID_GEN_STATISTICS took too long to complete. Operation Type: OID HOST VNIC.”

Questions:

1. Is this 4-QP limitation per vPort expected behavior in Hyper-V 2025 with E610-XT4?
2. Is the limitation enforced by the Intel driver (NDIS layer) or by Hyper-V’s vSwitch?
3. Are there any planned fixes, updated drivers, or registry overrides?

Any insight would be very helpful. Thank you!

Best regards,

Answer 1

Dear Team,

No, this is not expected behavior and points to a compatibility issue. It's a bottleneck that prevents you from using the full capabilities of your hardware.

---

What is causing the limitation?

The limitation is almost certainly being enforced by the Intel network driver, not by Hyper-V itself. The Hyper-V virtual switch requests 16 queue pairs, but the driver reports back that it can only support 4 per virtual port when configured with Switch Embedded Teaming (SET).

The related Event ID 285 (OID_GEN_STATISTICS took too long) further suggests the driver is struggling to communicate efficiently with the Hyper-V stack, reinforcing the likelihood of a driver or firmware problem.

---

How can you fix it?

There is no single guaranteed fix, as this is likely a bug that needs to be addressed by the vendor. However, your best course of action is:

Update Drivers & Firmware: Aggressively check for the very latest Intel Ethernet Adapter driver pack and NVM firmware for the E610-XT4. Release notes for new versions are your best friend here; look for mentions of Hyper-V, SET, or VMQ fixes.

Contact Vendor Support: Open a support ticket with both Microsoft and Intel. This is a specific, high-level technical issue, and they are the only ones who can provide a definitive fix through updated software.

Avoid Registry Hacks: Do not attempt to override this with registry changes unless explicitly instructed by vendor support, as it can lead to system instability.

Answer 2

Yes, we have already updated both the driver and firmware to the latest versions from Intel’s official Ethernet Adapter Complete Driver Pack 30.1.1. The current NVM firmware is version 1.33 (1.21), and all 8 E610-XT4 adapters are reporting VMQ and RSS correctly.

We had posted this issue in the Intel Community forum here: https://community.intel.com/t5/Ethernet-Products/E610-XT4-Hyper-V-2025-Queue-Pairs-limited-to-4-per-vPort-Event/m-p/1700370

Unfortunately, there has been no response from Intel so far. We will now open a direct support ticket with Intel as you suggest.

Thanks again for confirming that this is not expected behavior from the Hyper-V side.