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-ia64-devel

[Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#11300

To: <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#11300
From: "You, Yongkang" <yongkang.you@xxxxxxxxx>
Date: Mon, 28 Aug 2006 12:59:29 +0800
Delivery-date: Sun, 27 Aug 2006 22:00:13 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcbKXr1inyFJFTi/TQ+oUCK9PhzGGg==
Thread-topic: Xen/IA64 Healthiness Report -Cset#11300
Xen/IA64 Healthiness Report

We switch default nightly testing from UP Xen0 to SMP Xen0.

VTI domain might stop running if Xen0 is UP and using credit scheduler. This 
issue was found from 11270. SMP xen0 hasn't problem with credit scheduler. 
This problem also doesn't happen with bvt scheduler. 

Testing Environment:
----------------------------
Platform: Tiger4
Processor: Itanium 2 Processor
Logic Processors number: 8 (2 processors with Due Core)
PAL version: 8.15
Service OS: RHEL4u3 IA64 SMP with 2 VCPUs
VTI Guest OS: RHEL4u2 & RHEL4u3
XenU Guest OS: RHEL4u2
Xen IA64 Unstable tree: 11300:40f6fdb68fa9
Xen Schedule: credit
VTI Guest Firmware MD5: b6277539d86d785d8859ea2f99cf6013

Summary Test Report:
-----------------------------
  Total cases: 15
  Passed:    10
  Failed:     5
  Crashed:   0

Detailed test cases info:
-----------------------------
One_VTI_without_vif                __fail__ (Note1)
One_VTI                           pass 
One_XenU                         pass
Two_VTI_Coexist                   pass
One_VTI_and_One_XenU           pass
Two_XenU_Coexist                 __fail__ (Note2)
One_VTI_4096M                   pass
VTI_Network                       pass
XenU_Network                     __fail__ (Note2)
One_SMP_XenU                   pass
One_SMP_VTI                     pass
UP_VTI_LTP                       __fail__ (Note3)
VTI_Kernel_Build                   __fail__(Note1)
Four_VTI_Coexist                  pass
VTI_Windows                      pass

Notes:
-----------------------------
1. Meet can not allocate memory. bug #736
2. XenU cases failed reason should be bug #747.
3. VTI LTP is too slow to finish. So case report fail. Kernel build in VTI is 
also 
slower than before.

The last stable changeset:
-----------------------------
10706:2db50529223e

Best Regards,
Yongkang (Kangkang) 永康

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#11300, You, Yongkang <=