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 byXendCheckpoi

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

> > > > > 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.
> 
> Hmm.. Guess I need to retry with the latest then - do you happen to know
> if any fixes were made after 3.0.2? As I recall, the specific area we
> had problems with was in migration to a node that has had xend
> restarted... I will rerun our tests and report any issues I come across.

I'd expect that to work, and I don't know of any fixes in that area.
xm-test does some tests to see whether xend still functions after xend
is restarted, though I don't know whether that includes a migration.
Let me know how you get on.

Ewan.

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

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