Hey Checkyourlogsfans,
We have been experiencing an issue in the field for a while now with Server 2019 where when a VM that is migrated to 2019 it fails with a Triple Fault:
Critical 03/01/2019 16:13:49 Hyper-V-Worker 18560 None
‘Test VM 1’ was reset because an unrecoverable error occurred on a virtual processor that caused a triple fault. If the problem persists, contact Product Support. (Virtual machine ID 90B45891-E0EB-4842-8070-F30FF25C663A)
Right now, Microsoft does not have a fix for this issue and today came up with the following workaround.
Quote: Ben Armstrong – Microsoft
“In the meantime, it is possible to work around this. To get the virtual machine to boot, you need to get Hyper-V to create new firmware entries for the IPv6 boot data. The easiest way to do this is to change the MAC addresses on any network adapters connected to the affected virtual machine. This process is different for virtual machines with dynamic and static MAC addresses.”
Just change the static MAC to something different, and then you can change it back once it boots.
We ran into this issue big time with a large Hyper-V Migration project going from Windows Server 2012 R2 to Windows Server 2019. We were using Veeam to migrate the VM’s to the new Storage Spaces Direct farm and ran into this issue. Veeam would fail each Replicated VM… Our solution before this was to delete and recreate every VM which was a huge pain in the ass.
Hopefully, this little Mac Address fix will do the trick for us.
For more information you can check out Ben’s Blog: https://american-boffin.com/2019/01/17/virtual-machines-do-not-boot-after-moving-from-windows-server-2012-r2-to-windows-server-2019/
Thanks,
Dave
![The Case of Failing Veeam Replicas – The RPC Function Call failed Function Name [InvokeTestConnection]](https://i0.wp.com/www.checkyourlogs.net/wp-content/uploads/2019/08/082319_0123_TheCaseofFa1.png?resize=440%2C264&quality=80&ssl=1)
Thanks for posting. Was very helpful and sadly, nothing comes up from MS in all my searching on this. People like you who take the time make the internet a better place.
Really helpful post – was very confused after doing the same upgrade you did and got same result. Changed MAC of affected VMs and they’re running again…
Great fix. Thx!
I opened a case with Microsoft and they confirmed the BUG.
We received a private HotFix and it’s working great – VMs are starting again without altering their config.
Another easy way is to delete the network adapter and reinstall it again. Now It works fine.
Had the same, the VM was on “Dynamic MAC” however. I was able to fix it by disabling the Protected Network setting on the NIC. Since it’s a home server this is not a problem, make sure this is what you want in a production environment 😉
Great advice! Thank you. And shame on MS.
Does nto work for me. I’m trying to import a linux vm. Either changing the static mac or installing a new virtual adapter does not work after configuring a static mac with the desired value…any other hints?
Thank you for your advice. I have the same case. It helps! Shame on MS.
same migration here, smaller so just copying the VMs from host to host. Only happened on our virtual PBX, it had SR-IOV enabled? Deleted the NIC, added a new one, booted. Thank you for taking the time to make this post… boo MSFT