@Breno - I agree to #3 but since we have no hard ETA on the kernel I want to avoid punting qemu to the very last few days. History told me that always something happens/blocks and if we would miss GA we can't SRu to keep the final pseries-bionic type in sync.
For #4 there is no good "keep in proposed" for the current Dev release. I discussed with lagarcia and JFH on IRC once more: ... [15:02] <lagarcia_> cpaelzer, I am OK with that. TBH, we can live with QEMU removing the workaround now or after the kernel has been changed. [15:05] <cpaelzer> there was a bug update by breno 3 minutes ago [15:05] * cpaelzer is reading [15:06] <cpaelzer> oh I see, and your comment - mirrored both at once [15:06] <cpaelzer> my concern is that if anything comes up late [15:06] <cpaelzer> we might end up with the qemu change not reverted [15:07] <cpaelzer> as after release it becomes an issue [15:07] <cpaelzer> and will no more be removable [15:07] <cpaelzer> for consistency of the pseries-bionic type [15:07] <jfh1> cpaelzer, lagarcia: ah - just saw the ticket update and a reply from Breno ... [15:08] <cpaelzer> jfh1: do we have anything like an expected date by the kernel Team? [15:08] <cpaelzer> I'd not want to wait with qemu later than end of this week TBH [15:08] <cpaelzer> history teached me not to try changing things last minute [15:08] <jfh1> cpaelzer: I agree - there is always the option to pin a package to prevent it from getting updated [15:09] <jfh1> that can be an option for those guys who still need to KVM on P9 ... [15:09] <cpaelzer> jfh1: lagarcia_: so are we agreeing that I'll revert the avoidance in qemu now considering the various constraints? [15:09] * cpaelzer is +1 [15:10] <jfh1> I think so ... [15:12] <lagarcia_> cpaelzer, yep [15:13] <lagarcia_> cpaelzer, when the patches reach bionic kernel, everything should work out of the box. Meanwhile, we can implement the workaround by hand. With all that said, I'm including the revert of the current mitigation from the next qemu upload. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752026 Title: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memory, try cap-htm=off" (kvm) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1752026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
