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-devel

Re: [Xen-devel] Trivial patch to fix logging level output by XendCheckpo

To: "Graham, Simon" <Simon.Graham@xxxxxxxxxxx>
Subject: Re: [Xen-devel] Trivial patch to fix logging level output by XendCheckpoint.py
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Tue, 21 Nov 2006 15:05:47 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Delivery-date: Tue, 21 Nov 2006 07:05:54 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <342BAC0A5467384983B586A6B0B3767104190414@xxxxxxxxxxxxxxxxxxxxx>
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: <342BAC0A5467384983B586A6B0B3767104190414@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Tue, Nov 21, 2006 at 09:58:33AM -0500, Graham, Simon wrote:

> > > > Well, I didn't expect this much discussion!!! I must admit I found
> > it
> > > > hard to grok this code initially but I think the idea of exec'ing
> a
> > > > separate program is a good one to avoid the chance that xend can
> > die
> > > > (especially since you don't currently seem to be able to restart
> > xend
> > > > without rebooting Dom0).
> > >
> > > That's not true -- Xend ought to be restarting itself (it forks
> > itself so that
> > > it has a monitor process) and even then "xend restart" ought to
> work.
> > Are you
> > > having trouble with that?
> > >
> > > The one process that we can't restart at the moment is xenstored.
> > Everything
> > > else should be fine.
> >
> 
> Yes we have had problems with this (in 3.0.2) -- however, we test this
> with /etc/init.d/xend stop/start which will, I think, restart xenstored
> as well, so I guess this still does not work.

No, /etc/init.d/xend stop doesn't (shouldn't) stop xenstored.

Ewan.

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