[Xen-users] What behaviour in PV DomU can lead to a complete Dom0 hung/crash?

[Sergi Seira <s.seira@xxxxxxxxx>]

Hello,

I'm experiencing complete system blocking (unable to write anything via
keyboard console on Dom0) under circumstances other than high
load/cpu/networking (software versions below).
There are 10 debian etch DomU's running game server software
(precompiled binaries srcds_amd (counterstrike source) and steam software).
Dom0 is also debian etch (debian_version 4.0).

I have many other xen-servers (Dom0) with the very same software and
hardware but running other Dom0 servers (no counterstrike's; mysql,
spamassasins, webproxys, apaches, ...) under serious load and their
uptime can be hundreds of days.

I am wondering what can interfere so deep from a DomU as to hang the
complete system.

I can't see anything in log files or detecting strange behaviour in rrd
graphs (munin).

Maybe I am missing some log debug that should be activated in order to
point out the cause of all evil.

My system configuration:

# dpkg -l | grep xen
ii  libxenstore3.0                   
3.2.1-2                              Xenstore communications library for Xen
ii  linux-headers-2.6.26-1-common-xen
2.6.26-10                            Common header files for Linux
2.6.26-1-xen
ii  linux-headers-2.6.26-1-xen-amd64 
2.6.26-10                            Header files for Linux
2.6.26-1-xen-amd64
ii  linux-image-2.6.18-5-xen-amd64   
2.6.18.dfsg.1-13etch6                Linux 2.6.18 image on AMD64
ii  linux-image-2.6.18-6-xen-amd64   
2.6.18.dfsg.1-23                     Linux 2.6.18 image on AMD64
ii  linux-image-2.6.26-1-xen-amd64   
2.6.26-8                             Linux 2.6.26 image on AMD64
ii  linux-modules-2.6.18-5-xen-amd64 
2.6.18.dfsg.1-13etch6                Linux 2.6.18 modules on AMD64
ii  linux-modules-2.6.18-6-xen-amd64 
2.6.18.dfsg.1-23                     Linux 2.6.18 modules on AMD64
ii  linux-modules-2.6.26-1-xen-amd64 
2.6.26-8                             Linux 2.6.26 modules on AMD64
ii  xen-hypervisor-3.2-1-amd64       
3.2.1-2                              The Xen Hypervisor on AMD64
ii  xen-tools                        
3.9-4                                Tools to manage Debian XEN virtual
servers
ii  xen-utils-3.2-1                  
3.2.1-2                              XEN administrative tools
ii  xen-utils-common                 
3.2.0-2                              XEN administrative tools - common files
ii  xenstore-utils                   
3.2.1-2                              Xenstore utilities for Xen


# xm info
host                   : g01xen02
release                : 2.6.18-6-xen-amd64
version                : #1 SMP Wed Oct 15 11:49:51 UTC 2008
machine                : x86_64
nr_cpus                : 8
nr_nodes               : 1
cores_per_socket       : 4
threads_per_core       : 1
cpu_mhz                : 2010
hw_caps                :
178bf3ff:efd3fbff:00000000:00000110:00802001:00000000:000007ff
total_memory           : 16383
free_memory            : 15637
node_to_cpu            : node0:0-7
xen_major              : 3
xen_minor              : 2
xen_extra              : -1
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
cc_compiler            : gcc version 4.3.1 (Debian 4.3.1-2)
cc_compile_by          : waldi
cc_compile_domain      : debian.org
cc_compile_date        : Sat Jun 28 09:32:18 UTC 2008
xend_config_format     : 4

I'm going to try to move forward to xen 3.3 and hope it'll be resolved,
but any directions to discover what's happening now will be welcome,
thanks
Sergi

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users