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

Re: [Xen-users] DomUs crash on reboot

To: Olivier Le Cam <Olivier.LeCam@xxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] DomUs crash on reboot
From: Nico Kadel-Garcia <nkadel@xxxxxxxxx>
Date: Tue, 06 May 2008 09:38:38 +0100
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 06 May 2008 01:40:14 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=jsvm0x/OukWNxA8q5HHXJU8e54Vzh+/KtMElwaIzQVo=; b=fQomFHYmcsusoSdv8df25JSu55K38SC/NwR/II8ixzL6lOLCrxu9fU3VX1cGScT4dpRON80BY85x9eOFdRruauMpvVMJLGxjSFdV2nuP/CjCPnV5HmO/495pe4F+vHfldC8h0ALIn8E4anuOaOELAxRMGcfSQRxgqUoKFE54LM4=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=ceVr00wNG0yxQUyoAlFkuhE5p4xUSyTR7TCfRIEiNpc0k2K2O/HrvY2RGJe09zA9RqHQnI9oRlTa2UbWz37uStyQ1Hc2DPIQt94Lj9MAVl7JGF3QVyTwIEghvsrXr5IlFI9J9HRFD/CcWvRJ8pp0EQQPbyMhr1LQddp/hIIMTiE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <481FF65C.2060701@xxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <481FF65C.2060701@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.14 (Windows/20080421)
Olivier Le Cam wrote:
lestat thor wrote on Apr 26, 2007:

> I'm using my dom0 on a RHLE 4.4 with xen 3.0.4-1.
> My domUs work on the same O/S, and any virtual disk is composed by 5 files : > disk = [ 'file:/hawai/domains/vm113_112/boot.img,sda2,w','file:/hawai/domains/vm113_112/racine.img,sda1,w','file:/hawai/domains/vm113_112/save.img,sda3,w','file:/hawai/domains/vm113_112/logs.img,sda4,w','file:/hawai/domains/vm113_112/swap.img,sda5,w' ]
>
>
> I created some domUs on my host and they work perfectly.
>
>
> But, when I reboot my domUs, sometimes they crash ...
>
> This is the error :
>
> XENBUS: Timeout connecting to device: device/vbd/2049 (state 3)
> XENBUS: Timeout connecting to device: device/vbd/2051 (state 3)
> XENBUS: Timeout connecting to device: device/vbd/2050 (state 3)
> ...

I'm experiencing a similar problem with a debian/etch xen host. Kernel is 2.6.18-6-xen-amd64 with the Steve Kemp's xen-utils-3.1.3-1 backport.

Devices are LVMs partitions from a SAN FC storage.

I've try with various device names, like xvd* but this didn't help. Part of my domU config file is:

root        = '/dev/xvda2 ro'
disk        = [
                  'phy:/dev/vg_domUs/nunki-swap,xvda1,w',
                  'phy:/dev/vg_domUs/nunki-root,xvda2,w',
                  'phy:/dev/vg_domUs/nunki-var,xvda3,w',
                  'phy:/dev/vg_domUs/nunki-usr,xvda4,w',
                  'phy:/dev/vg_domUs/nunki-tmp,xvda5,w',
                  'phy:/dev/vg_domUs/nunki-home,xvda6,w',
                  'phy:/dev/vg_domUs/nunki-var-log,xvda7,w',
                  'phy:/dev/vg_wdatas/www,xvdb1,w!'
              ]

(xvdb1 is an OCFS2 clustered partition which explains the w!)

Any idea will be greatly appreciated!
Besides upgrading to RHEL 5, as fast as you can? Or to CentOS 5?

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

<Prev in Thread] Current Thread [Next in Thread>