Windows server 2022 - Hyper-v cluster issue

Nguyen Thanh Hieu 61 Reputation points
2023-06-13T16:14:44.34+00:00

Hi everyone,

We just created one Hyper-v cluster on Windows Server 2022. Everything seem working fine except this issue in event log.

Failed to allocate VMQ for NIC 3D7DD9B2-5DFF-4B17-A8D6-223D39CF8879--10084DE8-60F6-4376-B25F-75F746ECDF09 (Friendly Name: Network Adapter) on switch 29AA61E4-E05E-40EC-904D-1A6F86B8700E (Friendly Name: Production-Switch). Reason - Failed to set the VMQ affinity processor for NIC. Status = {Operation Failed} The requested operation was unsuccessful.

Failed to allocate VMQ for NIC DC4EBFC8-65C2-42B1-986E-885F4630452F--29D67411-B633-4E51-A76E-9BF75A8ED8FA (Friendly Name: Network Adapter) on switch 29AA61E4-E05E-40EC-904D-1A6F86B8700E (Friendly Name: Production-Switch). Reason - The OID failed. Status = An invalid parameter was passed to a service or function.

I already set VMQ for each NICs

Set-NetAdapterVmq -Name NIC1_Production -BaseProcessorNumber 30 -MaxProcessors 8 Set-NetAdapterVmq -Name SLOT6_P1_Production -BaseProcessorNumber 46 -MaxProcessors 8

This is RSS settings:

PS C:\Windows\system32> Get-NetadapterRss | ?{$_.Name -like "*production*"}


Name                                            : NIC1_Production
InterfaceDescription                            : Intel(R) Ethernet 10G 4P X710 SFP+ rNDC
Enabled                                         : True
NumberOfReceiveQueues                           : 8
Profile                                         : Closest
BaseProcessor: [Group:Number]                   : 0:30
MaxProcessor: [Group:Number]                    : 3:38
MaxProcessors                                   : 8
RssProcessorArray: [Group:Number/NUMA Distance] : 0:30/0  0:32/0  0:34/0  0:36/0  0:38/0  3:0/32704  3:2/32704  3:4/32704
                                                  3:6/32704  3:8/32704  3:10/32704  3:12/32704  3:14/32704  3:16/32704  3:18/32704  3:20/32704
                                                  3:22/32704  3:24/32704  3:26/32704  3:28/32704  3:30/32704  3:32/32704  3:34/32704  3:36/32704
                                                  3:38/32704  2:0/32730  2:2/32730  2:4/32730  2:6/32730  2:8/32730  2:10/32730  2:12/32730
                                                  2:14/32730  2:16/32730  2:18/32730  2:20/32730  2:22/32730  2:24/32730  2:26/32730  2:28/32730
                                                  2:30/32730  2:32/32730  2:34/32730  2:36/32730  2:38/32730  1:0/32767  1:2/32767  1:4/32767
                                                  1:6/32767  1:8/32767  1:10/32767  1:12/32767  1:14/32767  1:16/32767  1:18/32767  1:20/32767
                                                  1:22/32767  1:24/32767  1:26/32767  1:28/32767  1:30/32767  1:32/32767  1:34/32767  1:36/32767
                                                  1:38/32767
IndirectionTable: [Group:Number]                :

Name                                            : SLOT6_P1_Production
InterfaceDescription                            : Intel(R) Ethernet Converged Network Adapter X710
Enabled                                         : True
NumberOfReceiveQueues                           : 8
Profile                                         : Closest
BaseProcessor: [Group:Number]                   : 0:46
MaxProcessor: [Group:Number]                    : 3:38
MaxProcessors                                   : 8
RssProcessorArray: [Group:Number/NUMA Distance] : 1:0/0  1:2/0  1:4/0  1:6/0  1:8/0  1:10/0  1:12/0  1:14/0
                                                  1:16/0  1:18/0  1:20/0  1:22/0  1:24/0  1:26/0  1:28/0  1:30/0
                                                  1:32/0  1:34/0  1:36/0  1:38/0  3:0/32577  3:2/32577  3:4/32577  3:6/32577
                                                  3:8/32577  3:10/32577  3:12/32577  3:14/32577  3:16/32577  3:18/32577  3:20/32577  3:22/32577
                                                  3:24/32577  3:26/32577  3:28/32577  3:30/32577  3:32/32577  3:34/32577  3:36/32577  3:38/32577
                                                  2:0/32640  2:2/32640  2:4/32640  2:6/32640  2:8/32640  2:10/32640  2:12/32640  2:14/32640
                                                  2:16/32640  2:18/32640  2:20/32640  2:22/32640  2:24/32640  2:26/32640  2:28/32640  2:30/32640
                                                  2:32/32640  2:34/32640  2:36/32640  2:38/32640
IndirectionTable: [Group:Number]                :

Name                                            : Production-Team
InterfaceDescription                            : Microsoft Network Adapter Multiplexor Driver
Enabled                                         : True
NumberOfReceiveQueues                           : 0
Profile                                         : NUMAStatic
BaseProcessor: [Group:Number]                   : 0:0
MaxProcessor: [Group:Number]                    : 3:38
MaxProcessors                                   : 4
RssProcessorArray: [Group:Number/NUMA Distance] : 0:0/0  0:2/0  0:4/0  0:6/0  0:8/0  0:10/0  0:12/0  0:14/0
                                                  0:16/0  0:18/0  0:20/0  0:22/0  0:24/0  0:26/0  0:28/0  0:30/0
                                                  0:32/0  0:34/0  0:36/0  0:38/0  1:0/0  1:2/0  1:4/0  1:6/0
                                                  1:8/0  1:10/0  1:12/0  1:14/0  1:16/0  1:18/0  1:20/0  1:22/0
                                                  1:24/0  1:26/0  1:28/0  1:30/0  1:32/0  1:34/0  1:36/0  1:38/0
                                                  2:0/0  2:2/0  2:4/0  2:6/0  2:8/0  2:10/0  2:12/0  2:14/0
                                                  2:16/0  2:18/0  2:20/0  2:22/0  2:24/0  2:26/0  2:28/0  2:30/0
                                                  2:32/0  2:34/0  2:36/0  2:38/0  3:0/0  3:2/0  3:4/0  3:6/0
                                                  3:8/0  3:10/0  3:12/0  3:14/0  3:16/0  3:18/0  3:20/0  3:22/0
                                                  3:24/0  3:26/0  3:28/0  3:30/0  3:32/0  3:34/0  3:36/0  3:38/0
IndirectionTable: [Group:Number]                :

Name                                            : vEthernet (Production-Switch)
InterfaceDescription                            : Hyper-V Virtual Ethernet Adapter #2
Enabled                                         : True
NumberOfReceiveQueues                           : 16
Profile                                         : ClosestStatic
BaseProcessor: [Group:Number]                   : 0:0
MaxProcessor: [Group:Number]                    : 0:63
MaxProcessors                                   : 8
RssProcessorArray: [Group:Number/NUMA Distance] : 0:0/0  0:2/0  0:4/0  0:6/0  0:8/0  0:10/0  0:12/0  0:14/0
                                                  0:16/0  0:18/0  0:20/0  0:22/0  0:24/0  0:26/0  0:28/0  0:30/0
                                                  0:32/0  0:34/0  0:36/0  0:38/0
IndirectionTable: [Group:Number]                : 0:30  0:30    0:30    0:32    0:30    0:36    3:4     0:30
                                                  0:36  0:34    0:36    0:38    0:34    3:2     0:30    0:30
                                                  0:30  0:30    0:30    0:32    0:30    0:36    3:4     0:30
                                                  0:36  0:34    0:36    0:38    0:34    3:2     0:30    0:30
                                                  0:30  0:30    0:30    0:32    0:30    0:36    3:4     0:30
                                                  0:36  0:34    0:36    0:38    0:34    3:2     0:30    0:30
                                                  0:30  0:30    0:30    0:32    0:30    0:36    3:4     0:30
                                                  0:36  0:34    0:36    0:38    0:34    3:2     0:30    0:30
                                                  0:30  0:30    0:30    0:32    0:30    0:36    3:4     0:30
                                                  0:36  0:34    0:36    0:38    0:34    3:2     0:30    0:30
                                                  0:30  0:30    0:30    0:32    0:30    0:36    3:4     0:30
                                                  0:36  0:34    0:36    0:38    0:34    3:2     0:30    0:30
                                                  0:30  0:30    0:30    0:32    0:30    0:36    3:4     0:30
                                                  0:36  0:34    0:36    0:38    0:34    3:2     0:30    0:30
                                                  0:30  0:30    0:30    0:32    0:30    0:36    3:4     0:30
                                                  0:36  0:34    0:36    0:38    0:34    3:2     0:30    0:30


Could you please help me solve this issue ? What's wrong with my configuraiton?

Appriciated!

Thanks

Windows for business Windows Client for IT Pros Storage high availability Virtualization and Hyper-V
Windows for business Windows Server Storage high availability Clustering and high availability
Windows for business Windows Server User experience Other
0 comments No comments
{count} votes

Accepted answer
  1. Limitless Technology 44,751 Reputation points
    2023-06-14T08:27:17.73+00:00

    Hello Nguyen,

    Thank you for your question and for reaching out with your question today.

    The error message you provided suggests that there is an issue with allocating Virtual Machine Queues (VMQ) for the network adapters on your Hyper-V cluster. VMQ is a feature that allows network traffic to be distributed across multiple processors, improving network performance.

    Based on the information you provided, it seems that you have already configured VMQ settings for your network adapters using the Set-NetAdapterVmq cmdlet. However, the error indicates that the requested operation to set the VMQ affinity processor for the NIC failed.

    To troubleshoot this issue, you can try the following steps:

    1. Verify NIC compatibility: Ensure that the network adapters used in your Hyper-V cluster support VMQ. Check the hardware compatibility list (HCL) for Windows Server 2022 and verify that the NICs are listed as compatible.
    2. Update NIC drivers: Make sure you have the latest drivers installed for your network adapters. Check the manufacturer's website for updated drivers specifically designed for Windows Server 2022.
    3. Check VMQ support: Confirm that VMQ is enabled in the firmware settings (BIOS/UEFI) of the physical servers hosting the Hyper-V cluster. Refer to the server manufacturer's documentation for instructions on enabling VMQ.
    4. Verify processor compatibility: Ensure that the processors used in your servers support VMQ and have the necessary virtualization extensions enabled (e.g., Intel VT-x or AMD-V). Check the processor specifications and consult the server manufacturer's documentation for details.
    5. Adjust VMQ settings: Try adjusting the VMQ settings for your network adapters. You can experiment with different BaseProcessorNumber and MaxProcessors values to find a configuration that works. For example, you can set the BaseProcessorNumber to 0 and MaxProcessors to 4 for each adapter, and then gradually increase the MaxProcessors value if needed.
    6. Validate Hyper-V configuration: Run the "Validate a Configuration" wizard in the Failover Cluster Manager to check for any misconfigurations or issues related to the Hyper-V cluster. The wizard can help identify potential problems and provide recommendations for resolution.

    I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.

    If the reply was helpful, please don’t forget to upvote or accept as answer.

    Best regards.


1 additional answer

Sort by: Most helpful
  1. Nguyen Thanh Hieu 61 Reputation points
    2023-06-22T04:55:12.39+00:00

    After spent some days to find solutions, still can't fixed issue event tried with many settings.

    Finally, I switch to use SET (Switch Embended Team) instead legacy Teaming technique.Hope it help you guys who facing same issue.

    Br,

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.