From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: DomU stuck in "s" state in -unstable Date: Thu, 21 Apr 2005 23:40:46 -0500 Message-ID: <4268804E.20803@us.ibm.com> References: <001a01c546db$fa42c870$0201a8c0@hawk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <001a01c546db$fa42c870$0201a8c0@hawk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Christopher S. Aker" Cc: Ian Pratt , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Christopher S. Aker wrote: >>Yep, this is understood. Mike's preparing a big update to xend >>(basically a rewrite) that fixes this and a bunch of other problems. >>Stay tuned. >> >> > >Cool. Wasn't sure if this was a xend problem specifically, since vmtools won't >destroy the domain either. > > A domain won't disappear until all of the memory mapped from the domain is unmapped. The culprit here is either xcs or the device backends themself. It's not really harmful to the system to have these domains not totally destroyed (most of the memory has been reclaimed) but it is annoying. xcs is pretty good about eventually cleaning itself up so it's probably the devices not being properly destroyed. One of the features I'm working on for vm-tools is the ability to remove devices manually (after domain destruction). This will provide a way to recover from this sort of thing in the future. Regards, Anthony Liguori >-Chris > > >_______________________________________________ >Xen-devel mailing list >Xen-devel@lists.xensource.com >http://lists.xensource.com/xen-devel > > >