WINDOWS SERVER 2019 -HYPER-V TRIPLE FAULT BUG
i migrate some VMs from old Hyper-V 2012R2 infrastructure to new 2019 infrastructure, the migration was successful, but on the first reboot of migrated VM the VM wont start. In the event log i found this critical event:
„‚SVR_xxx“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 2F3329E8-5485-4DA3-93D5-A493E9A885A3)„
Workaround is change MAC address from dynamic to static and start VM, in my case the VM not started so i changed the MAC address from static to dynamic and VM started successfuly.
This issue is now resolved in the 2019-05-21 cumulative update (KB4497934)
(Visited 2 479 times, 1 visits today)
Toma! You are a 2am life saver! I ran into this identical issue this evening. I updated from HyperV 2012 R2 to 2019. Ran fine until I did the first restart and then I ran into the dreaded triple fault scenario. I was about to take drastic measures such as restoring from backups and doing import/export measures. Luckily I found your blog post. I did exactly as you described by changing MAC from dynamic to static and just like magic the guest VM’s are back online. Thanks to YOU! I’ll be applying the KB4497934 next. Just wanted to say thank you!!