SUSE Support

Here When You Need Us

Configure XEN Dom0 for a kernel dump

This document (7001383) is provided subject to the disclaimer at the end of this document.


SUSE Linux Enterprise Server 11 Service Pack 3 (SLES 11 SP3)
SUSE Linux Enterprise Server 10 Service Pack 2 (SLES 10 SP2)


Dom0 on a SLES 10 XEN server is crashing/panicking.


  1. Update the server to SLES 10 SP2 or newer and corresponding XEN packages (required).  Always review the update notes as it may be necessary to update any SLES Virtual Machines (and Virtual Machine Driver Pack installs on any VMs) prior to the XEN Host (dom0) update;  Especially if updating the XEN Host from SLES 10 (pre SP1).
  2. Configure dom0 for kdump
    1. Install the Yast2-kdump package on the XEN Host (dom0)
    2. Configure dom0 for a kernel dump
      1. From Yast2 > System > Kernel Kdump
        1. Enable Kdump (keep defaults)
      2. From Yast2 > System > Boot Loader
        1. Highlight the XEN kernel, then click Edit
        2. Cut and paste the crashkernel bootloader argument from the "Optional Kernel Command Line Parameter" section to the "Additional Xen Hypervisor Parameters" section
        3. Note that for Xen on SLES 11, the syntax  is still crashkernel=size@offset - e.g. crashkernel=512M@16M
          So you may need to modify the argument from the native kernel when appending it to the xen.gz options.
  3. Note:  The makedumpfile tool currently only supports the "ELF" format and a dumplevel setting of "0".  Check /etc/sysconfig/kdump file and verify KDUMP_DUMPLEVEL="0" and KDUMP_DUMPFORMAT="ELF". As of 2014 this is still the case for the current SLE versions.  SUSE engineering has developed fixes to the makedumpfile and kdump packages for SLE 11 SP3, which allow setting the dumplevel to "1" to at least allow some level of page filtering to take place. These patches are expected to get released with our maintenance stream. Should a customer have an urgent need for this functionality in the interim period, please open a service request with SUSE support and refer to bug 864910.
  4. Test by triggering a kernel dump
    1. Shutdown all VMs and reboot the VM Server
    2. From a terminal on dom0 run echo c > /proc/sysrq-trigger
  5. Note:  The system will become unresponsive until the core is written.  When focus returns, verify that a vmcore has been written to the /var/log/dump directory.

Additional Information

See TID 3374462:  Configure kernel core dump capture for more kdump info
See Troubleshooting a privileged (Dom0) Xen kernel for information on pre-SP2 XEN kernels.


This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7001383
  • Creation Date: 17-Sep-2008
  • Modified Date:03-Mar-2020
    • SUSE Linux Enterprise Server

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.