My Oracle Support Banner

Configuring Kdump on Exalogic Virtual OL6 Based UEK4 Dom0 Compute Nodes (Doc ID 2704455.1)

Last updated on NOVEMBER 14, 2022

Applies to:

Oracle Exalogic Elastic Cloud Software - Version and later
Linux x86-64
Oracle Virtual Server x86-64


This document illustrates how to configure the KDUMP utility to capture a vmcore file in response to a kernel panic.

The procedure to configure Kdump described in this document applies to the Exalogic Virtual release/PSU versions.


Exalogic Virtual racks running with Virtual release/PSU versions.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
 1) Validate that kexec-tools and busybox rpms are installed on OL6 dom0 compute nodes. 
 2) Take backup of grub, kdump and sysctl configuration files on Dom0 compute node.
 3) Update /etc/default/grub to add crashkernel=384M@64M parameter.
 4) Update /etc/sysconfig/kdump file and add iommu=off parameter
 5) Identify the UUID of /ssd on Dom0 compute node.
 6) Update /etc/kdump.conf to make Kdump configuration changes.
 7) Enable KDump to start on Compute Node reboot.
 8) Propagate the grub file changes to add crashkernel settings.
 9) Update /etc/sysctl.conf file and add "kernel.unknown_nmi_panic = 1" entry
 10) Reboot the Compute Node.
 11) Validate KDump Configuration changes are in effect after reboot.
 12) Test KDump Configuration on Dom0 Compute Node
 13) Validate VM Core file is generated from KDump Configuration test under /ssd.

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.