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

To: <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#11447
From: "You, Yongkang" <yongkang.you@xxxxxxxxx>
Date: Mon, 11 Sep 2006 13:20:20 +0800
Delivery-date: Sun, 10 Sep 2006 22:20:40 -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: AcbVYfkvTvKdoxfaS66nTFg2OyrYFQ==
Thread-topic: Xen/IA64 Healthiness Report -Cset#11447
Xen/IA64 Healthiness Report

Nightly testing still met:
"Error: Device 0 (vif) could not be connected. Hotplug scripts not working." 
, after a lot of times creating and destroying domains. IA32 side also met 
similar 
issue sometimes, but not so easy like IA64 side. It has to reboot testing 
machine to recover domain creating. 

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: 11447:a1988768828d
Xen Schedule: credit
VTI Guest Firmware MD5: ea1815932b91e5a6481bb64468e50254

Summary Test Report:
-----------------------------
  Total cases: 16
  Passed:    7
  Failed:     9

Detailed test cases info:
-----------------------------
One_VTI_without_vif                pass
One_VTI                           pass 
One_XenU                         pass
Two_VTI_Coexist                   __fail__(pass in manually retest)
One_VTI_and_One_XenU           pass
Two_XenU_Coexist                 pass
One_VTI_4096M                   pass
VTI_Network                       pass
XenU_Network                     __fail__(pass in manually retest)
One_SMP_XenU                   __fail__(pass in manually retest)
One_SMP_VTI                     __fail__(pass in manually retest)
UP_VTI_LTP                       __fail__(not retest)
VTI_Kernel_Build                   __fail__(not retest)
Four_VTI_Coexist                  __fail__(pass in manually retest)
VTI_Windows                      __fail__ (pass in manually retest)
VTI_Win_Linux_XenU_Coexist       __fail__(pass in manually retest)

Notes:
-----------------------------
All failed cases are because of "xm creating" command failed by
"Error: Device 0 (vif) could not be connected. Hotplug scripts not working."

The last stable changeset:
-----------------------------
11333:586c5fe8cf3e

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