Bug 652187
Summary: | BUG: soft lockup - CPU#1 stuck for 13s after saving internal snapshot | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Shirley Zhou <szhou> | ||||||
Component: | kvm | Assignee: | Zachary Amsden <zamsden> | ||||||
Status: | CLOSED DUPLICATE | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 5.5.z | CC: | bcao, gcosta, mkenneth, mshao, virt-maint, ykaul | ||||||
Target Milestone: | rc | ||||||||
Target Release: | --- | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2010-11-24 16:57:56 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Bug Depends On: | |||||||||
Bug Blocks: | 580946 | ||||||||
Attachments: |
|
Description
Shirley Zhou
2010-11-11 10:12:57 UTC
Created attachment 459713 [details]
dmesg info
This issue also exist when guest become paused because of no space/input/output error. Attach dmesg info for reference. Created attachment 460470 [details]
dmesg info when guest become paused because of no space/input/output error
I don't think this is a bug. Yes, the CPU stops when you pause the guest, and doesn't get interrupts. Looks like we just need Glauber's patches to avoid softlockup warnings on the 5.5z guest. I don't think I have bug privs to do this, but the patches should already be in 5.7. Zach, Unless I am understanding something wrong, the softlockup happens after the savevm, but before loadvm. I'd agree it is not a bug if we were stopped for a while, then resumed. Just issuing a savevm does not sound like a reason for a softlockup, so I am assuming it is a bug. Could the reporter clarify ? (In reply to comment #6) > Zach, > > Unless I am understanding something wrong, the softlockup happens after the > savevm, but before loadvm. I'd agree it is not a bug if we were stopped for a > while, then resumed. > > Just issuing a savevm does not sound like a reason for a softlockup, so I am > assuming it is a bug. > > Could the reporter clarify ? Softlockup happens after savevm (before loadvm), and more softlockup happens after loadvm. This has been reported on the same kernel version previously and is now verified. *** This bug has been marked as a duplicate of bug 583059 *** |