From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ted Kaczmarek Subject: Re: xm destroy changeset 6831 Date: Mon, 19 Sep 2005 20:20:55 -0400 Message-ID: <1127175655.23958.76.camel@pluto.linsolutions.com> References: <1126787974.4140.17.camel@pluto.linsolutions.com> <87mzm869fw.fsf@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7BIT Return-path: In-reply-to: <87mzm869fw.fsf@us.ibm.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: Dan Smith Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Mon, 2005-09-19 at 14:20 -0700, Dan Smith wrote: > TK> Test Case - try to start Domu without valid root filesystem, > TK> crashes on boot. > > TK> xm destroy will not get rid of the domain, but, restarting xend > TK> appears to clean things up, with previous builds I would still see > TK> the crashed domain floating around after a restart. > > Is this still an issue for you? I was unable to reproduce using the > following changeset: > > changeset: 6951:d1cbfaf804d98aec913ad57e3531d45c6459b366 > tag: tip > user: kaf24@firebug.cl.cam.ac.uk > date: Mon Sep 19 10:10:20 2005 > summary: Add lomount to 'make uninstall' target. Remove ... > > When I create a domain with an invalid root filesystem, it disappears > from "xm list" as soon as it crashes. Since 6902 I have been unable to reproduce this, the list's appears to be borked as I posted positive results on this issue and they never hit. Regards, Ted