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.
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
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 message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
F11 hit EOL 6 months ago and this issue should be resolved now anyway. Closing as CURRENTRELEASE.