Bug 616337
Summary: | guest hang when boot with nmi_watch=1 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Suqin Huang <shuang> |
Component: | kernel | Assignee: | Red Hat Kernel Manager <kernel-mgr> |
Status: | CLOSED DUPLICATE | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 6.1 | CC: | dzickus, llim, ndai, tburke |
Target Milestone: | rc | Keywords: | RHELNAK |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-07-28 12:52:37 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: | 562808, 580953 |
Description
Suqin Huang
2010-07-20 08:10:00 UTC
This issue has been proposed when we are only considering blocker issues in the current Red Hat Enterprise Linux release. ** If you would still like this issue considered for the current release, ask your support representative to file as a blocker on your behalf. Otherwise ask that it be considered for the next Red Hat Enterprise Linux release. ** Did you mean to say you used 'nmi_watchdog=1' on the command line? That is not expected to work for KVM (or any virt guests really) as the ioapic timer interrupts aren't emulated as nmi's to the guest. Though I wouldn't expect it to hang because with nmi_watchdog autodetection, and the fact there is no emulated performance counters, it defaults to the equivalent of nmi_watchdog=1. In that case you just see an error message and the kernel proceeds forward. So the priority should be low for this as it isn't expected to be a valid user configuration. But it might be a bug that will need to be fixed somewhere. *** This bug has been marked as a duplicate of bug 616296 *** |