Bug 614476
| Summary: | Implement xen_panic_block notifier for RHEL6 Xen guests | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Dave Anderson <anderson> | ||||
| Component: | kernel | Assignee: | Don Dutile (Red Hat) <ddutile> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Chao Ye <cye> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 6.0 | CC: | clalance, drjones, lwang, phan, qcai, syeghiay, yuzhang | ||||
| 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-11-11 16:10:40 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: | |||||||
| Attachments: |
|
||||||
|
Description
Dave Anderson
2010-07-14 14:55:00 UTC
Dave and I went over this, and the above is exactly right. In arch/x86/xen/enlighten.c, xen registers a crash_shutdown callback in the machine_ops structure. However, the callback is only ever called *if* kexec is configured, which is not the case in a xen PV guest. Therefore, we need to implement a panic notifier block; if crash_kexec() fails (which it will in the Xen PV case), then the panic notifier list will be run, at which point we will do the appropriate crash hypercall. Note that this is analogous to the situation in RHEL-5, where a crash_kexec() and the panic notifier blocks behave similarly. Chris Lalancette *** Bug 523132 has been marked as a duplicate of this bug. *** This issue has been proposed when we are only considering blocker issues in the current Red Hat Enterprise Linux release. It has been denied for 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. ** setting exception flag & rhel6.0.0 flags to ? dont see blocker flag box to set to ? to get reviewed. Posting (simple) patches shortly. Created attachment 432516 [details]
Patch to provide xen dump when xen guest crashes
Posted patch attached
Patch(es) available on kernel-2.6.32-52.el6 QA verified this bug on RHEL5.5 Xen host with the latest RHEL6 guest(20100805.0).
xen and kernel-xen packages:
kernel-xen-devel-2.6.18-206.el5
xen-3.0.3-115.el5
xen-debuginfo-3.0.3-115.el5
xen-devel-3.0.3-115.el5
kernel-xen-2.6.18-206.el5
xen-libs-3.0.3-115.el5
RHEL6 guest kernel:
2.6.32-59.el6.i686
Steps:
(1) enable "enable-dump" in xend-config.sxp and restart xend
(2) In the guest(RHEL6 HVM 32 and 64 bit guest, RHEL6 PV 32 bit guest),
# echo c > /proc/sysrq-trigger
(3) The guest crashes with call trace
We could find core dump files in the directory /var/lib/xen/dump/ for the crashed guest.
For RHEL6 64 bit PV guest, there is a bug(BZ#621846) which will result in guest crashing at boot time. So there is dump core file generated automatically whenever you try to create such a guest.
Change this bug to VERIFIED.
Red Hat Enterprise Linux 6.0 is now available and should resolve the problem described in this bug report. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you. |