Messages in this thread | | | Date | Thu, 16 Feb 2012 18:15:34 -0500 | From | Dave Jones <> | Subject | soft lockup detector & virtualisation |
| |
Lately I've noticed quite a few soft lockup bugs being reported. In many of them, they're coming from inside virtual guests.
Is the softlockup detector fundamentally broken in this situation ?
If the host doesn't schedule the guest for whatever reason, or the user suspends the VM and resumes it later ?
Here's the most recent example: https://bugzilla.redhat.com/attachment.cgi?id=563767
In many of these, the code where it's "stuck" isn't anything special, which is why I think the guest just hasn't had a timeslice in 185 seconds.
Is there some way we can perhaps detect we're running virtualised, and disable the detector automatically ?
thoughts ?
Dave
| |