I added the logs, keep in mind that I collected the logs from the vm
started with previous version of the kernel (can't boot the vm with the
affected version).
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1674635
Title:
Kernel linux-image-4.4.0-67-generic prevent the boot on Microsoft
Hyper-v 2012r2 Gen2 VM
Status in linux package in Ubuntu:
Confirmed
Bug description:
After updating the kernel inside the virtual machine to the version
4.4.0-67-generic, at the next boot the vm will stuck in a black screen at every
try. An hard reset is required.
The only workaround is to set the default in grub to the previous version.
The virtual machine hardware is a Gen2.
We are experiencing this issue on all our vps with the same kernel (around
300-400 vms).
---
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Mar 20 10:30 seq
crw-rw---- 1 root audio 116, 33 Mar 20 10:30 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/vg01--vg-swap_1
InstallationDate: Installed on 2017-03-13 (7 days ago)
InstallationMedia:
IwConfig: Error: [Errno 2] No such file or directory
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-66-generic.efi.signed
root=/dev/mapper/vg01--vg-root ro nomodeset
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
RelatedPackageVersions:
linux-restricted-modules-4.4.0-66-generic N/A
linux-backports-modules-4.4.0-66-generic N/A
linux-firmware 1.157.8
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial
Uname: Linux 4.4.0-66-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: 4898-1213-1192-4801-7611-1594-99
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674635/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
