All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Gorm Hansen <jacobg@diku.dk>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Preview of Next Generation VM-Tools
Date: Thu, 28 Apr 2005 17:08:58 -0700	[thread overview]
Message-ID: <42717B1A.9080903@diku.dk> (raw)
In-Reply-To: <427027F4.2040500@us.ibm.com>

Anthony Liguori wrote:
> Hi all,
> 
> I've posted a preview release of the next generation of VM-Tools.  This 
> generation of the tool chain will be different from the existing 
> versions of VM-Tools in a number of important ways.  Below are the 
> highlights:
> 
> o Single daemon based system
> o Support for 3.0 and 2.0.x trees
> o Improved logging via syslog
> o Many others
> 
> This is just a preview release and is not meant to be used for anything 
> other than simply understanding the new architecture.  The README in the 
> tarball includes a list of what's working and what's not working.
> 

hi Anthony,

there seems to be a race in the creation of new domains, if I run the 
commands from the README in a script, xenctld prints:

xenctld: New domain-0
xenctld: Binding to port 0:0
xenctld: Got message destined 1:0:1
xenctld: Received msg for unknown domain-1
xenctld: New domain-1
xenctld: evtchn_bind_interdomain(32752,1,0,1) failed: Invalid argument
xenctld: Failed opening event channel

Whereas If I put a 'sleep 1' between each of the lines in the script, 
the domain starts up and connects the conosole without problems.

Jacob\\

  reply	other threads:[~2005-04-29  0:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-28  0:01 Preview of Next Generation VM-Tools Anthony Liguori
2005-04-29  0:08 ` Jacob Gorm Hansen [this message]
2005-04-29  2:08   ` Anthony Liguori
2005-04-29  4:03     ` Jacob Gorm Hansen
2005-05-01 15:26 ` aq

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=42717B1A.9080903@diku.dk \
    --to=jacobg@diku.dk \
    --cc=aliguori@us.ibm.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.