All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Wright <anthony@overnetdata.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Domains not being destroyed properly
Date: Tue, 21 Jun 2011 13:57:20 +0100	[thread overview]
Message-ID: <4E009530.2040108@overnetdata.com> (raw)
In-Reply-To: <1308657108.6920.25.camel@zakaz.uk.xensource.com>

On 21/06/2011 12:51, Ian Campbell wrote:
> On Fri, 2011-06-17 at 12:29 +0100, Anthony Wright wrote:
>> 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.
> The -e option to xl create means don't daemonize to babysit this domain.
> One of the key bits of functionality of the daemon is to destroy the
> domain after it is shutdown. So if you use -e you need to do the destroy
> manually. So effectively you have gotten what you asked for ;-)
>
However I can't destroy the domain with 'xl destroy'. The command runs,
but the domain is still there afterwards.
>> 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.
> You can take a xenstore watch on the @releaseDomain pseudo node, does
> that do what you want?
>
I found the @releaseDomain xenstore watch, and have modified my code to
use it. I was wondering if there's a mechanism to find out which domain
is dying. The only mechanism I can find at the moment is to scan through
all the domains to see which one isn't there any more. Assuming 'xl
destroy' works, it would make things a little easier. Is there a better
way to get the domain states other than doing a 'xl list' and parsing
the result?

thanks,

Anthony.

  reply	other threads:[~2011-06-21 12:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-17 11:29 Domains not being destroyed properly Anthony Wright
2011-06-17 18:12 ` Nathan March
2011-06-21 11:51 ` Ian Campbell
2011-06-21 12:57   ` Anthony Wright [this message]
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=4E009530.2040108@overnetdata.com \
    --to=anthony@overnetdata.com \
    --cc=Ian.Campbell@citrix.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.