From: Anthony Wright <anthony@overnetdata.com>
To: xen-devel@lists.xensource.com
Subject: Domains not being destroyed properly
Date: Fri, 17 Jun 2011 12:29:20 +0100 [thread overview]
Message-ID: <4DFB3A90.70707@overnetdata.com> (raw)
If I create a domain with 'xl create -e', and then shut the domain down
with 'xl shutdown' according to 'xl list' it gets stuck in state
'--ps-d', with a name of '(none)' and 0 ram, ('xm list' doesn't show the
domain).
If I destroy the domain with 'xl destroy' the domain is destroyed properly.
If I create a domain with 'xl create' (without the '-e' option) and then
use 'xl shutdown', the domain is destroyed properly.
Since the 'xl shutdown' & 'xl destroy' give different results I presume
this is a bug.
As an extra question... Is there a way to be notified when a domain is
destroyed other than leaving the 'xl create' process lying around? I'd
like to know when any domain is destroyed, and leaving a large number of
processes lying around just to be able to do this seems rather ugly. In
the past I've editted some of the python code to achieve this, but my
patch doesn't work with 4.1, so I'm seeing if there's an official way to
do this before I work out a new patch.
thanks,
Anthony.
next reply other threads:[~2011-06-17 11:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 11:29 Anthony Wright [this message]
2011-06-17 18:12 ` Domains not being destroyed properly Nathan March
2011-06-21 11:51 ` Ian Campbell
2011-06-21 12:57 ` Anthony Wright
2011-06-21 13:13 ` Ian Jackson
2011-06-21 13:39 ` Konrad Rzeszutek Wilk
2011-06-21 14:52 ` Anthony Wright
2011-06-21 15:44 ` Ian Campbell
2011-06-21 16:04 ` Anthony Wright
2011-06-22 7:56 ` Ian Campbell
2011-06-24 12:54 ` Anthony Wright
2011-06-24 13:01 ` Tim Deegan
2011-06-24 13:36 ` Anthony Wright
2011-06-24 14:21 ` Ian Campbell
2011-06-24 13:45 ` Ian Campbell
2011-06-24 14:15 ` Anthony Wright
2011-06-24 14:24 ` Ian Campbell
2011-06-21 16:26 ` Ian Jackson
2011-06-21 16:42 ` Ian Campbell
2011-06-21 17:01 ` Keir Fraser
2011-06-21 19:35 ` Tim Deegan
2011-06-22 8:02 ` Ian Campbell
2011-06-21 13:27 ` Ian Jackson
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=4DFB3A90.70707@overnetdata.com \
--to=anthony@overnetdata.com \
--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.