Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, May 14, 2019 9:48 PM | 6 votes
Greetings,
Since December 2018, Hyper-v on Windows Server 2019 users have been reporting this issue. I am posting a new thread because the original thread on the topic had a potentially misleading headline. And most of the ensuing thread consisted of repeated requests for more information when in fact that information had already been provided. And yet, even after an MS representative confirmed through his own testing that the (serious) problem exists, no further information has been provided for over five months.
The problem, in a nut-shell is this: Guest VMs do not shut down gracefully when the Hyper-v host is shut down or restarted, regardless of guest VM settings.
Even when a guest VM is set to "shut down the guest operating system" as its default behavior for the "Automatic Stop Action", the Hyper-v host does not actually shut down the guest VM(s) as it shuts itself down. Rather, the VMs are just terminated as though power is cut. Upon rebooting, the guest VMs will report no attempt to be shut down, and instead report that the prior shutdown was unplanned.
This behavior is easily reproduced. Merely. . .
- Build a Hyper-v 2019 host server
- Install a guest VM.
- Set the guest VM to "shut down the guest operating system" under "Automatic Stop Action."
- Reboot the Hyper-v host while the guest VM is running.
. . .you will find that the guest VM was merely switched off ungracefully.
Microsoft, please acknowledge this issue and give us an ETR. I'm sure I'm not the only person putting their server upgrades on hold after running into this issue. Various work-arounds (using "save state" instead of "shut down") are not a viable option for me. Please, give us some news and hope (after an inexplicably long period of waiting) that a fix is imminent.
Best Regards,
Brian
All replies (8)
Tuesday, May 14, 2019 11:21 PM ✅Answered
You can vote this one up.
or contact microsoft directly here.
https://support.microsoft.com/en-us/hub/4343728/support-for-business
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter Management
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.
Thursday, May 16, 2019 8:40 AM
Hi ，
Just checking in to see if the information provided was helpful.
You could mark the useful reply as answer if you want to end this thread up.
Best Regards,
Candy
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]
Thursday, June 6, 2019 7:12 PM | 3 votes
It's crazy that this issue has not been addressed yet.
Friday, June 21, 2019 3:07 PM | 2 votes
Candy: tell someone with some authority at Microsoft, that this is a huge issue, and PREVENTS PEOPLE FROM UPGRADING TO 2019, and even raises questions about Azure reliability. Not to mention, THE PEOPLE ALREADY ON 2019 IS AT A VERY SERIOUS RISK OF LOSING DATA. Look at this thread, also: https://social.technet.microsoft.com/Forums/en-US/e8c45a15-0b9a-4b2c-ae2a-c546eadbcf41/hyperv-2019-guest-vm39s-shutdown-unexpectedly?forum=winserverhyperv
THIS BUG IS HUGE, IT SHOULD BE FIXED ASAP, WITH THE HIGHEST POSSIBLE PRIORITY.
Thursday, August 8, 2019 3:10 PM | 1 vote
If you have 2019 Hyper V servers you can install this service on them
https://github.com/platformcoders/vmmshutfix
and set machines to "Save" to not have Hyper V freak out on them. This will get you rolling until there is a fix. This service sends preshutdown notification from Host OS to VM's, that way critical services will start shutting down before the Hyper V saves or turns them off. You can compile it with free Visual Studio community downloaded from Microsoft.
If you want to test this code but you dont have 2019 HyperV lab you can use Self-paced lab for 2019 Software Defined Networking Microsoft has over here: https://www.microsoft.com/handsonlabs/SelfPacedLabs
Tuesday, September 17, 2019 8:55 PM
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?
Monday, December 2, 2019 3:34 PM
Hi. I had to go with 2016 for Hyper-V. Are there any news on this bug? Is this fixed, or still making 2019 unusable for Hyper-V?
Regards
Monday, February 17, 2020 7:18 PM | 1 vote
Fixed in October 2019 release
Good luck - we all need it.
Tim