[Bug 1691978] Re: Ubuntu 17.04: KVM host System does not boot up after upgrading to 17.04

Mon Aug 14 18:17:46 UTC 2017

The issue reported here was that upgrade from 16.10 to 17.04 failed.
16.10 (yakkety) is no longer supported. Can you please verify that this
is fixed in 16.04.3? and 17.04 ?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/1691978

Title:
  Ubuntu 17.04: KVM host System does not boot up after upgrading to
  17.04

Status in The Ubuntu-power-systems project:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  == Comment: #0 - HEMALATHA B T <hemalatha.bt at in.ibm.com> - 2017-05-17 10:28:27 ==
  ---Problem Description---
  System does not come up after upgrading from ubuntu 16:10 to ubuntu 17.04 

  Contact Information = hemalatha.bt at in.ibm.com 

  ---uname output---
  NA

  Machine Type = Firestone15 cores system 

  ---System Hang---
  Upon rebooting the system after upgrade to Ubuntu 17.04, the system does not come. 
  Have to power off and then poweron again the CEC From ipmitool and select a different
  kernel like 4.8 or 4.4 to get the system prompt

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   The system was at 16.04.2 ubuntu KVM host. For another bug, the system was to be updated
   to 4:10 Kernel. On guest I could easily update to 4:10 from ubuntu 16.04.2. However host would
  hang and could not come up on 4:10 kernel. Hence tried to officially upgrade to 17.04. 
  High level steps followed are:
  Upgrade from 16.04 to 16.10 and then upgrade to 1704. 
  On restarting the system the kernel does not boot up at 4:10 level. 
  Some of the messages seen suspecting on ipmitool console during bring up of 4:10 kernel are,

  [8093518175,5] INIT: Starting kernel at 0x20010000, fdt at 0x305bd430 (size 0x18834)
  [8247984723,3] OPAL: Trying a CPU re-init with flags: 0x2
  [    0.000000] OPAL V3 detected !
  [    0.000000] Reserved memory: failed to reserve memory for node 'ibm,homer-image at 7ffd800000': base 0x0000007ffd800000, size 4 MiB
  [    0.000000] Reserved memory: failed to reserve memory for node 'ibm,homer-image at 7ffdc00000': base 0x0000007ffdc00000, size 4 MiB
  [    0.000000] Reserved memory: failed to reserve memory for node 'ibm,hbrt-vpd-image at 7ffd700000': base 0x0000007ffd700000, size 1 MiB
  [    0.000000] Reserved memory: failed to reserve memory for node 'ibm,hbrt-target-image at 7ffd6d0000': base 0x0000007ffd6d0000, size 0 MiB
  [    0.000000] Reserved memory: failed to reserve memory for node 'ibm,hbrt-code-image at 7ffd4a0000': base 0x0000007ffd4a0000, size 2 MiB
  [    0.000000] Reserved memory: failed to reserve memory for node 'ibm,occ-common-area at 7fff800000': base 0x0000007fff800000, size 8 MiB
  [    0.000000] Reserved memory: failed to reserve memory for node 'ibm,firmware-stacks at 31c00000': base 0x0000000031c00000, size 17 MiB
  [    0.000000] Reserved memory: failed to reserve memory for node 'ibm,firmware-data at 31000000': base 0x0000000031000000, size 12 MiB
  [    0.000000] Reserved memory: failed to reserve memory for node 'ibm,firmware-heap at 30300000': base 0x0000000030300000, size 13 MiB
  [    0.000000] Reserved memory: failed to reserve memory for node 'ibm,firmware-code at 30000000': base 0x0000000030000000, size 3 MiB
  [    0.000000] Reserved memory: failed to reserve memory for node 'ibm,firmware-allocs-memory at 4000000000': base 0x0000004000000000, size 9 MiB
  [    0.000000] Reserved memory: failed to reserve memory for node 'ibm,firmware-allocs-memory at 39c00000': base 0x0000000039c00000, size 9 MiB
  [    0.000000] Using PowerNV machine description
  [    0.000000] Page sizes from device-tree:

  [    1.447130] pci 0001:02:0b.0: BAR 8: assigned [mem 0x3fe881800000-0x3fe882ffffff]
  [    1.447969] pci 0001:02:01.0: BAR 7: no space for [io  size 0x1000]
  [    1.449433] pci 0001:02:01.0: BAR 7: failed to assign [io  size 0x1000]
  [    1.450256] pci 0001:02:0a.0: BAR 7: no space for [io  size 0x1000]
  [    1.451071] pci 0001:02:0a.0: BAR 7: failed to assign [io  size 0x1000]
  [    1.452733] pci 0001:02:0b.0: BAR 7: no space for [io  size 0x1000]
  [    1.453580] pci 0001:02:0b.0: BAR 7: failed to assign [io  size 0x1000]
  [    1.454425] pci 0001:02:0a.0: BAR 7: no space for [io  size 0x1000]
  [    1.456107] pci 0001:02:0a.0: BAR 7: failed to assign [io  size 0x1000]
  [    1.456949] pci 0001:02:0b.0: BAR 7: no space for [io  size 0x1000]
  [    1.457753] pci 0001:02:0b.0: BAR 7: failed to assign [io  size 0x1000]
  [    1.458580] pci 0001:02:01.0: BAR 7: no space for [io  size 0x1000]
  [    1.459392] pci 0001:02:01.0: BAR 7: failed to assign [io  size 0x1000]
  [    1.460229] pci 0001:03:00.0: BAR 6: assigned [mem 0x3fe880000000-0x3fe88007ffff pref]

  Enter=accept, e=edit, n=new, x=exit, l=language, h=help
  The system is going down NOW!t 
  Sent SIGTERM to all processes
  Sent SIGKILL to all processes
  [19776032192,3] OPAL: Trying a CPU re-init with flags: 0x1
  [19970394859,3] OPAL: Trying a CPU re-init with flags: 0x2
   -> smp_release_cpus()
  spinning_secondaries = 119
   <- smp_release_cpus()
  [    3.165247] Unable to open file: /etc/keys/x509_ima.der (-2)
  [    3.165249] Unable to open file: /etc/keys/x509_evm.der (-2)
  [    5.214521] lpfc 0000:01:00.0: 0:1303 Link Up Event x1 received Data: x1 x0 x80 x0 x0 x0 0
  [    6.251254] lpfc 0000:01:00.1: 1:1303 Link Up Event x1 received Data: x1 x0 x80 x0 x0 x0 0

  After this is stops progressing

  Userspace tool common name: do-release-upgrade -d 

  The userspace tool has the following bit modes: 64bit 

  Userspace rpm: na

  Userspace tool obtained from project website:  na 

  *Additional Instructions for hemalatha.bt at in.ibm.com: 
  -Post a private note with access information to the machine that the bug is occuring on.
  -Attach ltrace and strace of userspace application.

  Please write to me for system access

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1691978/+subscriptions