Hyper-V-VMMS errors for a migration that doesn't exist

Christopher Boyd 1 Reputation point
2024-05-03T17:44:55.8433333+00:00

For the last month I've been getting errors referring to a request for a virtual machine migration from one of my Domain controllers. Makes no sense. Every 6 hours on the dot I get the following errors in sequence. These started occuring after a bunch of patches were applied. The client address 10.x.x.x is a domain controller on the same network.

The Virtual Machine Management Service blocked a connection request for a Virtual Machine migration from client address '10.x.x.x': %%2147778645 (0x80048055) Event ID 20400

Received invalid or corrupted data for a Virtual Machine migration Event ID 22042

Failed to receive data for a Virtual Machine migration: The data is invalid. (0x8007000D). Event ID 22040

Corresponding errors occur in the Hyper-V-VMMS Operational log :

onecore\vm\common\migration\vmmigrationtcptransport.cpp(2257)\vmms.exe!00007FF635EA597A: (caller: 00007FF635EA5AEB) Exception(2537) tid(10d4) 80072746 An existing connection was forcibly closed by the remote host. Event ID 1106

onecore\vm\common\migration\vmmigrationtcptransport.cpp(2317)\vmms.exe!00007FF635EA5A6A: (caller: 00007FF635EA5AEB) ReturnHr(308) tid(10d4) 80072746 An existing connection was forcibly closed by the remote host. Msg:[onecore\vm\common\migration\vmmigrationtcptransport.cpp(2257)\vmms.exe!00007FF635EA597A: (caller: 00007FF635EA5AEB) Exception(2537) tid(10d4) 80072746 An existing connection was forcibly closed by the remote host. Event ID 1106

vm\service\migration\vmmsmigrationconnection.cpp(342)\vmms.exe!00007FF635B44610: (caller: 00007FF635B231F1) Exception(2539) tid(10d4) 80048055 Event ID 1106

Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,735 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Ian Xue 37,621 Reputation points Microsoft Vendor
    2024-05-07T05:45:46.1866667+00:00

    Hi Christopher,

    Hope you're doing well.

    1. Could you provide a screenshot of the error message or screenshots? Are the virtual machines stored in Cluster Shared Volumes (CSV) within the cluster?
    2. If a new virtual machine is created in "Hyper-V Manager" with its path on a local disk (not in CSV), can you right-click on the virtual machine in "Hyper-V Manager" and use the "move" feature to migrate it to another node?
    3. Please provide us the following information and upload them to our workspace:

    (1) Open "Hyper-V Manager", right-click on the virtual machine experiencing real-time issues, click "Settings", "Processor"--"Compatibility". Check it.

    (2) Open PowerShell as an administrator and run the following command and send us the screenshots:

    Compare-VM -Name vmname -DestinationHost nodename

    (Compare-VM -Name vmname -DestinationHost nodename).Incompatibilities | fl *

    Please replace "vmname" and "nodename" with the names of the virtual machine and the cluster node, respectively.

    1. In addition, please try to disable 3rd party software and check whether the issue still occurring.

    Best Regards,

    Ian Xue


    If the Answer is helpful, please click "Accept Answer" and upvote it.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.