Thanks Victor for explaining what use-case this is about. Well, what should I say - I'm and was a s390x fanboy due to my history - so I'd like to add it. But I'm not the one to decide - and in this case that is probably good to not be too influenced. We will have to present this to release team for groovy and SRU Team later on.
Groovy: I'll add an FFe template here based on comment #5 ## SRUability ## I've looked forward a bit for an SRU to qemu 4.2 later on that would also need to include f76b348ec7 Linux headers: update dc6f8d458a linux-headers: update against Linux 5.7-rc3 ddda37483d linux-headers: update 50fd0c375b linux-headers: Update 2a886794f1 linux-headers: Update Of which some then won't apply cleanly due to the protvirt backport. The noise is handleable, but these are more and more changes that pile up. If you want to drive this forward to FOCAL as well it might be useful to provide us a header update with just exactly what you need instead. ** Information type changed from Private to Public ** Summary changed: - [20.10 FEAT] KVM: Enable Channel Path Handling for vfio-ccw - qemu part + [FFe][20.10 FEAT] KVM: Enable Channel Path Handling for vfio-ccw - qemu part -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887930 Title: [FFe][20.10 FEAT] KVM: Enable Channel Path Handling for vfio-ccw - qemu part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1887930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
