From: Dan Smith <danms@us.ibm.com>
To: Ted Kaczmarek <tedkaz@optonline.net>
Cc: xen-devel List <xen-devel@lists.xensource.com>
Subject: Re: changeset:6989 vm sticking around in shutdown state
Date: Thu, 22 Sep 2005 07:22:29 -0700 [thread overview]
Message-ID: <87br2lb2sa.fsf@us.ibm.com> (raw)
In-Reply-To: 1127398211.23958.315.camel@pluto.linsolutions.com
TK> Sound like a good starting point, you thinking about appending an
TK> instance to the name?
We previously discussed adding something like -zombie-X to the name,
where X is the old numeric domid. That would make it evident that the
domain was hanging around after death.
TK> I am of the mindset that something like allow creation with the
TK> same name, but invalidate the old one or vice versa.
Yea, so, since Xend looks things up mostly by name, we need to create
the new domain with the real name, and mangle the name of the zombie
so that it mostly gets ignored.
TK> This would also keep track of how many times such an issue occured
TK> on a particular domU.
Well, it would keep track of stuck instances, true. I don't think we
want to keep track of anything that we don't have to. That's what the
logs are for :)
TK> Name Id Mem(MB) CPU VCPU(s) State Time(s)
TK> Domain-0 0 182 - 2 r---- 970.7
TK> debian 3 128 - 2 -b--- 502.4
TK> debian.1 3.1 0 - 2 ---s- 91.1
I think it would/should look like this:
Name Id Mem(MB) CPU VCPU(s) State Time(s)
Domain-0 0 182 - 2 r---- 970.7
debian-zombie-3 3 0 - 2 ---s- 502.4
debian 4 128 - 2 -b--- 91.1
--
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms@us.ibm.com
next prev parent reply other threads:[~2005-09-22 14:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 13:13 changeset:6989 vm sticking around in shutdown state Ted Kaczmarek
2005-09-22 13:57 ` Dan Smith
2005-09-22 14:10 ` Ted Kaczmarek
2005-09-22 14:22 ` Dan Smith [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-23 22:30 Ian Pratt
2005-09-26 15:01 ` Dan Smith
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=87br2lb2sa.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.