From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: xm list d flag? Date: Sat, 01 Oct 2005 14:45:35 -0500 Message-ID: <433EE75F.9090606@us.ibm.com> References: <1128169060.3668.177.camel@pluto.linsolutions.com> <20051001144045.GA12651@uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20051001144045.GA12651@uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ewan Mellor Cc: Rusty Russell , xen-devel@lists.xensource.com, Christian Limpach List-Id: xen-devel@lists.xenproject.org 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@lists.xensource.com >http://lists.xensource.com/xen-devel > > >