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#12018

To: <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#12018
From: "You, Yongkang" <yongkang.you@xxxxxxxxx>
Date: Fri, 3 Nov 2006 16:30:59 +0800
Delivery-date: Fri, 03 Nov 2006 00:31:24 -0800
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: Acb/ImPIxY0g2KN3RvyoEIRPDNWNBQ==
Thread-topic: Xen/IA64 Healthiness Report -Cset#12018
Xen/IA64 Healthiness Report
----------------------------
Nightly testing failed in several XenU cases, but pass when retest. The reasons 
are not clear. 
When doing retesting, we also catch once Xen0 crashing in multi guest (SMP 
VTI Linux+XenU+WIndows) creating. No special serial log printed out. We will 
continue to track this issue.

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: 12018:11b718eb22c9
Xen Schedule: credit
VTI Guest Firmware MD5: ea1815932b91e5a6481bb64468e50254

Summary Test Report:
-----------------------------
  Total cases: 16
  Passed:    11
  Failed:     5

Detailed test cases info:
-----------------------------
Case Name             Status           Case Description
Four_SMPVTI_Coexist    __fail__       4 VTI (mem=256, vcpus=2)
Two_UP_VTI_Co         pass       2 UP_VTI (mem=256)
One_UP_VTI            pass        1 UP_VTI (mem=256)
One_UP_XenU          pass        1 UP_xenU(mem=256)
SMPVTI_LTP            pass        VTI (vcpus=4, mem=512) run LTP
SMPVTI_and_SMPXenU   __fail__    1 VTI + 1 xenU (mem=256 vcpus=2)
Two_SMPXenU_Coexist    __fail__      2 xenU (mem=256, vcpus=2)
One_SMPVTI_4096M      pass      1 VTI (vcpus=2, mem=4096M)
SMPVTI_Network          pass      1 VTI (mem=256,vcpu=2) and 'ping'
SMPXenU_Network        __fail__      1 XenU (vcpus=2) and 'ping'
One_SMP_XenU          pass       1 SMP xenU (vcpus=2)
One_SMP_VTI            pass       1 SMP VTI (vcpus=2)
SMPVTI_Kernel_Build      pass      VTI (vcpus=4) and do Kernel Build
Four_SMPVTI_Coexist      pass      4 VTI domains( mem=256, vcpu=2)
SMPVTI_Windows          pass      SMPVTI windows(vcpu=2)
SMPWin_SMPVTI_SMPxenU  __fail__    SMPVTI Linux/Windows & XenU
UPVTI_Kernel_Build       pass       1 UP VTI and do kernel build 

Notes:
-----------------------------
1. 4 SMP VTI co-existing failure because old suuid issue.
2. other cases are all failed by xenU domain creating failure. 

The last stable changeset:
-----------------------------
12004:cf05aabe6e65


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#12018, You, Yongkang <=