How to fix Windows Server 2022 event ID 252/253 on a Hyper-V failover cluster?

Question

We have a Hyper-V failover cluster with two nodes running Windows Server 2022. When the Hyper-V Host servers raised warning event log ID 252, it causes communication between VMs or clients with VMs to become unstable. Most of the time, this is related to CPU 0 and 40. We have already updated the network driver and firmware following Dell's recommendations, but the issue persists. Has anyone encountered this issue before? If so, could you please share your solution? Thank you.

Here is the relevant warning message:

Memory allocated for packets in a vRss queue (on CPU 40) on switch 505DDAEC-6F21-441D-9E2F-22329B3F7DC3 (Friendly Name: Production-Switch) due to low resource on the physical NIC has increased to 16MB. Packets will be dropped once queue size reaches 16MB.

Answer 1

Hey,

You should check configuration of network adapters configured on the hosts. There are adapters, which set receive buffers value to low to conserve allocated memory from the host. Might help:
https://learn.microsoft.com/en-us/archive/msdn-technet-forums/ef5a9d33-a50a-47b0-aeeb-1f21422ba992

Might also help: https://learn.microsoft.com/en-us/answers/questions/108148/hyper-v-cluster-issues-event-id-252-10400

In addition, if you need HA shared storage for your cluster, you can consider using StarWind VSAN as an option. https://www.starwindsoftware.com/starwind-virtual-san

Cheers,

Alex Bykovskyi

StarWind Software

Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.