From: Mike Wray <mike.wray@hpl.hp.com>
To: Stephen Childs <Stephen.Childs@cs.tcd.ie>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: Dead domains don't disappear from xm list
Date: Tue, 07 Dec 2004 16:32:49 +0000 [thread overview]
Message-ID: <41B5DB31.2010508@hpl.hp.com> (raw)
In-Reply-To: <41B5C808.8010007@cs.tcd.ie>
Stephen Childs wrote:
> Hi,
>
> When a domain shuts down it seems to stay visible in the output of xm list
> (see below) even if I do an 'xm destroy'. Has something changed (they used
> to disappear just fine for me)? I am running Xen 2.0 (fairly up-to-date).
>
>
> Name Id Mem(MB) CPU State Time(s) Console
> Domain-0 0 395 0 r---- 2377.2
> cagnode91-clone 10 199 2 -b--- 138.9 9610
> cagnode92-clone 8 199 1 -b--- 154.5 9608
> testce 18 0 1 ---s- 15.6 9618
> testce-clone 16 0 3 -b--- 155.7 9616
> testce-clone-clone 17 0 0 ---s- 98.0 9617
>
As you say, dead domains usually go away just fine.
If a domain doesn't disappear from the list, the usual
reason is that according to xen itself it still exists,
even though xend has tried to destroy it.
It's also possible there's a bug in xend.
Is there anything in /etc/log/xend.log?
(Only do this if your domains aren't important)
Do the zombie domains go away if you restart xend?
Mike
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-12-07 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-07 15:11 Dead domains don't disappear from xm list Stephen Childs
2004-12-07 16:32 ` Mike Wray [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-07 15:07 Stephen Childs
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=41B5DB31.2010508@hpl.hp.com \
--to=mike.wray@hpl.hp.com \
--cc=Stephen.Childs@cs.tcd.ie \
--cc=xen-devel@lists.sourceforge.net \
/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.