From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: Preview of Next Generation VM-Tools Date: Thu, 28 Apr 2005 21:08:22 -0500 Message-ID: <42719716.7070100@us.ibm.com> References: <427027F4.2040500@us.ibm.com> <42717B1A.9080903@diku.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <42717B1A.9080903@diku.dk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jacob Gorm Hansen Cc: xen-devel List-Id: xen-devel@lists.xenproject.org Jacob Gorm Hansen wrote: > hi Anthony, Hi Jacob, > > 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. I noticed that myself. Xencltd uses a timeout to update it's information about domains. What it needs to do is make sure that any entry into xenctld causes the information to be updated. That's for pointing it out. It'll be fixed for the next release. Regards, > Jacob\\ >