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
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Aug 16 17:14 seq
crw-rw---- 1 root audio 116, 33 Aug 16 17:14 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=/dev/mapper/s--rras--1--vg-swap_1
InstallationDate: Installed on 2018-07-28 (19 days ago)
InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lspci:
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: Microsoft Corporation Virtual Machine
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=/dev/mapper/s--rras--1--vg-root ro
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-29-generic N/A
linux-backports-modules-4.15.0-29-generic N/A
linux-firmware 1.173.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic
Uname: Linux 4.15.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 11/26/2012
dmi.bios.vendor: Microsoft Corporation
dmi.bios.version: Hyper-V UEFI Release v1.0
dmi.board.asset.tag: None
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: Hyper-V UEFI Release v1.0
dmi.chassis.asset.tag: 8318-2488-1276-9893-9570-2978-42
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: Hyper-V UEFI Release v1.0
dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
dmi.product.family: Virtual Machine
dmi.product.name: Virtual Machine
dmi.product.version: Hyper-V UEFI Release v1.0
dmi.sys.vendor: Microsoft Corporation
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.