Latest revision as of 13:09, 4 May 2009

Description

This test case verifies that a crash dump can be generated for a Fedora Xen DomU.

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
```
Once the domU has crashed, reboot it.
Inside the guest, install the kernel debuginfo for the kernel, along with the crash utility.
Copy the kernel core-file from the dom0 to the domU (or export it via NFS, etc.)

Inside the guest, run

crash /usr/lib/debug/../vmlinux /path/to/corefile

The guest should crash, and the dom0 should take over and dump a core.
The crash utility should be able to recognize the domU core file and perform basic operations on it.

@@ Line 4: / Line 4: @@
 # 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>
+# Once the domU has crashed, reboot it.
+# Inside the guest, install the kernel debuginfo for the kernel, along with the crash utility.
+# Copy the kernel core-file from the dom0 to the domU (or export it via NFS, etc.)
+# Inside the guest, run <pre>crash /usr/lib/debug/../vmlinux /path/to/corefile</pre>
+# Run a few crash commands, like <code>bt -a</code>, <code>ps</code>, etc.
 |results=
 # The guest should crash, and the dom0 should take over and dump a core.
+# The crash utility should be able to recognize the domU core file and perform basic operations on it.
 }}
 [[Category:Virtualization XenDomU Test Cases|Crash dump]]