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 7] domU shutdown and reboot problem

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 7] domU shutdown and reboot problem
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Mon, 25 Apr 2005 09:22:37 +0000
Delivery-date: Mon, 25 Apr 2005 09:22:41 +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 mike.wray@xxxxxx  2005-04-25 09:22 -------
I've been looking at the domain reaping code and it looks like
the Python xcs interface is not reporting the virq when domains exit.
The virq triggers the domain reaping code, so xend doesn't know
the domain has exited. Calling 'xm list' makes xend refresh the
domain list, so it notices the exited domain and cleans it up.

The code was not reaping periodically to avoid polling the
xen domain list, but since the virq is now unreliable I'm making it
do that every 5s.

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

Xen-bugs mailing list

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