From: Anthony Liguori <aliguori@us.ibm.com>
To: "Christopher S. Aker" <caker@theshore.net>
Cc: Ian Pratt <m+Ian.Pratt.m+Ian.Pratt@cl.cam.ac.uk>,
xen-devel@lists.xensource.com
Subject: Re: DomU stuck in "s" state in -unstable
Date: Thu, 21 Apr 2005 23:40:46 -0500 [thread overview]
Message-ID: <4268804E.20803@us.ibm.com> (raw)
In-Reply-To: <001a01c546db$fa42c870$0201a8c0@hawk>
Christopher S. Aker wrote:
>>Yep, this is understood. Mike's preparing a big update to xend
>>(basically a rewrite) that fixes this and a bunch of other problems.
>>Stay tuned.
>>
>>
>
>Cool. Wasn't sure if this was a xend problem specifically, since vmtools won't
>destroy the domain either.
>
>
A domain won't disappear until all of the memory mapped from the domain
is unmapped. The culprit here is either xcs or the device backends
themself. It's not really harmful to the system to have these domains
not totally destroyed (most of the memory has been reclaimed) but it is
annoying.
xcs is pretty good about eventually cleaning itself up so it's probably
the devices not being properly destroyed. One of the features I'm
working on for vm-tools is the ability to remove devices manually (after
domain destruction).
This will provide a way to recover from this sort of thing in the future.
Regards,
Anthony Liguori
>-Chris
>
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>
>
>
next prev parent reply other threads:[~2005-04-22 4:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-22 0:32 DomU stuck in "s" state in -unstable Ian Pratt
2005-04-22 1:38 ` Christopher S. Aker
2005-04-22 4:40 ` Anthony Liguori [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-22 0:28 Christopher S. Aker
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=4268804E.20803@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=caker@theshore.net \
--cc=m+Ian.Pratt.m+Ian.Pratt@cl.cam.ac.uk \
--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.