Skip to contentSkip to conversation

soft lockup detector & virtualisation

DISCUSSION Dave Jones 3 participants 3 messages Feb 16, 2012 – Feb 17, 2012

lore
Share & tools
lore

Dave Jones

author
#0 lore raw

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

#1 lore raw
Quoted 11 lines · Dave Jones

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

Quoted 6 lines

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 ?

I think Eric's work (See "Add check for suspended vm in softlockup detector" sent out today) tries to address this issue.

thanks
-john

#2 lore raw
Quoted 16 lines · john stultz
Quoted 15 lines · Dave Jones

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.

Quoted 8 lines
Quoted 2 lines

Is there some way we can perhaps detect we're running virtualised, and disable the detector automatically ?

I think Eric's work (See "Add check for suspended vm in softlockup detector" sent out today) tries to address this issue.

thanks
-john

The work I have been doing specifically handles the case where the hypervisor suspends the guest. There is talk of extending that work to handle preemption as well, which I think will cover your use case.

Eric