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


[Xen-bugs] [Bug 119] run away, unkillable domain

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 119] run away, unkillable domain
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Wed, 27 Jul 2005 20:24:34 +0000
Delivery-date: Wed, 27 Jul 2005 20:24:38 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

------- Additional Comments From aliguori@xxxxxxxxxx  2005-07-27 20:24 -------
This is really two bugs.  The first is the 100% CPU usage and the second is the
Zombie domain.

The Zombie domain issues is caused by the fact that the domain is in the dying
state but has no given up all of it's pages (or that someone else still has the
page mapped).  If restarting Xend causes the domain to disappear then this is a
Xend bug.

To trouble shoot the 100% CPU problem, try pausing the domain to remove it from
the scheduler and do a core dump to get the CPU state.  You could also write a
quick libxc program that calls vcpu_guest_get_context().  You want the EIP. 
That will help figure out where in the guest kernel it's looping hard.

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list