This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] Zombie domU

To: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Zombie domU
From: "Dirk H. Schulz" <dirk.schulz@xxxxxxxxxxxxx>
Date: Fri, 16 Dec 2005 08:29:57 +0100
Delivery-date: Fri, 16 Dec 2005 07:32:02 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D409D71@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D409D71@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.7 (Macintosh/20050923)
Ian Pratt schrieb:

- snip -

What version of Xen is this? Do you know what you did to kill the

In general, zombie domains aren't too much to worry about from a user
point of view. They typically don't really consume more than a few KB of
memory (despite being listed as holding their full size on 'xm list').
However, they're an indication that something has gone wrong (usually in
the tools) and Xen isn't prepared to destory them completely as it
thinks some resources are still in use. It's good to report such issues
wo we can fix them.
I would like to look somewhat deeper into that, too. I have several similar machines (IBM x330) with identical setup (xen 2.0.7), just different number of domUs. They all run fine, but one of them every few days does not. One of the domUs is not reachable any more then (though shown by xm list), cannot be destroyed (still shown by xm list with 0 used memory), and if I try to reboot the physical machine the shutdown process hangs after shutdown of the network (that usually means driving to the colocation center, urgh).
The only way I can make reboot work then is
a) destroy the domU that is not working
b) run "/etc/init.d/xend restart" which claims not to work
c) then reboot the machine.

There is one difference to the other machines: they all run HIGHMEM4G=y kernels, but the one having problems has only 1 GB of physical memory. Can that be the source of the problems?



Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>