From Fedora Project Wiki
(stub out this page) |
No edit summary |
||
Line 2: | Line 2: | ||
|description=This test case verifies that a crash dump can be generated for a Fedora Xen DomU. | |description=This test case verifies that a crash dump can be generated for a Fedora Xen DomU. | ||
|actions= | |actions= | ||
# | # Make sure your dom0 is configured to automatically dump core when a guest crashes. This is typically set in the /etc/xen/xend-config.sxp file; you'll need to change the parameter <code>#(enable-dump no)</code> to <code>(enable-dump yes)</code>, and restart xend on the dom0. | ||
# Inside the guest, run <pre>$> echo c > /proc/sysrq-trigger</pre> | |||
|results= | |results= | ||
# | # The guest should crash, and the dom0 should take over and dump a core. | ||
}} | }} | ||
[[Category:Virtualization XenDomU Test Cases|Crash dump]] | [[Category:Virtualization XenDomU Test Cases|Crash dump]] |
Revision as of 12:52, 4 May 2009
Description
This test case verifies that a crash dump can be generated for a Fedora Xen DomU.
How to test
- Make sure your dom0 is configured to automatically dump core when a guest crashes. This is typically set in the /etc/xen/xend-config.sxp file; you'll need to change the parameter
#(enable-dump no)
to(enable-dump yes)
, and restart xend on the dom0. - Inside the guest, run
$> echo c > /proc/sysrq-trigger
Expected Results
- The guest should crash, and the dom0 should take over and dump a core.