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] xm list d flag?

To: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] xm list d flag?
From: Anthony Liguori <aliguori@xxxxxxxxxx>
Date: Sat, 01 Oct 2005 14:45:35 -0500
Cc: Rusty Russell <rusty@xxxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Christian Limpach <Christian.Limpach@xxxxxxxxxxxx>
Delivery-date: Sat, 01 Oct 2005 19:43:15 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20051001144045.GA12651@xxxxxxxxxxxxxxxx>
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: <1128169060.3668.177.camel@xxxxxxxxxxxxxxxxxxxxxx> <20051001144045.GA12651@xxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.6 (X11/20050912)
Ewan Mellor wrote:

A "dying" domain is one that completed shutdown (be it a halt, reboot, crash,
or suspend) and that Xen is trying to destroy.  If it cannot destroy it, then
that means that someone is holding references to pages that belong to it.  For
example, if a driver backend fails to die, then the domain will stay around
(probably indefinitely).  Such an occurrence is a bug.
One thing to consider is having the drivers destroy the backend devices on a @releaseDomain watch instead of on the front-end path disappearing.

@releaseDomain wasn't available when the drivers were first written so it wasn't an option then.

This means that Xend does not have to be involved at all in device tear-down (except for the higher level stuff when the domain goes away completely).

This should more or less solve the zombie domain problem for good.

Thoughts?

Regards,

Anthony Liguori

Ewan.

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



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

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