Comment 3 for bug 1894942
Revision history for this message
| bugproxy (bugproxy) wrote Comment bridged from LTC Bugzilla | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
------- Comment From <email address hidden> 2020-09-09 02:50 EDT-------
> 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?
This is independent of protvirt.
uperf network workload with driver=qemu in libvirt for the network interface did trigger after some time.