Comment 4 for bug 1887930
Revision history for this message
| Christian Ehrhardt (paelzer) wrote Re: [20.10 FEAT] KVM: Enable Channel Path Handling for vfio-ccw - qemu part | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
FYI:
The patches would apply in groovy, but I agree to Frank that for the late addition to Groovy we'd need you to drive an FFe process (very soon). And since you usually want to have things in the last LTS we will need to make even more of a good case for this to have a compelling case for an SRU later on.
The current description outlines what technically happens, but if you could add more detail and scenarios to it where it actually fails today and works with the fix. If there are some/no ways for today users to mitigate the issue and so on.
I mean a crash of a guest (which you mentioned is the consequence) is always bad and shold be avouded. But "changes in the host's channel path" is rather generic term. Let me outline the range that comes to my mind for that:
1. A user disables the ccw disk the guest currently uses - well bad luck that will never be smooth I guess.
2. some one sets a checkbox on the storage server UI enabling an unimportant feature for a disk, due to that all guests - even those not using the disks - will crash
I hope you can see why adding more detail would help to decide on this case.
Then we can decide if it is:
a) it is really really important: drive this together through FFe process now and SRU process later
b) it is nice, but not strictly required: then let us just have it flow in via qemu >=5.1 in 21.04 please