similar to: Xen dom0 crash log

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

Hi, this is my first post in this list. I''m trying to run Xen 4.1.1 with Gentoo (Linux 3.3.8) as Dom0, however it crashes and prints stack trace for swapper/0 process. I can''t read anything since stack trace fills the screen and can''t scroll up to see preceding messages (even with noreboot parameter). How can I read the output? I only have one computer with me so

Hello, I have experienced a dom0 crash where the system became unreachable via the network and the console was unresponsive. I would appreciate help interpretting the logs and any configuration change suggestions. It is a stock Debian Lenny dom0 running xen 3.2.1 with kernel 2.6.26-2-xen-amd64 and an AMD Athlon IIx4 with 4 GB of RAM. It is running 4 VMs. One VM has two PCI NICs being

Hi, After reading XenServer documents and debugging, I found the previous configuration is correct, here is the one I've configured to work: In XCP, as in XenServer, system's network configuration doesn't really matter, it only make sense before XCP starts and handles the network settings. So there is no need to configure VLAN on host machine, and you only need a minimal one active

This issue came up when debugging pcpu linked list corruption (patches for that issue to follow). -- Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer T: +44 (0)1223 225 900, http://www.citrix.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel

Hi all, I recently had an issue where, running kernel 2.6.32-358.11.1, the box would be up for about five minutes, then would crash and reboot. kdump saved the vmcore files, so I was hoping to run crash against them to see why this was occurring. I copied the vmcores to another machine, installed the kernel-debuginfo package, and gave it a try, but had no success: $ crash

OS: CentOS 6.5 Crash: crash-7.1.0-6.el6.x86_64 Kdump: kexec-tools-2.0.0-273.el6.x86_64 GDB: gdb-7.2-60.el6_4.1.x86_64 /etc/kdump.conf: core_collector makedumpfile -c --message-level 1 -d 31 Kernel crashed by panic("string"), but I can't see any register in vmcore: crash> bt PID: 53331 TASK: ffff880c523ed540 CPU: 2 COMMAND: "bw_sd-ar-7-0_2" #0 [ffff880c4f12f978]

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

Hello. Is it available a communication interface between Dom0 and DomU to get some parameteres about DomU without connection via ssh? For example i need to get information about IP addresses that are allocated in DomU. I found following mail-thread: http://xen.1045712.n5.nabble.com/How-to-get-domU-IP-address-td2510278.html Keir Fraser said about xenstore, but as i understand to use xenstore

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

This caused particularly poor performance when booting a server in uniprocessor mode for debugging reasons, and had 4 dom0 vcpus competing for 1pcpus worth of time. -- Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer T: +44 (0)1223 225 900, http://www.citrix.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel

On Thu, Mar 28, 2019 at 6:55 AM wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn> wrote: > > -----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

kdump operates by booting a fresh kernel to capture the context of a crashed kernel, and so the only way for kdump to dump a kernel is to crash it and cause kdump to invoke its post-crash kernel. You can manually force a running kernel to panic (and invoke a correctly-configured kdump) with the following command sequence: > echo 1 > /proc/sys/kernel/sysrq > echo c >

> -----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 >

I have just successfully installed CentOS5 beta from CDs. No major issues so far, but it is still too fresh to say anything. The machine I used is peculiar. By peculiar I mean it won't boot if I use grub (this is a long story by itself). So, I manually installed lilo to boot the system. The only problem is that I could not use kdump. It produced an error saying "No bootloader config

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

> -----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

What do you mean? Wouldn't the kernel version always be the actual running version of the kernel that was booted? Ben On 3/26/19 6:16 PM, wuzhouhui wrote: >> -----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]

Add guide to using the kexec and kdump facility in xen. Signed-off-by: Simon Horman <horms@verge.net.au> --- I the work on this document using an ia64 machine and qemu emulating x86_32. I am yet to verify it on x86_32 hardware or x86_64. Index: xen-unstable.hg/docs/misc/kexec_and_kdump.txt =================================================================== --- /dev/null 1970-01-01

Hi all I want to upgrade from 4.5-RELEASE to 4.8-STABLE. I cvsup-ed the source tree and then in /usr/src do 'make -j4 buildworld'. But there was an error during make. here is the dump: ... ===> usr.bin/kdump cc -O -pipe -march=pentium -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin cc -O -pipe -march=pentium -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin gzip -cn