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-devel] What actually destroys a domain?

To: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] What actually destroys a domain?
From: Jimi Xenidis <jimix@xxxxxxxxxxxxxx>
Date: Mon, 11 Sep 2006 21:22:00 -0400
Delivery-date: Mon, 11 Sep 2006 18:22:08 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Collegues say that x86 does not have this problem, however on PowerPC if you:
 1) start a domain
 2) attach console
 3) destroy the domain

The xenconsole client stays connected because xenconsoled does not close
the PTY.  A character on the client will kick the close and all is
well.  Xenconsoled _does_ get the watch event, but the domain is
completely destroyed and xc_domain_getinfo does not find it to
eventually close() the PTY

It is possible that PowerPC is missing  a get_domain(), perhpas by a
resource held by xenconsoled?
Any thoughts?

Xen-devel mailing list