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

[Frank Heimes]

Since this fix is included in s390-tools 2.14, I'll mark the groovy
entry as Triaged (it would technically even a kind of duplicate of LP
1884721, if the SRU req. to focal wouldn't be there).

** Changed in: s390-tools (Ubuntu Groovy)
       Status: New => Triaged

** Changed in: s390-tools (Ubuntu Groovy)
     Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Foundations Team (canonical-foundations)

** Changed in: s390-tools (Ubuntu Focal)
     Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations)

-- 
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:
  Triaged
Status in s390-tools package in Ubuntu:
  Triaged
Status in s390-tools source package in Focal:
  New
Status in s390-tools source package in Groovy:
  Triaged

Bug 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