[Bug 1888231] Re: [UBUNTU 20.04] zipl: Fix KVM IPL without bootindex

[Lukas Märdian]

** Description changed:

+ [Impact] 
+  * Without bootindex specified there is no IPL parmblock on KVM which can be read by the stage3 loader.
+  * Backported to allow IBM Z users to boot KVM machines without secure initial program loader (IPL) data and without bootindex= parameter specified
+ 
+ [Test Case]
+  * prepare a new non-secure IPL and try booting via this IPL, without specifying the bootindex= parameter
+  * check if stage3 loader runs successfully
+ 
+ [Regression Potential]
+ 
+  * regressions in zipl/stage3 could break newly created IPLs
+  * If an IPL is broken, the boot sequence on IBM Z machines could not work
+  * the package is only available on s390x and thus could only affects IBM Z machines
+  * Existing boot devices / IPLs would not be affected
+ 
+ [Other Info]
+  * Needs to be tested/verified by IBM internally
+  * Patch is included in upstream 2.14.0 release
+  * Related to LP: #1892350 and LP: #1893027
+ 
+ === Original Description ===
  Description:   zipl: Fix KVM IPL without bootindex
  Symptom:       Failed IPL on KVM when no bootindex is specified.
  Problem:       Without bootindex specified there is no IPL parmblock
-                on KVM which can be read by the stage3 loader.
+                on KVM which can be read by the stage3 loader.
  Solution:      In case diag308 gives a response code 0x102 the stage3
-                loader can safely assume that no secure IPL is required
-                since no IPL report block exists.
+                loader can safely assume that no secure IPL is required
+                since no IPL report block exists.
  Reproduction:  IPL on KVM without 'bootindex=' attached.
  Upstream-ID:   c9066bf5497300db5e0ba11bf111683ea225d8c8
-                b7f1977d3f9332f82e7f388fb18076b89b83944e
+                b7f1977d3f9332f82e7f388fb18076b89b83944e
  
  Component:     s390-tools 2.14
  
  Should also be integrated into 20.04, where secure boot is enabled.

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

Title:
  [UBUNTU 20.04] zipl: Fix KVM IPL without bootindex

Status in Ubuntu on IBM z Systems:
  In Progress
Status in s390-tools package in Ubuntu:
  Fix Released
Status in s390-tools source package in Focal:
  New
Status in s390-tools source package in Groovy:
  Fix Released

Bug description:
  [Impact] 
   * Without bootindex specified there is no IPL parmblock on KVM which can be read by the stage3 loader.
   * Backported to allow IBM Z users to boot KVM machines without secure initial program loader (IPL) data and without bootindex= parameter specified

  [Test Case]
   * prepare a new non-secure IPL and try booting via this IPL, without specifying the bootindex= parameter
   * check if stage3 loader runs successfully

  [Regression Potential]

   * regressions in zipl/stage3 could break newly created IPLs
   * If an IPL is broken, the boot sequence on IBM Z machines could not work
   * the package is only available on s390x and thus could only affects IBM Z machines
   * Existing boot devices / IPLs would not be affected

  [Other Info]
   * Needs to be tested/verified by IBM internally
   * Patch is included in upstream 2.14.0 release
   * Related to LP: #1892350 and LP: #1893027

  === Original Description ===
  Description:   zipl: Fix KVM IPL without bootindex
  Symptom:       Failed IPL on KVM when no bootindex is specified.
  Problem:       Without bootindex specified there is no IPL parmblock
                 on KVM which can be read by the stage3 loader.
  Solution:      In case diag308 gives a response code 0x102 the stage3
                 loader can safely assume that no secure IPL is required
                 since no IPL report block exists.
  Reproduction:  IPL on KVM without 'bootindex=' attached.
  Upstream-ID:   c9066bf5497300db5e0ba11bf111683ea225d8c8
                 b7f1977d3f9332f82e7f388fb18076b89b83944e

  Component:     s390-tools 2.14

  Should also be integrated into 20.04, where secure boot is enabled.

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