From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Steven Hand" Subject: Re: VMX status report 11568:8c29bf7ede67 Date: Fri, 22 Sep 2006 08:18:31 +0100 Message-ID: <082301c6de17$4fb0f8d0$80cda8c0@Violet> References: Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Yu, Ping Y" , xen-devel@lists.xensource.com Cc: steven@xensource.com List-Id: xen-devel@lists.xenproject.org >1).IA32: Build linux 2.6.16 kernel in IA32 non-pae SMP VMX domain >succeed about 30% of the time. This should be fixed by the next -unstable cset (11569:6e3223a69461). Please let us know if not. >2).Create four VMX domains simultaneously, usually, not all four VMX >domains can start successfully. only part of them can start, but two or >one will failed with the following messages " Error: Device 768 (vbd) >could not be connected. Hotplug scripts not working." or "Error: Device >5632 (vbd) could not be connected. Hotplug scripts not working."or " >Error: Device 0 (vif) could not be connected. Hotplug scripts not >working.". Hmm - we're working on a fix for this; indeed, I thought that unstable cset 11554: 39aaa54756db which extends some timeouts would avoid this issue. We can look into this some more today. cheers, S.