Ok, good that the idea was picked up and is under consideration.
Since you are going to open a new BZ once available, I'm setting this to
Opinion/Wishlist for now ...
** Changed in: qemu (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: qemu (Ubuntu)
Status: New => Opinion
**
** Tags added: architecture-s39064 bugnameltc-182539 severity-high
targetmilestone-inin2004
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852541
Title:
Emulate s390x secureboot / sipl in qemu
To m
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852541
Title:
Emulate s390x secureboot / sipl in qemu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ub
In ppa:xnox/scratch there is qemu that forces "secure" to be 1 always on
boot. And kernel locks itself down.
[0.068890] Kernel is locked down from Secure IPL; see man
kernel_lockdown.7
** Patch added: "sipl-trick.patch"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1852541/+attachm
After discussing with IBM I've created the following RFE:
Emulate s390x secureboot / sipl in qemu
https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=138164
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
** Summary changed:
- "fake" s390x sipl
+ Emulate s390x secureboot / sipl in qemu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852541
Title:
Emulate s390x secureboot / sipl in qemu
To manage not
