Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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

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

View products that this article applies to.

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.

↑ Back to the top

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.

↑ Back to the top

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:
http://support.microsoft.com/contactus/?ws=support
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
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 8.1 and Windows Server 2012 R2 file information and notes

Important Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1/Windows Server 2012 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    VersionProductMilestoneService branch
    6.3.960 0.17 xxxWindows RT 8.1, Windows 8.1, and Windows Server 2012 R2RTMGDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 8.1
File nameFile versionFile sizeDateTimePlatform
Msft_netlbfoteam.cdxmlNot applicable7,06918-Jun-201312:26Not applicable
Msft_netlbfoteam.format.ps1xmlNot applicable2,97318-Jun-201312:26Not applicable
Msft_netlbfoteammember.cdxmlNot applicable5,76418-Jun-201312:26Not applicable
Msft_netlbfoteammember.format.ps1xmlNot applicable4,78918-Jun-201312:26Not applicable
Msft_netlbfoteamnic.cdxmlNot applicable4,82418-Jun-201312:26Not applicable
Msft_netlbfoteamnic.format.ps1xmlNot applicable4,72018-Jun-201312:26Not applicable
Msft_netswitchteam.cdxmlNot applicable5,83418-Jun-201312:26Not applicable
Msft_netswitchteam.format.ps1xmlNot applicable2,42818-Jun-201312:26Not applicable
Msft_netswitchteammember.cdxmlNot applicable1,23418-Jun-201312:26Not applicable
Msft_netswitchteammember.format.ps1xmlNot applicable3,38018-Jun-201312:26Not applicable
Msnetimplatform.mofNot applicable43,63821-Aug-201323:45Not applicable
Ndisimplatcim.dll6.3.9600.17714156,67226-Feb-201504:04x86
Ndisimplatform.dll6.3.9600.1741598,30429-Oct-201401:45x86
Ndisimplatform.sys6.3.9600.17714109,56826-Feb-201504:20x86
Netlbfo.psd1Not applicable1,07418-Jun-201312:26Not applicable
Netlbfo.types.ps1xmlNot applicable8,54718-Jun-201312:26Not applicable
Netswitchteam.mofNot applicable28,33821-Aug-201323:45Not applicable
Netswitchteam.psd1Not applicable1,05618-Jun-201312:26Not applicable
Netswitchteamcim.dll6.3.9600.17415110,08029-Oct-201401:45x86
For all supported x64-based versions of Windows 8.1 and Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Vmsif.dll6.3.9600.1739665,02408-Oct-201405:53x64
Vmsnetsetupplugin.dll6.3.9600.1739633,79208-Oct-201406:07x64
Vmswitch.sys6.3.9600.17714689,15226-Feb-201505:00x64
Vmsif.dll6.3.9600.1739665,02408-Oct-201405:53x64
Vmsntfy.dll6.3.9600.1739691,64808-Oct-201406:54x64
Vmswitch.sys6.3.9600.17714689,15226-Feb-201505:00x64
Msft_netlbfoteam.cdxmlNot applicable7,06918-Jun-201314:54Not applicable
Msft_netlbfoteam.format.ps1xmlNot applicable2,97318-Jun-201314:54Not applicable
Msft_netlbfoteammember.cdxmlNot applicable5,76418-Jun-201314:54Not applicable
Msft_netlbfoteammember.format.ps1xmlNot applicable4,78918-Jun-201314:54Not applicable
Msft_netlbfoteamnic.cdxmlNot applicable4,82418-Jun-201314:54Not applicable
Msft_netlbfoteamnic.format.ps1xmlNot applicable4,72018-Jun-201314:54Not applicable
Msft_netswitchteam.cdxmlNot applicable5,83418-Jun-201314:53Not applicable
Msft_netswitchteam.format.ps1xmlNot applicable2,42818-Jun-201314:53Not applicable
Msft_netswitchteammember.cdxmlNot applicable1,23418-Jun-201314:53Not applicable
Msft_netswitchteammember.format.ps1xmlNot applicable3,38018-Jun-201314:53Not applicable
Msnetimplatform.mofNot applicable43,63822-Aug-201306:50Not applicable
Ndisimplatcim.dll6.3.9600.17714202,75226-Feb-201504:41x64
Ndisimplatform.dll6.3.9600.17415119,80829-Oct-201402:26x64
Ndisimplatform.sys6.3.9600.17714126,46426-Feb-201505:01x64
Netlbfo.psd1Not applicable1,07418-Jun-201314:54Not applicable
Netlbfo.types.ps1xmlNot applicable8,54718-Jun-201314:54Not applicable
Netswitchteam.mofNot applicable28,33822-Aug-201306:50Not applicable
Netswitchteam.psd1Not applicable1,05618-Jun-201314:53Not applicable
Netswitchteamcim.dll6.3.9600.17415143,36029-Oct-201402:26x64
Mslbfoprovider.sys6.3.9600.17714117,24826-Feb-201505:02x64
Vmsif.dll6.3.9600.1739665,02408-Oct-201405:53x64
Vmsntfy.dll6.3.9600.1739691,64808-Oct-201406:54x64
Vmswitch.sys6.3.9600.17714689,15226-Feb-201505:00x64
Vmsif.dll6.3.9600.1739665,02408-Oct-201405:53x64
Vmsntfy.dll6.3.9600.1739691,64808-Oct-201406:54x64
Vmswitch.sys6.3.9600.17714689,15226-Feb-201505:00x64
Msft_netlbfoteam.cdxmlNot applicable7,06918-Jun-201312:26Not applicable
Msft_netlbfoteam.format.ps1xmlNot applicable2,97318-Jun-201312:26Not applicable
Msft_netlbfoteammember.cdxmlNot applicable5,76418-Jun-201312:26Not applicable
Msft_netlbfoteammember.format.ps1xmlNot applicable4,78918-Jun-201312:26Not applicable
Msft_netlbfoteamnic.cdxmlNot applicable4,82418-Jun-201312:26Not applicable
Msft_netlbfoteamnic.format.ps1xmlNot applicable4,72018-Jun-201312:26Not applicable
Msft_netswitchteam.cdxmlNot applicable5,83418-Jun-201312:26Not applicable
Msft_netswitchteam.format.ps1xmlNot applicable2,42818-Jun-201312:26Not applicable
Msft_netswitchteammember.cdxmlNot applicable1,23418-Jun-201312:26Not applicable
Msft_netswitchteammember.format.ps1xmlNot applicable3,38018-Jun-201312:26Not applicable
Netlbfo.psd1Not applicable1,07418-Jun-201312:26Not applicable
Netlbfo.types.ps1xmlNot applicable8,54718-Jun-201312:26Not applicable
Netswitchteam.psd1Not applicable1,05618-Jun-201312:26Not applicable
For all supported Windows RT 8.1
File nameFile versionFile sizeDateTimePlatform
Msft_netlbfoteam.cdxmlNot applicable7,06918-Jun-201314:56Not applicable
Msft_netlbfoteam.format.ps1xmlNot applicable2,97318-Jun-201314:56Not applicable
Msft_netlbfoteammember.cdxmlNot applicable5,76418-Jun-201314:56Not applicable
Msft_netlbfoteammember.format.ps1xmlNot applicable4,78918-Jun-201314:56Not applicable
Msft_netlbfoteamnic.cdxmlNot applicable4,82418-Jun-201314:56Not applicable
Msft_netlbfoteamnic.format.ps1xmlNot applicable4,72018-Jun-201314:56Not applicable
Msft_netswitchteam.cdxmlNot applicable5,83418-Jun-201314:56Not applicable
Msft_netswitchteam.format.ps1xmlNot applicable2,42818-Jun-201314:56Not applicable
Msft_netswitchteammember.cdxmlNot applicable1,23418-Jun-201314:56Not applicable
Msft_netswitchteammember.format.ps1xmlNot applicable3,38018-Jun-201314:56Not applicable
Msnetimplatform.mofNot applicable43,63821-Aug-201323:38Not applicable
Ndisimplatcim.dll6.3.9600.17714141,82426-Feb-201503:33Not applicable
Ndisimplatform.dll6.3.9600.1771494,20826-Feb-201503:33Not applicable
Ndisimplatform.sys6.3.9600.1771499,84026-Feb-201503:44Not applicable
Netlbfo.psd1Not applicable1,07418-Jun-201314:56Not applicable
Netlbfo.types.ps1xmlNot applicable8,54718-Jun-201314:56Not applicable
Netswitchteam.mofNot applicable28,33821-Aug-201323:38Not applicable
Netswitchteam.psd1Not applicable1,05618-Jun-201314:56Not applicable
Netswitchteamcim.dll6.3.9600.16384103,93622-Aug-201302:57Not applicable

Additional file information

Additional file information for Windows 8.1 and Windows Server 2012 R2
Additional files for all supported x86-based versions of Windows 8.1
File propertyValue
File nameX86_e04ad3a3e8304f16cba023f89e067096_31bf3856ad364e35_6.3.9600.17714_none_81dec95afd1f5b18.manifest
File versionNot applicable
File size703
Date (UTC)26-Feb-2015
Time (UTC)12:49
File nameX86_microsoft-windows-ndis-implatform_31bf3856ad364e35_6.3.9600.17714_none_ead692555f3fe11a.manifest
File versionNot applicable
File size48,030
Date (UTC)26-Feb-2015
Time (UTC)12:53
Additional files for all supported x64-based versions of Windows 8.1 and Windows Server 2012 R2
File propertyValue
File nameAmd64_8d2b32bffb793fef0ccfec7149515ce2_31bf3856ad364e35_6.3.9600.17714_none_fa040693f8245dae.manifest
File versionNot applicable
File size708
Date (UTC)26-Feb-2015
Time (UTC)12:49
File nameAmd64_903502cbdb33d0857bb92ff39e542d3d_31bf3856ad364e35_6.3.9600.17714_none_b0a79eea08ee940f.manifest
File versionNot applicable
File size701
Date (UTC)26-Feb-2015
Time (UTC)12:49
File nameAmd64_93ee7a0aed9826f3b72b577501886d87_31bf3856ad364e35_6.3.9600.17714_none_06e59fc97f759bb8.manifest
File versionNot applicable
File size725
Date (UTC)26-Feb-2015
Time (UTC)12:49
File nameAmd64_c595584f86598a95cab06ca752e8eca3_31bf3856ad364e35_6.3.9600.17714_none_64b052be2676cd7e.manifest
File versionNot applicable
File size707
Date (UTC)26-Feb-2015
Time (UTC)12:49
File nameAmd64_efa8c26a24c0ae028abab425c530c244_31bf3856ad364e35_6.3.9600.17714_none_a2e26f630d2dc92b.manifest
File versionNot applicable
File size707
Date (UTC)26-Feb-2015
Time (UTC)12:49
File nameAmd64_microsoft-hyper-v-d..ch-coresystem-state_31bf3856ad364e35_6.3.9600.17714_none_e89fc26043576c5a.manifest
File versionNot applicable
File size10,027
Date (UTC)26-Feb-2015
Time (UTC)12:55
File nameAmd64_microsoft-hyper-v-drivers-vmswitch_31bf3856ad364e35_6.3.9600.17714_none_5a1539d253db398b.manifest
File versionNot applicable
File size7,613
Date (UTC)26-Feb-2015
Time (UTC)12:55
File nameAmd64_microsoft-windows-ndis-implatform_31bf3856ad364e35_6.3.9600.17714_none_46f52dd9179d5250.manifest
File versionNot applicable
File size48,034
Date (UTC)26-Feb-2015
Time (UTC)12:55
File nameAmd64_microsoft-windows-ndis-lbfo_31bf3856ad364e35_6.3.9600.17714_none_026e00f3ea8f2712.manifest
File versionNot applicable
File size21,621
Date (UTC)26-Feb-2015
Time (UTC)07:25
File nameAmd64_wvms_pp.inf_31bf3856ad364e35_6.3.9600.17714_none_53ef93acc520b27f.manifest
File versionNot applicable
File size3,379
Date (UTC)26-Feb-2015
Time (UTC)12:55
File nameAmd64_wvms_pp_coresys.inf_31bf3856ad364e35_6.3.9600.17714_none_626da6ef600fc2ae.manifest
File versionNot applicable
File size3,411
Date (UTC)26-Feb-2015
Time (UTC)12:55
File nameWow64_microsoft-windows-ndis-implatform_31bf3856ad364e35_6.3.9600.17714_none_5149d82b4bfe144b.manifest
File versionNot applicable
File size20,681
Date (UTC)26-Feb-2015
Time (UTC)05:26
Additional files for all supported Windows RT 8.1
File propertyValue
File nameArm_061f95770322a68617361b37d4eb19cc_31bf3856ad364e35_6.3.9600.17714_none_bdcdf2e07becbdc5.manifest
File versionNot applicable
File size703
Date (UTC)26-Feb-2015
Time (UTC)12:49
File nameArm_microsoft-windows-ndis-implatform_31bf3856ad364e35_6.3.9600.17714_none_ead904ad5f3cffe0.manifest
File versionNot applicable
File size48,030
Date (UTC)26-Feb-2015
Time (UTC)12:49

↑ Back to the top

Status

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

↑ Back to the top

References

See the terminology that Microsoft uses to describe software updates.

↑ Back to the top

Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 3031598
Revision : 1
Created on : 1/7/2017
Published on : 7/24/2015
Exists online : False
Views : 308