Windows Server 2019 Shared Nothing Live Migration - Single Error Event ID 21024

Question

Hello!

I am trying to get a Shared-nothing Live Migration working between a Windows Server 2019 Hyper-V Server and a Hyper-V 2019 server (Not running full Windows). These two hosts are not in a cluster.

I am getting an error message "There was an error during move operation. Virtual machine migration operation failed at migration source". The only event that I can find is in the "Hyper-V VMMS - Admin" log and it is Event ID 21024 "Virtual machine migration operation for <VM> failed at migration source <host>". No other messages.

I am getting this same error on multiple VM's, and whether I am using CredSSP or Kerberos (using Constrained Delegation).

I even tried removing the Hyper-V 2019 server from the domain and re-configuring Constrained Delegation.

Does anyone have any suggestions for me to try? If so, I would really appreciate it!

Dave

Answer 1

I'd suggest starting a case here with product support.
https://support.serviceshub.microsoft.com/supportforbusiness

--please don't forget to Accept as answer if the reply is helpful--

Answer 2

Hi,

1. Where does the VM store in the source server, local storage or network storage?
2. On the source server, please open CMD, and run netstat -an | find "6600", check if port 6600 is listening
   
3. Please try to restart the VMMS service on the source server, check if it could work.
   

Thanks for your time!
Best Regards,
Anne

-----------------------------

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

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

Thanks for you input, Anne!

1. The storage for the VM is local (E:)
2. port 6600 is listening on the source server: C:\Windows\system32>netstat -an | find "6600"
   TCP 10.1.1.10:6600 0.0.0.0:0 LISTENING
   TCP [fe80::c860:ba0b:d0f1:5191%4]:6600 [::]:0 LISTENING
3. This problem has been ongoing - multiple reboots of both the source & destination Hyper-V (which would obviously restart services) doesn't fix the problem.

Answer 4

I also was running into issues with this. My solution was to change the memory of the virtual machine from 16GB to 8GB and then the live migration was able to work!

Also, some things I check when doing a live migration is

• Check that the name of the virtual network cards match on the old server and new server (this might be fixed by MS now though)
• Make sure there are no ISO or CD's attached to the virtual machine
• Make sure that the Processor compatibility section is checked for "migrate to a physical computer with a different processor version"
• ensure there are no shadow checkpoints by running the following hyper v powershell command Get-VM | ForEach-Object { $_ | Get-VMSnapshot } If it finds snapshots, run this command Get-VM | Get-VMSnapshot | Remove-VMSnapshot -Confirm:$false