WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Xen 3.4.3 - randomly crash of Dom0 and DomU

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Xen 3.4.3 - randomly crash of Dom0 and DomU
From: Felix Botner <botner@xxxxxxxxxxxxx>
Date: Thu, 3 Jun 2010 10:05:27 +0200
Delivery-date: Mon, 14 Jun 2010 08:04:58 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.10 (enterprise35 20100115.1075236)
Hi everyone,

from time to time (but at least one crash in 24h) the system crashes (neither 
Dom0 nor DomU is accessible via network or console) with no usefull 
information in any log file and i have no idea what the problem could be.
Log files (syslog, kern.log, messages, xend.log) on both systems, Dom0 and 
DomU, show nothing, no kernel oops or anything.

The setup is:

   * a Dom0 (64Bit) with a 2.6.32-xen, Debian Sid based kernel 
     (linux-source-2.6.32 2.6.32-13) with xen-3.4.3 (build with 
     the standard options)

   * and one paravirtualized Debian Etch based linux DomU (32Bit) with a
     Debian Etch based kernel 2.6.18-xen (also tried other Debian Lenny based 
     DomU Kernels, 2.6.26-xen and 2.6.30-xen)

   * DomU's network interface is connected via bridge

   * xen.independent_wallclock=1 and ntpd in DomU (due to many
    "clocksource/2: Time went backwards" log messages)

   DomU cgf:
     name = 'name'
     kernel = "/opt/ucs2.2_xen/vmlinuz-2.6.18-ucs153-xen-686"
     memory = 2500
     vcpus = 1
     disk = ['file:/var/lib/xen/name/disk,xvda,w' ]
     vif = [ 'mac=00:16:3e:8e:8b:08' ]
     boot = 'd'
     ramdisk = "/opt/ucs2.2_xen/initrd.img-2.6.18-ucs153-xen-686"
     root = "/dev/xvda1 ro"
     extra = 'xencons=tty console=hvc0'

   Dom0 /etc/xen/xend-config.sxp:
     (xen-api-server ((unix)))
     (xend-http-server no)
     (xend-unix-server no)
     (xend-unix-xmlrpc-server yes)
     (xend-tcp-xmlrpc-server no)
     (xend-relocation-server no)
     (xend-relocation-ssl-server no)
     (network-script network-bridge)
     (vif-script vif-bridge)
     (dom0-min-mem 196)
     (enable-dom0-ballooning yes)
     (dom0-cpus 0)
     (vncpasswd '')

Is there any known problem running a 32Bit DomU in a 64 Bit Dom0?
Could anyone give me a hint, how to debug this situation or where i can find 
more information?

Feel free to ask for more information about the system or the setup.

Many thanks

-- 
Felix Botner

Open Source Software Engineer

Univention GmbH
Linux for your business
Mary-Somerville-Str.1
28359 Bremen
Tel. : +49 421 22232-0
Fax : +49 421 22232-99

botner@xxxxxxxxxxxxx>
http://www.univention.de

Geschäftsführer: Peter H. Ganten
HRB 20755 Amtsgericht Bremen
Steuer-Nr.: 71-597-02876 

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