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] VMX status report. Xen: #16702 & Xen0: #376 --one new is

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, "Li, Haicheng" <haicheng.li@xxxxxxxxx>, "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] VMX status report. Xen: #16702 & Xen0: #376 --one new issue.
From: "You, Yongkang" <yongkang.you@xxxxxxxxx>
Date: Fri, 11 Jan 2008 22:52:06 +0800
Delivery-date: Fri, 11 Jan 2008 07:13:08 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C3ACFF63.1A989%Keir.Fraser@xxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AchUNAk+3fzkJe+DRkO89KSlZwE7TQADq6rfAAd15vA=
Thread-topic: [Xen-devel] VMX status report. Xen: #16702 & Xen0: #376 --one new issue.
On Friday, January 11, 2008 7:12 PM, "Keir Fraser" wrote:

> On 11/1/08 09:26, "Li, Haicheng" <haicheng.li@xxxxxxxxx> wrote:
> 
>> One new issue, as listed, is found in today's testing, which is not a
>> regression, should be present for a long time.
>> 
>> New Issues:
>> ==============================================
>> 1) XenU guest will hang if booted just after destorying a HVM guest.
>> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1139
> 
> Is there a new test you've added which triggers this?
> 
>  -- Keir

No, we do not add new case to trigger this. But locate it from the tricky 
testing result. We found some strange testing output that show there is often 
1~2 cases failed in the totally 30+ auto testing. But when we redo the specail 
case or manualy retest, it always pass. So it puzzled us. Finally we found this 
failure would happen in a combination testing situation. Well, it seems not 
happen every time and not happen on all machines. 

Could this issue be reproduced in your machine? 

Best Regards,
Yongkang You

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