none
Windows 2019 Hyper-V-VmSwitch Event 113 RRS feed

  • Question

  • Hello

    I have already used VMQ with LBFO on Hyper-V Windows 2012R2 and this hotfix:

    https://support.microsoft.com/en-gb/help/3001783/vmswitch-error-113-event-is-logged-when-you-start-or-live-migrate-virt

    There were no problems with Windows 2016.

    Hyper-V-VmSwitch Event ID: 106
    Available processor sets of the underlying physical NICs belonging to the LBFO team NIC /DEVICE/{B5070B0E-DFF1-42EB-8D72-9D93ECC59F73} (Friendly Name: Microsoft Network Adapter Multiplexor Driver #2) on switch 226F1E40-7DBB-4C62-BB3B-2CF93333FAE5 (Friendly Name: Logical Switch) are not configured correctly. Reason: The processor sets overlap when LBFO is configured with sum-queue mode.

    Solved with this setting:

    Set-NetAdapterRss -Name MGMT-SW01 -BaseProcessorNumber 0 -MaxProcessorNumber 36
    Set-NetAdapterRss -Name MGMT-SW02 -BaseProcessorNumber 37 -MaxProcessorNumber 63
    Set-NetAdapterRss -Name MGMT-SW01 -MaxProcessors 24
    Set-NetAdapterRss -Name MGMT-SW02 -MaxProcessors 24

    Now I have the same message in Windows 2019 again:

    Hyper-V-VmSwitch Event ID: 113
    Failed to allocate VMQ for NIC C3586E18-CE38-4FE1-A5ED-7929D551B151--952909D8-D3A5-47F3-9876-2D72717DB2FE (Friendly Name: TEST1) on switch 226F1E40-7DBB-4C62-BB3B-2CF93333FAE5 (Friendly Name: Logical Switch). Reason - The OID failed. Status = An invalid parameter was passed to a service or function.

    Is there a hotfix for Windows 2019 or a workaround?

    Thanks a lot!

    Thursday, April 4, 2019 8:56 AM

All replies

  • Hello,

    You can view the released update history for the Windows server 2019 by clicking the following link.

    In the KB articles, there is no introduction about this hotfix. However, I would recommend to install the most recent update, and see if it's fixed. 

    https://support.microsoft.com/en-us/help/4490481

    Best regards,

    Andy Liu


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, April 5, 2019 3:09 AM
  • Hello,

    Is there a solution? I have exactly the same error (Event 113)!

    Regards

    Martin

    Wednesday, June 5, 2019 10:08 AM