From: Dan Smith <danms@us.ibm.com>
To: Ted Kaczmarek <tedkaz@optonline.net>
Cc: xen-devel@lists.xensource.com
Subject: Re: xm destroy changeset 6831
Date: Mon, 19 Sep 2005 14:20:51 -0700 [thread overview]
Message-ID: <87mzm869fw.fsf@us.ibm.com> (raw)
In-Reply-To: 1126787974.4140.17.camel@pluto.linsolutions.com
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
next prev parent reply other threads:[~2005-09-19 21:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 12:39 xm destroy changeset 6831 Ted Kaczmarek
2005-09-19 21:20 ` Dan Smith [this message]
2005-09-20 0:20 ` Ted Kaczmarek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mzm869fw.fsf@us.ibm.com \
--to=danms@us.ibm.com \
--cc=tedkaz@optonline.net \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.