Live migration Error

[steveg]

I'm trying to live migrate our virtual servers from existing 2019 host to new 2025 host.  

 

I've got it all setup, delegated access, configured identical networks, enabled cpu compatibility etc, but running compare-vm gives incompatibilities {21024}.  Actually trying to run a move gets most of the way there and gives a fairly generic error, with the same 21024 code logged in event log.

 

I've got 2 servers going to 2 new servers and both give the same issue.  Export and then import to the new server works fine, but I can't do this for the domain controllers.  

[CrootUK]

Pickup the entire vm folder, import with same guid, perfectly doable with DCs or any VM for that matter

Edited June 18, 2025 by CrootUK

[steveg]

I've done that with all the other VMs, export and import with same id, but didn't think this could be done with a DC? 

[Fazza]

Whenever I've had issues live migrating a VM I've got around it by using Replication.  I replicate the VM to the new Hypervisor and then perform a failover and then get rid of the Replication and jobs a goodun!

[willtech]

On 18/06/2025 at 15:52, steveg said:

I'm trying to live migrate our virtual servers from existing 2019 host to new 2025 host.  

 

I've got it all setup, delegated access, configured identical networks, enabled cpu compatibility etc, but running compare-vm gives incompatibilities {21024}.  Actually trying to run a move gets most of the way there and gives a fairly generic error, with the same 21024 code logged in event log.

 

I've got 2 servers going to 2 new servers and both give the same issue.  Export and then import to the new server works fine, but I can't do this for the domain controllers.  

Have you seen: https://learn.microsoft.com/en-us/troubleshoot/windows-server/virtualization/troubleshoot-live-migration-issues#event-id-21024:~:text=Event ID 21024,address is used.

Edited June 20, 2025 by willtech

[steveg]

Thanks, had seen that troubleshooting guide but it doesn't get to being completed so don't think it is the error they are referencing.

 

I will try doing it with replication and failover.