From: David F Barrera <dfbp@us.ibm.com>
To: Gerd Knorr <kraxel@suse.de>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: zombie domains
Date: Mon, 31 Oct 2005 14:59:29 -0600 [thread overview]
Message-ID: <436685B1.1050003@us.ibm.com> (raw)
In-Reply-To: <43662E9F.3000103@suse.de>
I saved a domain and ended up with a Zombie-migrating domain:
x235:~ # xm list
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 250 1 r----- 5518.8
vm1 1 127 1 ------ 2564.9
Zombie-migrating-vm2 2 0 1 ---s-d 1292.4
vm3 3 127 1 ------ 1683.5
vm4 4 127 1 ------ 1783.8
vm5 5 127 1 r----- 1615.0
vm2 6 126 1 ------ 10.9
At first I thought it was a temporary state, but after an hour or so, it
is still there. I later restored it (vm2) successfully, but the zombie
is still there.
Gerd Knorr wrote:
> Hi,
>
> How can I figure why some domain is still in zombie state, like these
> ones:
>
> master-xen root /vm/ttylinux# xm list
> Name ID Mem(MiB) VCPUs State Time(s)
> Domain-0 0 574 1 r----- 90.5
> Zombie-small-11 28 0 1 ---s-d 0.9
> Zombie-small-17 34 0 1 ---s-d 0.5
> Zombie-small-18 35 0 1 ---s-d 0.6
> Zombie-small-19 36 0 1 ---s-d 0.5
>
> I've created 16 ttylinux instances with a script, then called "xm
> shutdown -a -w", then ended up with these four Zombies ...
>
> Gerd
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2005-10-31 20:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 14:47 zombie domains Gerd Knorr
2005-10-31 20:59 ` David F Barrera [this message]
2005-11-08 15:00 ` Ewan Mellor
2005-11-08 15:07 ` Steven Hand
2005-11-08 15:59 ` Gerd Knorr
-- strict thread matches above, loose matches on Subject: below --
2005-11-01 1:47 Yu, Ping Y
2006-07-19 22:32 Zombie domains David Lie
2006-07-20 0:59 Ian Pratt
2006-07-20 3:35 ` David Lie
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=436685B1.1050003@us.ibm.com \
--to=dfbp@us.ibm.com \
--cc=kraxel@suse.de \
--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.