Hi,
the patches LGTM and I'll make it part of the Ubuntu builds.
One question thou: on one hand "occasionally end up with" sounds like this is
almost impossible to explicitly test, but then the attached debug patch
suggests there might be a way to trigger this through protvirt.
But even if that is the case backporting it to all kind of older versions there
is no protvirt.
So I wanted to ask:
a) is there any way to reliably trigger this for A/B testing of the fix as far
back as qemu 2.5?
b) how real is the danger to hit and consequences of this in the pre-protvirt
(=<Focal) era?
** Also affects: qemu (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu Xenial)
Status: New => Incomplete
** Changed in: qemu (Ubuntu Bionic)
Status: New => Incomplete
** Changed in: qemu (Ubuntu Focal)
Status: New => Triaged
** Changed in: qemu (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: qemu (Ubuntu)
Importance: Undecided => High
** Changed in: qemu (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894942
Title:
[UBUNTU 20.04] Lost virtio host --> guest notifications cause devices
to cease normal operation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1894942/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
