From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dan Smith <danms@us.ibm.com>
Subject: Re: xm destroy changeset 6831
Date: Mon, 19 Sep 2005 14:20:51 -0700
Message-ID: <87mzm869fw.fsf@us.ibm.com>
References: <1126787974.4140.17.camel@pluto.linsolutions.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Ted Kaczmarek <tedkaz@optonline.net>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

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.

-- 
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms@us.ibm.com