Hyper-V host crashes and has errors when you perform a VM live migration in Windows 8.1 and Windows Server 2012 R2

This article describes an issue that occurs in a Windows 8.1 or Windows Server 2012 R2 Hyper-V host. A hotfix is available to resolve this issue. Before you install this hotfix, check out the Prerequisites section.

Introduction

Consider the following scenario:
  • You have a Windows Server 2012 R2-based computer that is configured for one or more NIC teams by using Windows NIC Teaming (LBFO).
  • You have implemented Windows NIC Teaming (LBFO) in Switch Independent teaming mode by using Hyper-V Port or Dynamic Load Balancing mode. Additionally, you have correctly configured the NICs to use non-overlapping processors. (For more information, see Knowledge Base article 2974384 ).
  • A Hyper-V virtual switch is bound to one of the LBFO teams.
  • You start a virtual machine on the Hyper-V server, or you live migrate a virtual machine from one server to another server.
In this scenario, you experience one or more of the following issues:
  • Issue 1: The following Error 113 event is logged intermittently in the event log:

    Log Name: System
    Source: Microsoft-Windows-Hyper-V-VmSwitch
    Date: <DateTime>
    Event ID: 113
    Task Category: None
    Level: Error
    Keywords:
    User: SYSTEM
    Computer: Server1.contoso.com
    Description:
    Failed to allocate VMQ for NIC EDCED345-4C96-4C75-92A0-0C4FC5688F73--35BEB899-5BE9-4128-900A-6FE0BBFC7B22
    (Friendly Name: Network Adapter) on switch DE4F3664-68D9-4781-825B-882A540FAB08 (Friendly Name: VM Switch).
    Reason - The OID failed. Status = {Operation Failed} The requested operation was unsuccessful.
    Additionally, the Hyper-V VmSwitch may fail to allocate VMQ queues for virtual machines.

    Note In the event description, the Reason text is always "The OID failed." The Status text varies based on the network adapter driver that is being used. Other Status examples include the following:
    • Status = An invalid parameter was passed to a service or function
    • Status = Insufficient system resources exist to complete the API
    • Status = Unknown
    Cause This issue occurs because the VmSwitch assumes that the default processor for VMQ is zero (0) when it performs VMQ allocation. This causes some network adapter drivers to reject the allocation and generate Error 113.

    Fix information After you apply this hotfix, the VmSwitch no longer assumes that the default processor for VMQ is zero (0).

    For more information about this issue, see Knowledge Base article 3001783 .

  • Issue 2: Performance degrades or the system stops responding.

    Cause This issue occurs because LBFO physical resource mapping algorithm overloads the host. This issue can also trigger "MAC flapping."

    Fix information After you apply this hotfix, the rebalancing algorithm is optimized and made more scalable.

  • Issue 3: A STOP 0xD1 error occurs on the host during live migration.

    Cause This issue occurs after LBFO clears its own structures because it assumes that the forward progress of the Object identifier (OID) is guaranteed.

    Fix information After you apply this hotfix, LBFO clears its mappings only if the OID succeeds. For failure scenarios, LBFO passes the OID status back to VmSwitch. VmSwitch receives the failure status and processes it through its own logic.

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows 8.1 or Windows Server 2012 R2.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.
File information

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

See the terminology that Microsoft uses to describe software updates.
Properties

Article ID: 3031598 - Last Review: Jul 24, 2015 - Revision: 1

Windows Server 2012 R2 Datacenter, Windows Server 2012 R2 Essentials, Windows Server 2012 R2 Standard, Windows 8.1 Enterprise, Windows 8.1 Pro, Windows 8.1

Feedback