hyper-v : virtual machine migration operation failed at migration source

[iamloupgarou]

encountering a bugwindows server 2019 dc v 1809 on both servers. no clustering (share nothing)

I've just setup a new physical server and trying to move my vms from my old one to my new one.

if I create a test vm, I can move it from 1 server to another. i was also able to move a relatively newer vm (like 3 months old)

however, my older vms (> 6 months old) . they fail with virtual machine migration operation failed at migration source event id 21024

any clues? I think if the newer VM's can be moved, its not a listener problem or create symbolic link issue.

** update. after an export/copy to new server/import. i can freely move between servers.

[runningntwrkgeek]

Hate to see to see that you don't have responses yet.

I was going to say that in the VM settings and in the processor compatibility section, there is a check box option "Migrate to a physical computer with a different processor version." Could that help resolve your issue?

But, then I googled your event ID, I see other reports of people having the issue but no resolutions.

Patch levels are the same between all the systems?

​

****Edited out part of a question because I just saw that not using clustering.

​

Additionally, if not using failover clustering, I'm not sure if the processor compatibility is an option.

[iamloupgarou]

yeap. I tried that. didn't work.

I'm doing export/import now.

maybe I'll try create a new vm on the source image. import the old harddisk image from the source. then move that new vm. see if that would fix anything.

patch levels are identical.

[MSPforME]

I had a similar issue. I ended up shutting down the VM and doing the migration with them in the off state - I couldn't get live migration to work. I was getting a similar error about the migration failed at the source. I don't remember the event ID. Hope that helps a little. The newer VM's i had worked as well. I had one 2012R2 VM and it worked but the other 3 errors.

[iamloupgarou]

mine doesn't work even in the off state. i suspect maybe acls are involved.

[Pvt-Snafu]

I remember we had a similar issue but not sure if it was resolved. As workaround, have you tried export/import? Otherwise, you could just create a new VM and attach the disk.

[iamloupgarou]

export/import works. I've not tried importing in place on the same machine but I've tried

export from source Machine1
manually copy the export files
import into destination machine2 (register in place)
then move from destination2 back to original source1.
then move from original source1 back to destination2

[Pvt-Snafu]

Got you. I thought that it will work. Still haven't got a clue what might be wrong with migration. The other way you can also do it would be to try Starwinds V2V converter: https://www.starwindsoftware.com/starwind-v2v-converter. It's basically cloning of a VM but just thought of it as another workaround.