Bug 607949 - No core file was generated when RHEL 6 PV guest crashed
Summary: No core file was generated when RHEL 6 PV guest crashed
Status: CLOSED DUPLICATE of bug 523132
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: xen   
(Show other bugs)
Version: 5.6
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Xen Maintainance List
QA Contact: Virtualization Bugs
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-25 09:30 UTC by Yufang Zhang
Modified: 2010-11-09 12:41 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-28 17:21:34 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
screen dump of the guest when it crashes (3.41 KB, text/plain)
2010-06-25 09:35 UTC, Yufang Zhang
no flags Details

Description Yufang Zhang 2010-06-25 09:30:16 UTC
Description of problem:
For RHEL6 PV guest, no core file was generated automatically when the guest crashed, even core-dumps had been enabled in xend-config.sxp.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. enable core-dumps and restart xend
2. create a RHEL 6 PV guest
3. force the guest to crash within the guest via:
echo c > /proc/sysrq-trigger
Actual results:
The guest does crash but no core file is generated.

Expected results:
core file should be generated automatically when the guest crashes.

Additional info:
screen dump of the guest is in the attachment.

Comment 1 Yufang Zhang 2010-06-25 09:35:01 UTC
Created attachment 426812 [details]
screen dump of the guest when it crashes

Comment 2 Lei Wang 2010-06-25 10:04:36 UTC
Same problem occur for RHEL6 HVM guest.

With same version xen package,
and kernel-xen version is:  2.6.18-194.6.1.el5

Comment 3 Andrew Jones 2010-06-28 17:21:34 UTC
To test if the host's userspace can create core files correctly, then the dump should be initiated with 'xm dump-core' or 'virsh dump'. This appears to work correctly (although crash has a problem reading PV guest dumps: bug 608779).

When initiating a crash with 'echo c > /proc/sysrq-trigger' this is testing the "kexec" path in the guest kernel. This is known not to work, see bug 523132.

I'll dup this bug against the kexec bug. If this was really a test of the host userspace, then it should be closed as NOTABUG due to using the wrong mechanism.

*** This bug has been marked as a duplicate of bug 523132 ***

Note You need to log in before you can comment on or make changes to this bug.