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: "Daniel P. Berrange" <berrange@xxxxxxxxxx>, "Ewan Mellor" <ewan@xxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Trivial patch to fix logging level output by XendCheckpoint.py
From: "Graham, Simon" <Simon.Graham@xxxxxxxxxxx>
Date: Tue, 21 Nov 2006 09:58:33 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 21 Nov 2006 06:58:45 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AccNaSra9mXdMOouQ4qf7Dp6IYJuAQAEroig
Thread-topic: [Xen-devel] Trivial patch to fix logging level output by XendCheckpoint.py
> > > 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. I will look into modifying
the test so it kills the main xend process instead to more accurately
test fault insertion in xend.

> While XenD itself can easily be restarted it does cause a few problems
> if you have any HVM domains, or paravirt + blktap domains running.
XenD
> is the parent process for both qemu-dm and tapdisk helper processes.
It
> appears that these two are incapable of detecting shutdown of the
guest
> they are associated with themselves, and instead rely on XenD to tell
> them when to exit / kill them. So the problem is, that if you restart
> XenD these processes get re-parented to init, and then when you
> shutdown
> the guest domain, the qemu-dm/tapdisk helpers stay around causing the
> domain to linger in zombie state forever.
> 
> If we could figure out how to sort this, then XenD would be trivially
> restartable without any ill effects.
> 

Ah - OK, well, we aren't testing HVM guests yet but we will be;
hopefully one of us can figure out how to solve this issue.

Simon

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