2020-12-10 11:59:22 |
bugproxy |
bug |
|
|
added bug |
2020-12-10 11:59:24 |
bugproxy |
tags |
|
architecture-s39064 bugnameltc-190224 severity-high targetmilestone-inin--- |
|
2020-12-10 11:59:25 |
bugproxy |
ubuntu: assignee |
|
Skipper Bug Screeners (skipper-screen-team) |
|
2020-12-10 11:59:32 |
bugproxy |
affects |
ubuntu |
qemu (Ubuntu) |
|
2020-12-10 12:33:30 |
Dan Streetman |
bug |
|
|
added subscriber Guilherme G. Piccoli |
2020-12-10 12:33:37 |
Dan Streetman |
bug |
|
|
added subscriber Dan Streetman |
2020-12-10 12:34:26 |
Frank Heimes |
qemu (Ubuntu): assignee |
Skipper Bug Screeners (skipper-screen-team) |
Canonical Server Team (canonical-server) |
|
2020-12-10 12:34:57 |
Frank Heimes |
bug task added |
|
ubuntu-z-systems |
|
2020-12-10 12:35:34 |
Frank Heimes |
nominated for series |
|
Ubuntu Groovy |
|
2020-12-10 12:35:34 |
Frank Heimes |
bug task added |
|
qemu (Ubuntu Groovy) |
|
2020-12-10 12:35:34 |
Frank Heimes |
nominated for series |
|
Ubuntu Hirsute |
|
2020-12-10 12:35:34 |
Frank Heimes |
bug task added |
|
qemu (Ubuntu Hirsute) |
|
2020-12-10 12:35:34 |
Frank Heimes |
nominated for series |
|
Ubuntu Focal |
|
2020-12-10 12:35:34 |
Frank Heimes |
bug task added |
|
qemu (Ubuntu Focal) |
|
2020-12-10 12:35:53 |
Frank Heimes |
ubuntu-z-systems: assignee |
|
Skipper Bug Screeners (skipper-screen-team) |
|
2020-12-10 12:35:59 |
Frank Heimes |
ubuntu-z-systems: importance |
Undecided |
High |
|
2020-12-10 12:36:10 |
Frank Heimes |
ubuntu-z-systems: status |
New |
Triaged |
|
2020-12-10 12:37:21 |
Frank Heimes |
bug |
|
|
added subscriber Christian Ehrhardt |
2020-12-10 13:23:34 |
Christian Ehrhardt |
tags |
architecture-s39064 bugnameltc-190224 severity-high targetmilestone-inin--- |
architecture-s39064 bugnameltc-190224 qemu-21.04 severity-high targetmilestone-inin--- |
|
2020-12-10 13:30:26 |
Christian Ehrhardt |
qemu (Ubuntu Hirsute): status |
New |
In Progress |
|
2020-12-10 15:09:31 |
bugproxy |
attachment added |
|
Sample Guest XML https://bugs.launchpad.net/bugs/1907656/+attachment/5442524/+files/kexec-test.xml |
|
2020-12-10 15:27:17 |
Frank Heimes |
ubuntu-z-systems: status |
Triaged |
In Progress |
|
2020-12-11 08:42:53 |
Christian Ehrhardt |
qemu (Ubuntu Groovy): status |
New |
Triaged |
|
2020-12-11 08:42:55 |
Christian Ehrhardt |
qemu (Ubuntu Focal): status |
New |
Triaged |
|
2020-12-17 10:32:38 |
Launchpad Janitor |
qemu (Ubuntu Hirsute): status |
In Progress |
Fix Released |
|
2020-12-17 10:32:38 |
Launchpad Janitor |
cve linked |
|
2020-15859 |
|
2020-12-17 10:32:38 |
Launchpad Janitor |
cve linked |
|
2020-17380 |
|
2020-12-17 10:32:38 |
Launchpad Janitor |
cve linked |
|
2020-25084 |
|
2020-12-17 10:32:38 |
Launchpad Janitor |
cve linked |
|
2020-25085 |
|
2020-12-17 10:32:38 |
Launchpad Janitor |
cve linked |
|
2020-25624 |
|
2020-12-17 10:32:38 |
Launchpad Janitor |
cve linked |
|
2020-25625 |
|
2020-12-17 10:32:38 |
Launchpad Janitor |
cve linked |
|
2020-25707 |
|
2020-12-17 10:32:38 |
Launchpad Janitor |
cve linked |
|
2020-25723 |
|
2020-12-17 10:32:38 |
Launchpad Janitor |
cve linked |
|
2020-27616 |
|
2020-12-17 10:32:38 |
Launchpad Janitor |
cve linked |
|
2020-27617 |
|
2020-12-17 10:32:38 |
Launchpad Janitor |
cve linked |
|
2020-27661 |
|
2020-12-17 10:32:38 |
Launchpad Janitor |
cve linked |
|
2020-27821 |
|
2020-12-17 10:32:38 |
Launchpad Janitor |
cve linked |
|
2020-28916 |
|
2021-01-05 14:48:13 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/395786 |
|
2021-01-05 14:57:12 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/395787 |
|
2021-01-06 09:31:53 |
Christian Ehrhardt |
description |
Description: s390x/s390-virtio-ccw: Reset PCI devices during subsystem reset
Symptom: PCI devices are unavailable after a subsystem reset
Problem: When a subsystem reset event occurs (e.g. via kexec) PCI
devices are not being reset and are therefore in an
unexpected state when the guest attempts to enable them
again after the subsystem reset. This results in the devices
being unavailable to the guest until a reboot.
Solution: Add the s390 PCI host bridge to the list of devices to be
reset during a subsystem reset event
Reproduction: kexec on an s390x guest with PCI devices
db08244a3a7e s390x/s390-virtio-ccw: Reset PCI devices during subsystem reset
This fix need to be applied to qemu for focal (20.04) and groovy (20.10). |
[Impact]
Symptom: PCI devices are unavailable after a subsystem reset
Problem: When a subsystem reset event occurs (e.g. via kexec) PCI
devices are not being reset and are therefore in an
unexpected state when the guest attempts to enable them
again after the subsystem reset. This results in the
[Test Case]
# Prep a guest and wait until it booted
$ apt install uvtool-libvirt
$ uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily "arch=s390x" label=daily "release=focal"
$ uvt-kvm create --disk 5 --password=ubuntu testguest release=focal arch=s390x label=daily
$ virsh console testguest
# lspci in guest shows nothing yet (expected)
# Add virtio device
$ cat > virtio-pci.xml << EOF
<interface type='network'>
<source network='default'/>
<model type='virtio'/>
<address type='pci'/>
<rom bar='off' file=''/>
</interface>
EOF
$ virsh attach-device testguest virtio-pci.xml
# lspci in guest now shows the device
ubuntu@testguest:~$ lspci
0001:00:00.0 Ethernet controller: Red Hat, Inc. Virtio network device
# verify that a "normal" reboot does not loose the device
ubuntu@testguest:~$ sudo reboot
...
ubuntu@testguest:~$ lspci
0001:00:00.0 Ethernet controller: Red Hat, Inc. Virtio network device
# Kexec into a kernel (can be the same)
ubuntu@testguest:~$ sudo apt install kexec-tools
ubuntu@testguest:~$ sudo kexec --load /boot/vmlinuz --initrd=/boot/initrd.img --append="$(cat /proc/cmdline)"
ubuntu@testguest:~$ sudo kexec --exec
# Log in and recheck lspci - it will be empty (wrong)
# With the Fix that will show the pci device again
ubuntu@testguest:~$ lspci
# Note: A Reboot will get the device back (in old and new case)
[Where problems could occur]
* The patch is gladly small - it affects the list of devices that will
be reset them. By extending this list obivously more devices will be
reset - therefore the activity of a "subsystem_reset" will cover more
devices.
Regressions (let us hope not) would happen there. For example think
there is a buggy PCI device that no one cared about before. Formerly it
would not have been reset, but now it is. If that reset fails badly you
have a regression.
Fortunately PCI devices are still uncommon on s390x, so even if (I
doubt) there is a regression it would affect a small fraqction of users
only.
These kind of resets happen on load (kexec, reboot, start) and that is
the place to look out for regressions.
[Other Info]
* n/a
---
Description: s390x/s390-virtio-ccw: Reset PCI devices during subsystem reset
Symptom: PCI devices are unavailable after a subsystem reset
Problem: When a subsystem reset event occurs (e.g. via kexec) PCI
devices are not being reset and are therefore in an
unexpected state when the guest attempts to enable them
again after the subsystem reset. This results in the devices
being unavailable to the guest until a reboot.
Solution: Add the s390 PCI host bridge to the list of devices to be
reset during a subsystem reset event
Reproduction: kexec on an s390x guest with PCI devices
db08244a3a7e s390x/s390-virtio-ccw: Reset PCI devices during subsystem reset
This fix need to be applied to qemu for focal (20.04) and groovy (20.10). |
|
2021-01-06 16:43:08 |
Frank Heimes |
qemu (Ubuntu Groovy): status |
Triaged |
In Progress |
|
2021-01-06 16:43:14 |
Frank Heimes |
qemu (Ubuntu Focal): status |
Triaged |
In Progress |
|
2021-01-08 13:48:05 |
Timo Aaltonen |
qemu (Ubuntu Groovy): status |
In Progress |
Fix Committed |
|
2021-01-08 13:48:07 |
Timo Aaltonen |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
2021-01-08 13:48:11 |
Timo Aaltonen |
bug |
|
|
added subscriber SRU Verification |
2021-01-08 13:48:16 |
Timo Aaltonen |
tags |
architecture-s39064 bugnameltc-190224 qemu-21.04 severity-high targetmilestone-inin--- |
architecture-s39064 bugnameltc-190224 qemu-21.04 severity-high targetmilestone-inin--- verification-needed verification-needed-groovy |
|
2021-01-08 13:50:19 |
Timo Aaltonen |
qemu (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
2021-01-08 13:50:29 |
Timo Aaltonen |
tags |
architecture-s39064 bugnameltc-190224 qemu-21.04 severity-high targetmilestone-inin--- verification-needed verification-needed-groovy |
architecture-s39064 bugnameltc-190224 qemu-21.04 severity-high targetmilestone-inin--- verification-needed verification-needed-focal verification-needed-groovy |
|
2021-01-08 14:04:30 |
Frank Heimes |
ubuntu-z-systems: status |
In Progress |
Fix Committed |
|
2021-01-08 20:47:07 |
Frank Heimes |
tags |
architecture-s39064 bugnameltc-190224 qemu-21.04 severity-high targetmilestone-inin--- verification-needed verification-needed-focal verification-needed-groovy |
architecture-s39064 bugnameltc-190224 qemu-21.04 severity-high targetmilestone-inin--- verification-done verification-done-focal verification-done-groovy |
|
2021-01-18 17:06:50 |
Launchpad Janitor |
qemu (Ubuntu Groovy): status |
Fix Committed |
Fix Released |
|
2021-01-18 17:07:02 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
2021-01-18 17:08:35 |
Launchpad Janitor |
qemu (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
2021-01-18 18:43:42 |
Frank Heimes |
ubuntu-z-systems: status |
Fix Committed |
Fix Released |
|
2021-01-19 10:00:26 |
bugproxy |
tags |
architecture-s39064 bugnameltc-190224 qemu-21.04 severity-high targetmilestone-inin--- verification-done verification-done-focal verification-done-groovy |
architecture-s39064 bugnameltc-190224 qemu-21.04 severity-high targetmilestone-inin2104 verification-done verification-done-focal verification-done-groovy |
|