Hyper-V 2019 - Guest VMs shutdown unexpectedly
When the host server shuts down, a bug in which guest VMs are not automatically shut down occurs in Windows 10 1809 or Windows Server 2019.
It is also a topic in the forum.
Please solve this bug as soon as possible.
This was supposed to be fixed in September's cumulative patch, but it seems that it hasn't. Why? How does people using this in production deal with this?
Daniel Domnick commented
Um, we just bought several 2K19 Datacenter licenses last week to upgrade our VM hosts - and I come across this? Epic fail. Contacting vendor to return my licenses tomorrow morning.
I don't understand why this has not been fixed yet....ridiculous! It's (almost) unbelievable that a MS Hypervisor cannot even safely shut down a VM running an MS Operating System...and MS seems to be completely ignoring the issue.
guys from MS ... Are You f kidding me ? We paid for this M$HIT !
IT´S A MS ZERO DAY BUG !!!
FIX IT ASAP !!!
Leonid Vardanyan commented
Это вообще забавно! Серьезнейшая ошибка, приводящая к потере данных на виртуальных машинах и потенциально способная привести к потере самих виртуалок (у нас в организации их 150 и восстанавливать после сбоев даже часть из них не просто и не быстро), уже пол-года не устраняется. Майкрософт, ау! Есть кто-нибудь дома?
Christopher Butler commented
How can this POSSIBLY Not be FIXED by now?
My suggestion to you all in the meantime is to protect yourself in the case of, say, a power failure situation by installing apcupsd on all the VMs and getting a UPS with an APC IP Card in it, set apcupsd up to speak directly to the card using PCNET protocol and time each of your VMs to shut down in a logical order before the Hyper-V Host does so.
Not only when host shuts down. We are having a 2003 server as virtual guest.. Whenever we shut it down via VMM shut down option on restart there will be the error information on Windows 2003 server startup that there was an unexpected shutdown. If that's true, that's very very concerning regarding data integrity and will sooner or later lead to data corruption.
Daniel Pedrosa Morillo commented
I think that this bug is still unfixed on purpose. It's Microsoft's way of telling us to "wait for the service pack". Nobody in their right mind would install a Windows release on its first year of life. Server 2019 is still technically "unfinished"
Fernando Rapetti commented
How on earth is this still not fixed!? I was planing to upgrade all Hosts to 2019, and i find this huge problem.
As DCs and Database Servers cannot use the "save state" option, there is no way to run them safely under this OS.
Worse: i even readed on the net that it also affects 2016!? Is that true!?
Very dissapointing. How can we trust Hyper-V if such a huge problem is unresolved for more than half a year, and counting!?
With all the hype on the Cloud, how can Microsoft afford to have such a problem on their hypervisor, and not care to fix it? Does this affect Azure?
I've had the same issues when I tried restarting a VM and it doesn't restart so unfortunately I don't use it anymore as I cannot see the VM is I'm remotely working so cannot confirm if its restarted.
I tested by open a VM connection VM Connection and tried restart a VM from WAC to see if the VM restarted and it didn't however I did not experience the VM shutdown unexpectedly but it doesn't seem to work