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/