Hyper-V live migration failed with ID 20201, 20126, 20134

[guest]

Situation: when attempting to run live migration on Microsoft failover cluster, it failed with these event logs:
Log Name: Microsoft-Windows-Hyper-V-High-Availability-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 5/17/2012 11:54:36 AM
Event ID: 20201
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: HPV-DELL04
Description:
The Virtual Machine Management Service failed to restart the live migration connection listener thread: The requested address is not valid in its context. (0x80072741).

Log Name: Microsoft-Windows-Hyper-V-High-Availability-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 5/17/2012 11:54:36 AM
Event ID: 20126
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: HPV-DELL04
Description:
The Virtual Machine Management Service failed to queue the migration request.

Log Name: Microsoft-Windows-Hyper-V-High-Availability-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 5/17/2012 11:54:36 AM
Event ID: 20134
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: HPV-DELL04
Description:
Failed to migrate a virtual machine. (Virtual Machine ID 0471150B-DC5F-4077-9F86-411B0CB26D6B)

Log Name: Microsoft-Windows-Hyper-V-High-Availability-Admin
Source: Microsoft-Windows-Hyper-V-High-Availability
Date: 5/17/2012 11:54:48 AM
Event ID: 21114
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: HPV-DELL04
Description:
'Virtual Machine CBGMAC' live migration did not succeed at the destination.

Log Name: System
Source: Microsoft-Windows-Hyper-V-High-Availability
Date: 5/17/2012 11:54:48 AM
Event ID: 21502
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: HPV-DELL04
Description:
'Virtual Machine CBGMAC' live migration did not succeed at the destination.

The Virtual Machine Management Service failed to queue the migration request.

Troubleshooting: make sure you have a good network connection. Or Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.