--- Comment From heinz-werner_se...@de.ibm.com 2019-08-14 03:38 EDT---
IBM Bugzilla status -> closed, Fix Released with Eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830243
Title:
[19.
--- Comment From cborn...@de.ibm.com 2019-07-05 06:10 EDT---
Yes, you do need a signed key. For the purpose of QEMU testing maybe you can
use the sign_file tool from the kernel to have a signed kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
--- Comment From cborn...@de.ibm.com 2019-07-04 10:32 EDT---
You can actually try to test that yourself by having a guest that has a very
new zipl
(this commit or newer)
https://github.com/ibm-s390-tools/s390-tools/commit/6ea645b3453264a0f1a60955c4476dab54035f88
(s390-tools 2.9 will be goo
--- Comment From mihaj...@de.ibm.com 2019-07-04 08:02 EDT---
While I'd expect that the combination of a newer guest under an older
hypervisor will not be that common, it would probably not hurt to SRU this. If
you do, don't forget the OpenStack QEMUs.
--
You received this bug notificati
--- Comment From cborn...@de.ibm.com 2019-07-04 05:29 EDT---
The commits identified by Dmitry are mostly for IPLing from a dasd attached via
vfio-ccw.
I cannot say right now if we want that feature also for disco,cosmic and
bionic.
If not we can simply focus on just the secure boot toler
