** Description changed: + [Impact] + + * on s390x the transition from non-secure to secure is a program directed + IPL. IPL "usually" was menat to load a system. Due to that the + -no-reboot option blocks that transition. + + * It is required to check the IPL function code and allow this "kind of + IPL" despite -no-reboot being set. + + [Test Case] + + * Run a s390x protvirt qemu-kvm and add the option -no-reboot + - without the fix this will fail + + * Note: We will need IBM to test this for the access to the required + hardware and a secure-execution enabled kernel (as used in the bug + report) + + [Regression Potential] + + * The change is small and clear, but if anything then IPL actions like + load&reboot should be affected. + + [Other Info] + + * n/a + + --- + ---Problem Description--- Secure Execution: Qemu fails to start with no output when "-no-reboot" option has been set. - + ---uname output--- Linux se1 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 17:53:50 UTC 2020 s390x s390x s390x GNU/Linux - - Machine Type = z15 8562 - + + Machine Type = z15 8562 + ---Debugger--- A debugger is not configured - + ---Steps to Reproduce--- Run Qemu with "-no-reboot" option: /usr/bin/qemu-system-s390x -kernel ./se.img -nographic -monitor none -machine accel=kvm -no-reboot - - Userspace tool common name: qemu-system-s390x - - The userspace tool has the following bit modes: 64 + + Userspace tool common name: qemu-system-s390x + + The userspace tool has the following bit modes: 64 Userspace rpm: qemu-system-s390x - Userspace tool obtained from project website: na - + Userspace tool obtained from project website: na Solution: Fix is upstream for qemu commit d1bb69db4ceb6897ef6a17bf263146b53a123632 Author: Christian Borntraeger <borntrae...@de.ibm.com> AuthorDate: Tue Jul 21 06:32:02 2020 -0400 Commit: Cornelia Huck <coh...@redhat.com> CommitDate: Fri Jul 24 08:35:22 2020 +0200 - s390x/protvirt: allow to IPL secure guests with -no-reboot + s390x/protvirt: allow to IPL secure guests with -no-reboot
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890154 Title: [UBUNTU 20.04] Secure Execution: Unable to start Qemu with "-no- reboot" option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1890154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
