With the FFe granted for s390x-tools in comment #11 (thx for that) and the kernel patches having landed in proposed (220.127.116.11), about 2/3 of the overall FFe is now completed.
Having the beta freeze on April the 2nd in mind, and the good progress on testing the patched qemu version that was made available via PPA (protvirt testing by IBM and regression testing by Canonical) and the fact that Cornelia Huck (s390 qemu maintainer) finally allowed the patches to be queued for s390-next (LP 1835546), I'm wondering if the qemu part of this FFe is now acceptable as well, or if additional effort or more time is needed. @ 'Ubuntu Release Team' would you mind having now a look at the qemu situation, too? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866866 Title: [FFe] Please accept patches for secure guest feature Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Fix Committed Status in qemu package in Ubuntu: New Status in s390-tools package in Ubuntu: Fix Released Bug description: The secure guest feature (aka protvirt) affects multiple components (kernel, qemu and s390-tools - see below). While dedicated tickets for the different components exist since quite a while, the code arrived late and/or discussion to get it upstream accepted took longer than expected. (Even if we as of today didn't reached the kernel freeze, I'm already adding kernel to this FFe.) Since this is a very important feature the current IBM Z and LinuxONE family, it's requested to be included into focal, the next LTS release, to become exploitable by long running systems. The code is largely architecture specific. No brand new packages or new upstream version are requested, only the cherry-pick of commits (or PR) - so far everything is 'cherry-pick'-able. kernel: The patch set for the kernel is huge (30+ commits), but has only one common code patch (two files). The arch specific patches landed in between in linux-next, the arch specific one is expected to land there very soon (hours/days from now). The common-code patch ran through several hands and landed in between in Andrew Morton's mmots tree. A pre-screening of the code was done by the kernel team and it looked acceptable. (dedicated kernel ticket: https://bugs.launchpad.net/bugs/1835531) qemu: The entire code seems to be arch specific. Again a pre-screening of the maintainer lead to the fact that it should be acceptable, too. (dedicated qemu ticket: https://bugs.launchpad.net/bugs/1835546) s390-tools: The entire tool only exists for the s390x architecture. Hence obviously everything is arch specific on that. (dedicated s390-tools ticket: https://bugs.launchpad.net/bugs/1834534) Currently work is going on to test this function end to end based on Ubuntu components (means based on our s390-tools, qemu and kernel [focal master-next] trees). On top I applied the patches to the packages as well and did manual test buids. With that a potential regression can be considered as low - and even in case of a regression, it will affect s390x only. The patches are being staged for this feature in: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3970 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1866866/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : email@example.com Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp