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.

+++ This bug was initially created as a clone of Bug #499648 +++

Description of problem:
I'm following the test case here: https://fedoraproject.org/wiki/QA:Testcase_Virtualization_XenDomU_Crash_dump

While trying to make the F-11 Xen domU take a crashdump using:

# echo c > /proc/sysrq-trigger

all I get is a message on the console like:

SysRq : Trigger a crashdump

Looking at dmesg, I also see this:
Kexec: Warning: crash image not loaded

However, for a Xen domU, we don't need a kexec crash image loaded; we just have to inform the hypervisor that we are crashing, and the dom0 will take an image of memory for us.

--- Additional comment from clalance on 2009-05-08 11:19:09 EDT ---

Miroslav,
     If you have time to look at this, this would be a good bug to fix in upstream and then port into Fedora.  The ability to crash dump is very important for debugging future issues.

Chris Lalancette

--- Additional comment from fedora-triage-list on 2009-06-09 11:20:41 EDT ---


This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Still need to come up with the best way to deal with this. Will do as work for 6.1.

*** Bug 607949 has been marked as a duplicate of this bug. ***

This should be resolved by bug 614476 when the work for that is completed. Dupping.

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