Hi all,
I have a strange problem here with Hyper-V live migration.
I have two hosts with identical hardware running Windows Server 2022. Both are on the same patch level and have no other role than Hyper-V installed. Hyper-V-configuration is also the same on both servers. They are not clustered, but live migration is enabled.
When I initiate a live migration, it works for some VMs and on some it fails. This is not random, the result remains the same for the specific VMs - but I cannot find a pattern or cause for the failure.
IF live migration fails, the error is always the same:
Virtual machine migration operation failed at migration destination.
Failed to transfer log files information.
Virtual machine migration operation for [VM] failed at migration destination [HOST].
[VM] Failed to transfer log files information. The data is invalid. (0x8007000D).
All I found regarding live migration failure troubleshooting pointed to something like 'check connection, access permissions, blabla' but there can't be an issue like that imho since some machines can be live-migrated (in both ways, from host A to B and back from B to A) so there must be something in the VM configuration itself that causes the issue.
A workaround would be to create new VMs using the existing VHDX-files, but that causes follow-up issues, since some IDs (e.g. NICs) change during that process - and this is no final option since two of the affected VMs are DCs!
Besides that I'd like to understand what's going on there.
What I can rule out is:
- VM OS
- VM-size (one VM has several hundred GB and can be migrated while others less than 100GB are failing)
- Age of VM
- Configuration version (all are on V10.0)
- VM Generation as only cause (at least there are some G2-VMs that are failing, but also all G1-VMs left)
So, does anybody have an idea how I can solve this?
EDIT: I completely forgot to mention that none of the VMs have been initially created on one of the hosts I'm talking about. They have all been migrated from older servers running Windows Server 2019 via export-vm -> import on new server -> update configuration from 9.0 to 10.0.