DescriptionChris Lalancette
2009-09-14 08:34:51 UTC
+++ 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
Comment 1RHEL Program Management
2009-09-14 08:49:45 UTC
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.