[Bug 1888231] Re: [UBUNTU 20.04] zipl: Fix KVM IPL without bootindex
Launchpad Bug Tracker
1888231 at bugs.launchpad.net
Mon Oct 26 09:59:40 UTC 2020
This bug was fixed in the package s390-tools - 2.12.0-0ubuntu3.1
---------------
s390-tools (2.12.0-0ubuntu3.1) focal; urgency=medium
* debian/patches/0082-*.patch .. 0111-*.patch (LP: #1892350)
- Cherrypick patches from upstream, to make zipl boot loader check for
secure IPL feature before looking up data
- Cherrypick 0111-*/fd81728 ("zipl: fix incorrect setup of stage3 flags")
additionally, to fix bug in 0089-*/6c04f97 ("zipl: consolidate
stage3_params structs and stage3 flags")
* d/p/0110-zipl-stage3-correctly-handle-diag308-response-code.patch
- Cherrypick 943c5dc ("zipl/stage3: correctly handle diag308 response
code"), to fix KVM IPL without bootindex= specified (LP: #1888231)
* d/p/0112-cpumf-lscpumf.pl-displays-raw-event-number-incorrect.patch
- Only needed for perl lscpumf in Focal (LP: #1893027)
-- Lukas Märdian <lukas.maerdian at canonical.com> Thu, 01 Oct 2020
12:41:35 +0200
** Changed in: s390-tools (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
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:
Fix Committed
Status in s390-tools package in Ubuntu:
Fix Released
Status in s390-tools source package in Focal:
Fix Released
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
More information about the foundations-bugs
mailing list