Daniel Bradler
2014-Jul-29 19:44 UTC
[CentOS-virt] Frequent Kernel Oops' on CentOS 6 / Xen
Hi,
we have a couple of nodes based on CentOS 6 and Xen4CentOS. Unfortunately
some of these nodes keep crashing frequenly.
We use the latest versions:
# uname -r
3.10.43-11.el6.centos.alt.x86_64
# xm info
host : vserver20
release : 3.10.43-11.el6.centos.alt.x86_64
version : #1 SMP Mon Jun 16 14:22:02 UTC 2014
machine : x86_64
nr_cpus : 24
nr_nodes : 2
cores_per_socket : 6
threads_per_core : 2
cpu_mhz : 2400
hw_caps :
bfebfbff:2c100800:00000000:00003f40:009ee3fd:00000000:00000001:00000000
virt_caps : hvm hvm_directio
total_memory : 65527
free_memory : 22692
free_cpus : 0
xen_major : 4
xen_minor : 2
xen_extra : .4-33.el6
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : unavailable
xen_commandline : dom0_mem=2560M,max:3072M loglvl=all
guest_loglvl=all
cc_compiler : gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-4)
cc_compile_by : mockbuild
cc_compile_domain : centos.org
cc_compile_date : Mon Jun 16 17:22:14 UTC 2014
xend_config_format : 4
Our configuration looks as follows:
Grub:
title CentOS (3.10.43-11.el6.centos.alt.x86_64)
root (hd0,1)
kernel /xen.gz dom0_mem=2560M,max:3072M loglvl=all guest_loglvl=all
module /vmlinuz-3.10.43-11.el6.centos.alt.x86_64 ro root=/dev/sda1
KEYBOARDTYPE=pc KEYTABLE=de-latin1-nodeadkeys crashkernel=auto
module /initramfs-3.10.43-11.el6.centos.alt.x86_64.img
/etc/xen/xend-config.sxp
(xend-unix-server yes)
(xend-relocation-server no)
(xend-relocation-hosts-allow '^localhost$ ^localhost\\.localdomain$')
(network-script network-bridge)
(vif-script vif-bridge)
(dom0-min-mem 1024)
(enable-dom0-ballooning no)
(total_available_memory 0)
(dom0-cpus 0)
(vncpasswd '')
I've attached the logfile information regarding the latest crash as
crash.log?
Does anybody has an idea how to solve these issues?
Kind Regards
Daniel Bradler
-------------- next part --------------
A non-text attachment was scrubbed...
Name: crash.log
Type: text/x-log
Size: 9750 bytes
Desc:
URL:
<http://lists.centos.org/pipermail/centos-virt/attachments/20140729/274a5272/attachment-0006.bin>
On Tue, Jul 29, 2014 at 3:44 PM, Daniel Bradler <daniel at bradler.com> wrote:> Hi, > > we have a couple of nodes based on CentOS 6 and Xen4CentOS. Unfortunately > some of these nodes keep crashing frequenly. > > We use the latest versions: > > # uname -r > 3.10.43-11.el6.centos.alt.x86_64 > > # xm info > host : vserver20 > release : 3.10.43-11.el6.centos.alt.x86_64 > version : #1 SMP Mon Jun 16 14:22:02 UTC 2014 > machine : x86_64 > nr_cpus : 24 > nr_nodes : 2 > cores_per_socket : 6 > threads_per_core : 2 > cpu_mhz : 2400 > hw_caps : > bfebfbff:2c100800:00000000:00003f40:009ee3fd:00000000:00000001:00000000 > virt_caps : hvm hvm_directio > total_memory : 65527 > free_memory : 22692 > free_cpus : 0 > xen_major : 4 > xen_minor : 2 > xen_extra : .4-33.el6 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=0xffff800000000000 > xen_changeset : unavailable > xen_commandline : dom0_mem=2560M,max:3072M loglvl=all > guest_loglvl=all > cc_compiler : gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-4) > cc_compile_by : mockbuild > cc_compile_domain : centos.org > cc_compile_date : Mon Jun 16 17:22:14 UTC 2014 > xend_config_format : 4 > > Our configuration looks as follows: > > Grub: > > title CentOS (3.10.43-11.el6.centos.alt.x86_64) > root (hd0,1) > kernel /xen.gz dom0_mem=2560M,max:3072M loglvl=all guest_loglvl=all > module /vmlinuz-3.10.43-11.el6.centos.alt.x86_64 ro root=/dev/sda1 > KEYBOARDTYPE=pc KEYTABLE=de-latin1-nodeadkeys crashkernel=auto > module /initramfs-3.10.43-11.el6.centos.alt.x86_64.img > > /etc/xen/xend-config.sxp > > (xend-unix-server yes) > (xend-relocation-server no) > (xend-relocation-hosts-allow '^localhost$ ^localhost\\.localdomain$') > (network-script network-bridge) > (vif-script vif-bridge) > (dom0-min-mem 1024) > (enable-dom0-ballooning no) > (total_available_memory 0) > (dom0-cpus 0) > (vncpasswd '') > > I've attached the logfile information regarding the latest crash as > crash.log?Thanks for this report -- would it be possible to get a full console log from boot? -George