VM crashes after saving and restoring with latest kernel

[Daniel]

After upgrading my Ubuntu Hyper-V VM to the latest kernel (4.4.0-67-generic, Ubuntu 16.04.2 LTS), it started crashing after saving and restoring it.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-67-generic 4.4.0-67.88
ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
Uname: Linux 4.4.0-67-generic x86_64
AlsaDevices:
 total 0
 crw-rw----+ 1 root audio 116, 1 Mar 26 20:49 seq
 crw-rw----+ 1 root audio 116, 33 Mar 26 20:49 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Date: Sun Mar 26 20:51:29 2017
HibernationDevice: RESUME=/dev/mapper/HUGVWEB01--vg-swap_1
InstallationDate: Installed on 2015-10-29 (514 days ago)
InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lspci:

Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: Microsoft Corporation Virtual Machine
PciMultimedia:

ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-67-generic.efi.signed root=/dev/mapper/hostname--vg-root ro elevator=noop
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-67-generic N/A
 linux-backports-modules-4.4.0-67-generic N/A
 linux-firmware 1.157.8
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2017-02-23 (31 days ago)
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: 0559-3398-3600-3623-3585-8903-93
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.name: Virtual Machine
dmi.product.version: Hyper-V UEFI Release v1.0
dmi.sys.vendor: Microsoft Corporation
---
AlsaDevices:
 total 0
 crw-rw----+ 1 root audio 116, 1 Mar 26 21:13 seq
 crw-rw----+ 1 root audio 116, 33 Mar 26 21:13 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=/dev/mapper/HUGVWEB01--vg-swap_1
InstallationDate: Installed on 2015-10-29 (514 days ago)
InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
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=/vmlinuz-4.4.0-67-generic.efi.signed root=/dev/mapper/hostname--vg-root ro elevator=noop
ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-67-generic N/A
 linux-backports-modules-4.4.0-67-generic N/A
 linux-firmware 1.157.8
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial xenial
Uname: Linux 4.4.0-67-generic x86_64
UnreportableReason: The report belongs to a package that is not installed.
UpgradeStatus: Upgraded to xenial on 2017-02-23 (31 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-adressverwaltung
_MarkForUpload: False
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: 0559-3398-3600-3623-3585-8903-93
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.name: Virtual Machine
dmi.product.version: Hyper-V UEFI Release v1.0
dmi.sys.vendor: Microsoft Corporation

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1676209

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.

[Daniel (d-maml-o)]

apport information

[Daniel (d-maml-o)]

apport information

[Daniel (d-maml-o)]

apport information

[Daniel (d-maml-o)]

apport information

[Daniel (d-maml-o)]

apport information

[Daniel (d-maml-o)]

apport information

[Daniel (d-maml-o)]

apport information

[Daniel (d-maml-o)]

apport information

[Daniel (d-maml-o)]

apport information

[Daniel (d-maml-o)]

Added a screenshot of the error I see when connecting to the Hyper-V VM, after it crashed.

[Joseph Salisbury (jsalisbury)]

This could be related to bug 1674635. Can you try the test kernel posted in comment #42?

[Blake Cottington (cottington)]

Hi, I know this isn't my thread but I'm trying to help. I am seeing the crash of the VM during a Windows Server Backup with the latest kernel 4.4.0-67. I installed the kernel from comment 42 referenced in the other thread. It did make a difference. I will post screenshots of the results.

Side note - I am a noob to installing patches like this. I tried using the 3rd technique here:
https://wiki.ubuntu.com/Kernel/Dev/KernelTesting

and pointed to: http://kernel.ubuntu.com/~jsalisbury/lp1674635/revert/

then did apt-get update, but I got a message similar to this:
W: The repository '...' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch ... 404 Not Found
E: Some index files failed to download. They have been ignored, or old ones used instead.

So... I did wget and dpkg -i for each of the 12 files in the directory.

[Blake Cottington (cottington)]

More info: Host is Server 2016. Guest is Generation 2 type. Dynamic memory is not enabled.

[Daniel (d-maml-o)]

Joseph, your kernel seems to be working fine. Although I am still seeing an error upon restoring.

Blake, this is how you do it: https://wiki.ubuntu.com/Kernel/MainlineBuilds

[Joseph Salisbury (jsalisbury)]

@Daniel, is my test kernel resolving this bug and preventing the crash?

[Daniel (d-maml-o)]

Joseph, I saved and restored the VM several times. Veeam backups finished successfully two times in a row. The VM did not crash with your kernel.

The error message on the login promp remains (see attachment in #17), although I am not sure if that is connected to the crash.