All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grzegorz Milos <gm281@cam.ac.uk>
To: "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@unisys.com>
Cc: Melvin Anderson <Melvin.Anderson@hp.com>, xen-devel@lists.xensource.com
Subject: Re: Xen bug 647: Creation of Mini-OS domain causes certain xm commandsto hang
Date: Thu, 29 Jun 2006 19:40:53 +0200	[thread overview]
Message-ID: <44A410A5.2050004@cam.ac.uk> (raw)
In-Reply-To: <EF8D308BE33AF54D8934DF26520252D304CC4803@USTR-EXCH5.na.uis.unisys.com>

Steven Smith, who originally wrote XenBus code has now updated it as a 
part of a larger patch. It's possible that the problem will go away 
then. We are currently working on checking that in.

I'll report back when that happens.

Cheers
Gregor

> 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

  reply	other threads:[~2006-06-29 17:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-29 15:52 Xen bug 647: Creation of Mini-OS domain causes certain xm commands to hang Melvin Anderson
2006-06-29 17:24 ` Xen bug 647: Creation of Mini-OS domain causes certain xm commandsto hang Puthiyaparambil, Aravindh
2006-06-29 17:40   ` Grzegorz Milos [this message]
2006-06-29 17:51     ` Keir Fraser
2006-07-04 17:35       ` [PATCH] " Grzegorz Milos
2006-07-04 17:39         ` Muli Ben-Yehuda
2006-07-04 18:09           ` Grzegorz Milos
2006-07-05 10:14             ` Grzegorz Milos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44A410A5.2050004@cam.ac.uk \
    --to=gm281@cam.ac.uk \
    --cc=Melvin.Anderson@hp.com \
    --cc=aravindh.puthiyaparambil@unisys.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.