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 Live Migration fails on Windows Server 2008 R2 with Event IDs 21203 and 21125

Hyper-V Live Migration fails on Windows Server 2008 R2 with Event IDs 21203 and 21125

View products that this article applies to.

Symptoms

When you perform a live migration of a Hyper-V virtual machine on Windows Server 2008 R2, the live migration may fail and the virtual machine will have a status of Online (Migration attempt failed).

On the destination node, the following events will be logged in the Microsoft-Windows-Hyper-V-High-Availability/Admin event log:

Log Name:      Microsoft-Windows-Hyper-V-High-Availability-Admin
Source:        Microsoft-Windows-Hyper-V-High-Availability
Event ID:      21203
Description:
Failed to create virtual network switch port '4825deff-6f69-45fd-92f2-3d344f0b95b2'. (HRESULT 0x80070490)

Log Name:      Microsoft-Windows-Hyper-V-High-Availability-Admin
Source:        Microsoft-Windows-Hyper-V-High-Availability
Event ID:      21125
Description:
Configuration setup for live migration failed on the destination node. Make sure that name of the virtual network is the same on the source and destination nodes, and try the live migration again.

↑ Back to the top

Cause

This issue occurs if the virtual network name is not the same between the source and destination nodes.

↑ Back to the top

Resolution

To resolve this issue, perform the following steps:

1.     Open the Hyper-V Manager console on the source and destination nodes.
2.     Select Virtual Network Manager.
3.     Verify that the virtual network names match between the source and destination nodes.
4.     Click OK to close the Virtual Network Manager window.
5.     Right-click on the virtual machine on the source node and select Settings.
6.     Verify that the virtual machine is configured to use the correct virtual network.
7.     Click OK to close the Virtual Machine Settings window.
8.     Close the Hyper-V Manager console on the source and destination nodes.
9.     Open the Failover Cluster Manager console on the source node.
10.   Expand Services and Applications and then select the Virtual Machine.
11.   In the Actions pane, click More Actions, and then click Refresh virtual machine configuration.
12.   Perform a live migration of the virtual machine to the destination node.

↑ Back to the top

More Information

For more information on Hyper-V, visit the following Microsoft web site: http://technet.microsoft.com/en-us/library/cc753637(WS.10).aspx

↑ Back to the top

Keywords: kbhyperv, kb

↑ Back to the top

Article Info
Article ID : 2475761
Revision : 1
Created on : 1/7/2017
Published on : 12/17/2010
Exists online : False
Views : 382