WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] RE: Xen bug 647: Creation of Mini-OS domain causes certain x

To: "Melvin Anderson" <Melvin.Anderson@xxxxxx>
Subject: [Xen-devel] RE: Xen bug 647: Creation of Mini-OS domain causes certain xm commandsto hang
From: "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>
Date: Thu, 29 Jun 2006 13:24:34 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Grzegorz Milos <gm281@xxxxxxxxx>
Delivery-date: Thu, 29 Jun 2006 10:25:06 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1151596374.31660.18.camel@xxxxxxxxxxxxxxxxxxxxxxx>
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
Thread-index: AcablB/BIeNy0ovYR9Cg5XJhcBAEzQADDgnA
Thread-topic: Xen bug 647: Creation of Mini-OS domain causes certain xm commandsto hang
Melvin,

> Did you or anyone else on the Xen distribution list make any progress
> with bug 647: "Creation of Mini-OS domain causes certain xm commands
to
> hang"?

Gregor said that he would be looking into this. I am not sure if he has
made any progress.

> After starting mini-OS and running "xm list" it seems as if the
function
> "domains" in XMLRPCServer.py is entered, but never returns.

Yup that is where the hang happens. BTW, if you don't initialize xenbus
this problem does not happen the last time I tried. So I think it is a
locking issue in the mini-os xenbus code.

Cheers,
Aravindh

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel