This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1787423
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1787423
Title:
When shutting down, the VM is stuck in the state "Stopping" and
Hyper-V Management Service (vmms) must be terminated
Status in linux package in Ubuntu:
Incomplete
Bug description:
My problem is, that my Hyper-V Guest (Ubuntu Server 18.04.1) is stuck
at the state "Stopping" when I shut down the guest. When this happens
I am not capable of doing any actions regarding this guest. The only
solution is to shutdown the other guests and kill the vmms.exe.
I recognized this behaviour in version 18.04 before and decided to wait a bit
for the software to mature. Unfortunately this error also occurs in this
version 18.04.1.
It seems that the system is shutting down fine (reboot or shutdown) and when
the moment comes where it powers off the image is fading but it hangs/stucks at
this faded image and it does not turn off the machine. Last time I initiated a
shutdown via ssh and was not connected directly through the Hyper-V manager to
the console. When I saw the "Stopping" state I tried to connect to the console
and I recognized that the Hyper-V connection manager constantly flapping with
connecting to the VM until an error message is shown which reports an problem
with connecting to the VM. It looks like it is stuck between the last step of
shutting down and the "ACPI power off".
The Hyper-V host is a Windows Server 2012 R2 Server Core. The Hyper-V
guest is a generation 2 machine with 16 GiB hard disk, 1024 MiB RAM
and three NICs.; 2 CPUs assigned. The previous released Ubuntu LTSB
didn't show this erroneous behaviour. The machine was designed to run
as router and mail relay.
In all my tests this problem occurred. I took a screenshot. Nothing -
except that it stays at this point - looks wrong from outside. But I
am a Windows administrator and not a Linux administrator, therefor I
am not familiar dealing with those kind of problems.
https://1drv.ms/u/s!AoEuCh4Zdmlpg5MF81-oczJ8CfWeGg
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787423/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
