Bug 557044
Summary: | Kdump cause guest hang and qemu takes up 100% cpu | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Yolkfull Chow <yzhou> |
Component: | kvm | Assignee: | Zachary Amsden <zamsden> |
Status: | CLOSED WORKSFORME | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.5 | CC: | christian, llim, ndai, tburke, virt-maint, ykaul |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-04-16 02:53:51 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: | 580948 |
Description
Yolkfull Chow
2010-01-20 08:56:25 UTC
based on the information in this bug report, it isn't clear if a 32-bit or 64-bit guest kernel was tried. It is clear, however, this is a kexec bug and NOT a timer IRQ related issue. I'll attempt to reproduce on 32/64 regardless. Tested 32-bit: appeared to have booted into crash kernel. I've never actually done this before so I'm not 100% sure what so expect, but the system rebooted again right after that. Unfortunately, can't log in because of an unrelated disk space issue, but the system did not get stuck. worth noting, my guest kernel is 2.6.18-164.el5, so it is possible this is some kind of regression. Tested 64-bit: crash kernel is working just fine. I'll try with RHEL-5.5 beta guest kernels to rule out a regression, but it looks like this bug might have already been squashed - could have been a reboot issue or something fixed in KVM since 83-147. 32-bit crash kernel works fine after upgrade to RHEL-5-5 beta (2.6.18-194.el5) So does 64-bit. So it's not a kernel regression, nor is the bug found in recent KVM. Closing as unable to reproduce. |