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/
Home Products Support Community News


Re: [Xen-devel] xend bug? restart = 'never'

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] xend bug? restart = 'never'
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Mon, 10 Oct 2005 23:45:04 +0100
Delivery-date: Mon, 10 Oct 2005 22:42:33 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20051010194105.GA6264@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <434AB8C1.3070502@xxxxxxx> <20051010194105.GA6264@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Mon, Oct 10, 2005 at 08:41:05PM +0100, Ewan Mellor wrote:

> On Mon, Oct 10, 2005 at 02:53:53PM -0400, Jonathan M. McCune wrote:
> > Hello,
> > 
> > I'm observing a situation where domU crashes and xend continuously tries 
> > to restart it.  For example, I have to write commands like this to 
> > actually get it to stop:
> > 
> > for i in `seq 80 90`; do xm destroy $i; done
> > 
> > I've tried adding restart = "never" and restart = 'never' to the domain 
> > config file (the file that gets passed to `xm create`).  Is this a known 
> > issue?  Am I doing something wrong?
> It's a bug.  Please use the new config options on_poweroff, on_reboot, and
> on_crash (documented in the example configuration files in
> tools/examples/xmexample{1,2,3}).  We are supposed to be backwards compatible
> with the old restart option, but that is clearly broken.

Also, xm shutdown --halt should override any restarting configuration, and
definitively halt the domain.


Xen-devel mailing list