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

Re: [Xen-devel] Preview of Next Generation VM-Tools

To: Anthony Liguori <aliguori@xxxxxxxxxx>
Subject: Re: [Xen-devel] Preview of Next Generation VM-Tools
From: Jacob Gorm Hansen <jacobg@xxxxxxx>
Date: Thu, 28 Apr 2005 17:08:58 -0700
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 29 Apr 2005 00:08:41 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <427027F4.2040500@xxxxxxxxxx>
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>
References: <427027F4.2040500@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0 (X11/20050302)
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\\

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

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