Unable to configure kdump on a VMWare virtual guest running Oracle Linux 6.10
(Doc ID 2554666.1)
Last updated on MAY 15, 2020
Applies to:Linux OS - Version Oracle Linux 6.10 and later
On an Oracle Linux 6.10 system, kdump fails to collect a vmcore, even though it has been configured in the standard way, and there is enough space free under /var/crash to save a vmcore.
The system is a VMWare virtual guest.
When testing kdump via Alt-SysRq commands, kdump is started (as seen in the example logs below), however post reboot, there is no vmcore from the crash found on the system.
Apr 1 12:05:29 <hostname> kdump: kexec: loaded kdump kernel
Apr 1 12:05:29 <hostname> kdump: started up
Apr 1 12:05:29 <hostname> abrtd: Init complete, entering main loop
Apr 1 12:05:40 <hostname> kernel: Hangcheck: starting hangcheck timer 0.9.1 (tick is 30 seconds, margin is 180 seconds).
Apr 1 12:05:40 <hostname> kernel: Hangcheck: Using getrawmonotonic().
Apr 1 12:14:48 <hostname> kernel: imklog 5.8.10, log source = /proc/kmsg started. <---- server restart post reboot
Apr 1 12:14:48 <hostname> rsyslogd: [origin software="rsyslogd" swVersion="5.8.10" x-pid="2070" x-info="http://www.rsyslog.com"] start
Apr 1 12:14:48 <hostname> kernel: Initializing cgroup subsys cpuset
Apr 1 12:14:48 <hostname> kernel: Initializing cgroup subsys cpu
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