group.of.nepali.translators team mailing list archive

[Joseph Salisbury <joseph.salisbury@xxxxxxxxxxxxx>]

Can you see if this bug happens with the following kernel:

http://kernel.ubuntu.com/~jsalisbury/lp1741934/

** Changed in: linux (Ubuntu)
   Importance: Undecided => Critical

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => Critical

** Changed in: linux (Ubuntu Xenial)
       Status: New => Confirmed

** Tags added: kernel-key

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1742286

Title:
  [regression] Xenial host with 4.4.0-108.131 fails to power some KVM
  guests

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  I have an (old) hypervisor with an Intel Xeon E3110 (Core 2 Duo E8400
  rebranded) that is unable to boot 2 of my 17 KVM guests. The guests
  that boot fine are all Xenial (running 4.4.0-104.127). The 2 that do
  not work are: a Trusty VM (3.13.0-137.186) and an OpenBSD 6.2 VM
  (latest kernel).

  With previous kernels, the host used those boot arguments:

    hugepages=3008 kaslr nmi_watchdog=0 possible_cpus=2
  transparent_hugepage=never vsyscall=none

  Now with 4.4.0-108.131, to be able to boot the Trusty and OpenBSD VMs,
  I had to drop most boot args to only have this:

    hugepages=3008

  I will try to find which arg(s) is responsible for the guest boot
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-108-generic 4.4.0-108.131
  ProcVersionSignature: Ubuntu 4.4.0-108.131-generic 4.4.98
  Uname: Linux 4.4.0-108-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices:
   total 0
   crw-rw----+ 1 root audio 116,  1 Jan  9 15:28 seq
   crw-rw----+ 1 root audio 116, 33 Jan  9 15:28 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
  Date: Tue Jan  9 15:54:18 2018
  HibernationDevice: RESUME=UUID=36924004-26f8-48e3-abe3-41be311bd7af
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: System manufacturer P5E-VM HDMI
  PciMultimedia:

  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-108-generic root=UUID=40a302c9-82d9-4574-ac2f-efcf5c9d126f ro hugepages=3008
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-108-generic N/A
   linux-backports-modules-4.4.0-108-generic  N/A
   linux-firmware                             1.157.14
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/26/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0709
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5E-VM HDMI
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0709:bd03/26/2010:svnSystemmanufacturer:pnP5E-VMHDMI:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5E-VMHDMI:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5E-VM HDMI
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742286/+subscriptions