RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 619345 - RFE: Enable coredump capture in the appliance
Summary: RFE: Enable coredump capture in the appliance
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libguestfs
Version: 6.2
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Richard W.M. Jones
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 619334
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-29 10:24 UTC by Matthew Booth
Modified: 2011-06-12 18:24 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 619334
Environment:
Last Closed: 2011-06-12 18:24:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Matthew Booth 2010-07-29 10:24:50 UTC 
+++ This bug was initially created as a clone of Bug #619334 +++

Description of problem:

It should be possible to enable coredump capture in the appliance.  This
would allow us to more easily debug certain problems without requiring
'printf' statements as now.

It would work something like this:

(1) Add a handle variable called 'coredump' /
  LIBGUESTFS_COREDUMP=<path>

(2) This sets a kernel parameter for the appliance.

(3) If the kernel parameter is set then the daemon enables coredumps:

  (a) echo /sysroot/<path>/core.%t.%e > /proc/sys/kernel/core_pattern
  (b) Set ulimit core unlimited

(4) After something coredumps (even the daemon) this ought to
  capture the coredump on the currently mounted device.

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

1.5.x

--- Additional comment from rjones on 2010-07-29 06:05:35 EDT ---

I wonder if we can coredump to a raw disk?  Then the user could
add a "coredump capture disk".

--- Additional comment from mbooth on 2010-07-29 06:15:30 EDT ---

Unless we plan to turn this on by default, this is really a developer tool. I think we can assume to a significant extent that the user understands exactly how it works and what the implications of using it are. This would include, for example, choosing a sensible value for LIBGUESTFS_COREDUMP for the current image file. I'd keep this one simple.
Comment 1 Matthew Booth 2010-07-29 10:25:52 UTC 
Cloning this here because I think this will be an essential support tool.
Comment 2 Richard W.M. Jones 2010-11-24 09:06:12 UTC 
Postponing to 6.2 since we have no idea how to implement this
upstream.

6.1 will include the unsupported debug core_pattern feature
which Marek is using.
Comment 3 Richard W.M. Jones 2011-03-17 10:58:00 UTC 
I posted a patch to the kernel which works rather
nicely.  However at present it seems unlikely to
be accepted.

http://lkml.org/lkml/2011/3/16/201
Comment 4 Richard W.M. Jones 2011-03-24 17:17:11 UTC 
Note to self on why using core_pattern is unlikely
to work for us:
https://rwmj.wordpress.com/2010/08/03/linux-core_pattern-fail/#content
Comment 6 Richard W.M. Jones 2011-06-12 18:06:28 UTC 
After further "discussions" with kernel developers, they're
not interested in fixing the broken core_pattern interface.
Barring some major revolution, this can't be done.
Comment 7 RHEL Program Management 2011-06-12 18:24:48 UTC 
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.
Note You need to log in before you can comment on or make changes to this bug.