[20.10 FEAT] KVM: Enable Channel Path Handling for vfio-ccw (kernel)
Bug #1887931 reported by
bugproxy
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu on IBM z Systems |
Fix Released
|
High
|
Skipper Bug Screeners | ||
| linux (Ubuntu) |
Fix Released
|
Undecided
|
Skipper Bug Screeners | ||
Bug Description
Without support for channel path handling changes in the host's channel path for underlying CCW devices may go unnoticed by the guest. This could cause erroneous operation and lead to a crashing guest. Therefore it is necessary to ensure proper handling of channel paths in vfio-ccw, like passing through channel path operations and notification of channel path changes.
Business Case:
Enhance RAS characteristics of guests using passed-through CCW devices.
Feature request for kernel.
Target kernel >= 5.9, therefore backport required
| tags: | added: architecture-s39064 bugnameltc-186729 severity-high targetmilestone-inin2010 |
| Changed in ubuntu: | |
| assignee: | nobody → Skipper Bug Screeners (skipper-screen-team) |
| affects: | ubuntu → linux (Ubuntu) |
Revision history for this message
| Frank Heimes (fheimes) wrote | #1 |
| Changed in ubuntu-z-systems: | |
| status: | New → Incomplete |
| importance: | Undecided → High |
| assignee: | nobody → Skipper Bug Screeners (skipper-screen-team) |
| summary: |
- [20.10 FEAT[KVM: Enable Channel Path Handling for vfio-ccw (kernel) + [20.10 FEAT [KVM: Enable Channel Path Handling for vfio-ccw (kernel) |
| summary: |
- [20.10 FEAT [KVM: Enable Channel Path Handling for vfio-ccw (kernel) + [20.10 FEAT] KVM: Enable Channel Path Handling for vfio-ccw (kernel) |
Revision history for this message
| bugproxy (bugproxy) wrote Comment bridged from LTC Bugzilla | #2 |
Revision history for this message
| Frank Heimes (fheimes) wrote | #3 |
| Changed in linux (Ubuntu): | |
| status: | New → Fix Released |
| Changed in ubuntu-z-systems: | |
| status: | Incomplete → Fix Released |
Revision history for this message
| bugproxy (bugproxy) wrote | #4 |
| information type: | Private → Public |
To post a comment you must log in.
Changing to Incomplete until code got upstream released (and potential backport was made available, in case cherry-pick is not possible).
Please notice that this can be very tight in time for groovy, since you mentioned that the code will land in "kernel >= 5.9".