Bug 1057754
| Summary: | BUG: soft lockup - CPU#0 stuck for 67s! [qemu-kvm:20512] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Dan Yocum <dyocum> |
| Component: | qemu-kvm | Assignee: | Andrew Jones <drjones> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.5 | CC: | acathrow, bsarathy, drjones, juzhang, kchamart, klepikho, masao-takahashi, michen, mkenneth, qzhang, virt-maint |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-04-15 14:53:07 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Dan Yocum
2014-01-24 18:18:12 UTC
maybe relevant to this bug - these came up when I rebooted the host node and VMs: kvm: 11517: cpu0 unhandled rdmsr: 0xc0011021 kvm: 11517: cpu0 unhandled rdmsr: 0xc0010112 kvm: 11517: cpu0 unhandled rdmsr: 0xc0010001 kvm: 11517: cpu1 unhandled rdmsr: 0xc0011021 Similar soft-lockup I've seen as part of upstream QEMU/KVM testing with Intel Haswell machines: https://bugzilla.redhat.com/show_bug.cgi?id=1058209 [3.14.0-0.rc0.git9.1.fc21] Booting into a guest on Intel Haswell (bare-metal) throws soft lockups [qemu-system-x86:911] Its associated upstream Kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=69491 Just dug this BZ up out of my backlog. I checked the customer portal and see the case is closed, but grabbed the sos report anyway. However, it must not be the same one, because this sos_commands/general/dmesg is for a 2.6.32-220.el6.x86_64 kernel, not 2.6.32-358.118.1.openstack.el6.x86_64, as above. Anyway, I'd prefer they move to 6.5.z and see if it reproduces there before putting too much effort into the issue. OTOH, the dmesg in this sos report does show soft lockups for qemu-kvm, but I also see evidence that tracing was enabled at the time. So, in any case, I don't believe we have good enough information for this [now closed] customer case in order to proceed. I'm going to close as INSU for now, of course it can be reopened if necessary. (In reply to Andrew Jones from comment #4) > Just dug this BZ up out of my backlog. I checked the customer portal and see > the case is closed, but grabbed the sos report anyway. However, it must not > be the same one, because this sos_commands/general/dmesg is for a > 2.6.32-220.el6.x86_64 kernel, not 2.6.32-358.118.1.openstack.el6.x86_64, as > above. Anyway, I'd prefer they move to 6.5.z and see if it reproduces there > before putting too much effort into the issue. OTOH, the dmesg in this sos > report does show soft lockups for qemu-kvm, but I also see evidence that > tracing was enabled at the time. So, in any case, I don't believe we have > good enough information for this [now closed] customer case in order to > proceed. I'm going to close as INSU for now, of course it can be reopened if > necessary. Sounds reasonable - we're now at RHELv6.5 and kernel on the compute nodes ad the kernel is 2.6.32-431.5.1.el6.x86_64 and we haven't seen the soft-lockup since, I don't think. |