Kdump kernel hangs when using iommu=soft

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

Environment

SUSE Linux Enterprise Server 10 SP2

Situation

SLES10 SP2 in VMWare ESX 3.5 VMs (4vCPU with 8GB) are hanging, when vmlinux has been
booted with iommu=soft. The problem only happens with more than 2vCPUs or 2.5GB of RAM.
When booting with iommu=soft (enabling swiotlb) the kernel will not fit into 64M.

Resolution

To get kdump to work in an ESX VM when vmxnet is in use and the kernel is
booted with iommu=soft:
Configure more crashkernel space. 
Change the default crashkernel=64M@16M to crashkernel=128M@16M

Disclaimer

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:7002635
  • Creation Date: 14-Mar-2009
  • Modified Date:24-Feb-2021
    • SUSE Linux Enterprise Server

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback@suse.com

SUSE Support Forums

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

Join Our Community

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.


SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

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

Go to Customer Center