This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(208, 35%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJS%3C/text%3E%3C/svg%3E)
I will apologize now as I am sure I will leave out pertinent information as I explain my issue here but any help would be appreciated.
We have a 3 node Hyper-V cluster running Windows 2022 Datacenter. It was setup by the vendor (not correctly) and then they bailed and said call Microsoft. All 3 servers are brand new, identical hardware, Lenovo servers in an Azure Stack HCI configuration. We are getting numerous errors in the event logs and are unable to migrate VM's in various ways. I have several test VM's running on HOST1, Windows 10, Server 2019, 32bit and 64bit versions of Window 7. I can do a quick migration without error to HOST2 and HOST3 but not Live. Some of the VM's can do Live migrations from HOST2 & 3 to each other and back to one but not all of them. Quick Migration works on all of them but that is not ideal for failover purposes.
The only errors I am getting are the following:
In Cluster Events in Failover Cluster Manager - Event ID 1155 - The pending move for the role 'Windows 10' did not complete.
In Event Viewer > Applications and Service Logs > Microsoft > Windows > Failover Clustering > Diagnostic - Event ID 2051 - [RES] Virtual Machine <Virtual Machine Windows 10>: Live migration of 'Virtual Machine Windows 10' failed.
Virtual machine migration operation for 'Windows 10' failed at migration source 'ITS-HYVEE1'. (Virtual machine ID E15B4F56-E68F-4EFA-9E99-559936334A26)
The Virtual Machine Management Service failed to establish a connection for a Virtual Machine migration with host 'ITS-HYVEE3': This operation returned because the timeout per
In Event Viewer > Applications and Service Logs > Microsoft > Windows > Hyper-V-High-Availability > Admin - Event ID 2111 - Live migration of 'Virtual Machine Windows 10' failed.
In Event Viewer > Applications and Service Logs > Microsoft > Windows > Hyper-V-VMMS > Admin - Event ID 15268 - Failed to get the disk information.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(262.40000000000003, 95%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EES%3C/text%3E%3C/svg%3E)
It sounds as though they configured networking incorrectly. You may also have faulty network hardware, although that's rare. The fix is probably simple, but finding the exact problem might require deeper help than you get on a forum. I would start by investigating the TCP/IP and virtual switch configuration on each host. Look especially for senseless multihoming and multiple default gateways. I would guess that they used a switch embedded team, so Get-VMSwitchTeam might give you some hints.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 68%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELT%3C/text%3E%3C/svg%3E)
Hello there,
Please try to restart the VMMS service .
Then check the event log again
Please check if you have assigned the same names for vSwitches on both nodes.
Please also check if VM configuration file is located on CSV.
Hope this resolves your Query !!
--If the reply is helpful, please Upvote and Accept it as an answer--
I restarted the VMMS service and tried moving a VM again and received the same errors in the event logs. All three nodes have the same VM Switch name, and the VM Config file for each VM is on the Cluster Storage Volumes. All three nodes can access the CSV's. I also checked all my network configs, no multiple gateways as was suggested by Eric above.
