similar to: [patch] kexec and kdump documentation for xen

I seem to be struggling with setting up kdump to debug Xen/dom0 freeze. According to http://xenbits.xen.org/docs/unstable/misc/kexec_and_kdump.txt the "crashkernel=" parameter must be passed to the Xen hypervisor. When it is passed to Xen I dont see "Crash Kernel" under System RAM in /proc/iomem inside dom0. I am missing something obvious here. Could someone please explain why

upstream commit 7e96287ddc4f42081e18248b6167041c0908004c Author: Vivek Goyal <vgoyal@in.ibm.com> [PATCH] kdump: introduce "reset_devices" command line option Resetting the devices during driver initialization can be a costly operation in terms of time (especially scsi devices). This option can be used by drivers to know that user forcibly wants the devices to

Howdy, Running a round of updates from 6.3 to 6.4 and I'm seeing the following on all the servers. Want to make sure I'm not going to end up with a kernel panic if I reboot into the new kernel or have any other issues. Apr 22 11:10:21 www kdump: kexec: unloaded kdump kernel Apr 22 11:10:21 www kdump: stopped Apr 22 11:10:21 www kdump: mkdumprd: failed to make kdump initrd Apr 22

Kexec / Kdump - xen-3.0.4-testing-13098 Kexec Kexec Kexec Kexec Kdump Hardware Xen -> Xen -> bzImage -> Xen -> Xen -> Arch Platform Xen bzImage Xen vmlinux vmlinux i386 A PASS PASS PASS PASS PASS i386 B (VMX) PASS PASS PASS PASS

I need to make a decision on the configuration of the kdump location for a bunch of new machines. It seems like using a raw partition directly is the safest choice, right? If I configure it to dump vmcore on a filesystem, and the filesystem gets corrupted somehow, then the dump will fail. Same for network-based dumps (the remote end may be unavailable due to a number of reasons). The local

Requires "kdump support" patch for ovirt-node Signed-off-by: Alan Pevec <apevec at redhat.com> --- common-blacklist.ks | 2 +- common-pkgs.ks | 2 ++ ovirt-node-image.ks | 10 +++++++++- 3 files changed, 12 insertions(+), 2 deletions(-) diff --git a/common-blacklist.ks b/common-blacklist.ks index 2452237..af7fa07 100644 --- a/common-blacklist.ks +++

> On 12/26/2012 06:18 PM, Daniel Kiper wrote: > > Add i386 kexec/kdump implementation. > > > > v2 - suggestions/fixes: > > - allocate transition page table pages below 4 GiB > > (suggested by Jan Beulich). > > Why? Sadly all addresses are passed via unsigned long variable to kexec hypercall. Daniel

> On 12/26/2012 06:18 PM, Daniel Kiper wrote: > > Add i386 kexec/kdump implementation. > > > > v2 - suggestions/fixes: > > - allocate transition page table pages below 4 GiB > > (suggested by Jan Beulich). > > Why? Sadly all addresses are passed via unsigned long variable to kexec hypercall. Daniel

This removes the custom kdump configurations by emptying the configuration file /etc/kdump.conf. Signed-off-by: Wanlong Gao <gaowanlong@cn.fujitsu.com> --- sysprep/Makefile.am | 1 + sysprep/sysprep_operation_kdump_config.ml | 44 +++++++++++++++++++++++++++++++ 2 files changed, 45 insertions(+) create mode 100644 sysprep/sysprep_operation_kdump_config.ml diff

On 09/06/2013 04:06 PM, Richard W.M. Jones wrote: > On Fri, Sep 06, 2013 at 03:52:40PM +0800, Wanlong Gao wrote: >> + kdump_config \ > > Better to call this one just "kdump" ? > > However I'm unclear why anyone would want to remove kdump config in a > sysprep operation. Or TCP wrappers for that matter. There seems to > be no useful point in having

CentOS Errata and Bugfix Advisory 2013:0789 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-0789.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 021d9f4df1f3b077f5f6d0da0cb60ceaea1d8bf2a3fa096e42a6634eef7e9171 system-config-kdump-1.0.14-5.el5_9.noarch.rpm x86_64:

The ‘vmware-uninstall-tools.pl’ script tries to rebuild the initrd. On SUSE, if kdump initrd has been enabled, this hangs because the ‘mkdumprd’ doesn't know what root device to use. Fix that by setting the ‘rootdev’ environment variable. --- v2v/convert_linux.ml | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/v2v/convert_linux.ml b/v2v/convert_linux.ml index

Hello, I am new in this mailing,please if somebody knows how to make kdump able to load in startup. i will be very thankful, -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20090409/d3435a68/attachment-0002.html>

hi all mine does not, and I've tampered with it in many ways, cannot get it to work. best, L.

Hi, Is there a way to specify kernel version when (re)start kdump service? Suppose I have install a new kernel and kdump will generate kdump.img for new kernel in next boot. But I want kdump to generate kdump.img for new kernel immediately, is it possible? Thanks.

> -----Original Messages----- > From: "Benjamin Hauger" <hauger at noao.edu> > Sent Time: 2019-03-27 00:15:21 (Wednesday) > To: centos at centos.org > Cc: > Subject: Re: [CentOS] How to specify kernel version when restart kdump > > kdump operates by booting a fresh kernel to capture the context of a > crashed kernel, and so the only way for kdump to

> -----Original Messages----- > From: "Benjamin Hauger" <hauger at noao.edu> > Sent Time: 2019-03-28 01:31:40 (Thursday) > To: wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn>, centos at centos.org > Cc: > Subject: Re: [CentOS] How to specify kernel version when restart kdump > > What do you mean? Wouldn't the kernel version always be the actual >

On Thu, Mar 28, 2019 at 9:24 AM Gianluca Cecchi <gianluca.cecchi at gmail.com> wrote: > > > 1) In CentOS 6 we have the classical SysV service > file: /etc/rc.d/init.d/kdump > > Supposing you have just installed 2.6.32-642.13.1.el6.x86_64 kernel > > [snip] > > and at the end it runs this command if it doesn't find one: > $MKDUMPRD $kdump_initrd

> -----Original Messages----- > From: "Gianluca Cecchi" <gianluca.cecchi at gmail.com> > Sent Time: 2019-03-28 16:59:19 (Thursday) > [...] > The command line fo CentOS 6 clearly misses the kernel version to build > initrd file for, so the correct command should be: > > /sbin/mkdumprd -d -f > "/boot/initrd-2.6.32-642.13.1.el6.x86_64kdump.img"

Hi, I update scripts which extract dom0/domU/hypervisor image from kdump''s whole-machine image. Now it supports x86_32 pae. It needs libelf and work on x86_32 platform. Converted images can be analysed by crash(dom0 or domU) or gdb(hypervisor). regards, -- Kazuo Moriwaka _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com