From: David Lie <lie@eecg.toronto.edu>
To: xen-devel@lists.xensource.com
Subject: Zombie domains
Date: Wed, 19 Jul 2006 18:32:11 -0400 [thread overview]
Message-ID: <44BEB2EB.3040801@eecg.toronto.edu> (raw)
I'm using the grant table to map a shared frame between two domains.
Domain 1 shares the frame, and Domain 2 maps it into it's address space.
I then make sure Domain 2 unmaps the frame, and releases all event
channels, etc... before shutting down. Domain 2 always remains as a
zombie though when I do xm list. If I dump the domain info in the Xen
console, I get this information for the zombie domain:
(XEN) General information for domain 12:
(XEN) flags=6 refcnt=1 nr_pages=0 xenheap_pages=0 dirty_cpus={}
(XEN) handle=f4a55907-26db-d7c3-f6a7-392637013289
(XEN) Rangesets belonging to domain 12:
(XEN) Interrupts { }
(XEN) I/O Memory { }
(XEN) I/O Ports { }
(XEN) Memory pages belonging to domain 12:
(XEN) VCPU information and callbacks for domain 12:
(XEN) VCPU0: CPU0 [has=F] flags=10 upcall_pend = 01, upcall_mask =
00 dirty}(XEN) Notifying guest (virq 1, port 0, stat 0/0/-1)
Unfortunately, these fields do not mean very much to me. What does
upcall_pend mean? Sometimes this field is 01, sometimes it's 00. What
about refcnt? Note that Domain 2 is not running XenoLinux, but
something similar to Mini-OS. Can anyone on this list see what might be
stopping this domain from shutting down cleanly? If not, is there any
documentation as to what these fields mean?
Thanks in advance.
-DL
next reply other threads:[~2006-07-19 22:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 22:32 David Lie [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-20 0:59 Zombie domains Ian Pratt
2006-07-20 3:35 ` David Lie
2005-11-01 1:47 zombie domains Yu, Ping Y
2005-10-31 14:47 Gerd Knorr
2005-10-31 20:59 ` David F Barrera
2005-11-08 15:00 ` Ewan Mellor
2005-11-08 15:07 ` Steven Hand
2005-11-08 15:59 ` Gerd Knorr
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=44BEB2EB.3040801@eecg.toronto.edu \
--to=lie@eecg.toronto.edu \
--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.