[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#11270
Xen/IA64 Healthiness Report We switch default nightly testing from UP Xen0 to SMP Xen0. 11270 can not create VTI domain if Xen0 is UP and using credit scheduler. But SMP xen0 hasn't problem with credit scheduler. This problem also doesn't happen if changing to 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: 11270:0ae5ba4585c9 Xen Schedule: credit VTI Guest Firmware MD5: b6277539d86d785d8859ea2f99cf6013 Summary Test Report: ----------------------------- Total cases: 15 Passed: 10 Failed: 4 Crashed: 1 Detailed test cases info: ----------------------------- One_VTI_without_vif pass One_VTI __fail__ One_XenU pass Two_VTI_Coexist pass One_VTI_and_One_XenU pass Two_XenU_Coexist pass One_VTI_4096M __fail__(Note1) VTI_Network pass XenU_Network pass One_SMP_XenU __fail__ (Note2) One_SMP_VTI pass UP_VTI_LTP __fail__ (Note3) VTI_Kernel_Build pass Four_VTI_Coexist __crash__(Note4) VTI_Windows pass Notes: ----------------------------- 1. Meet can not allocate memory. bug #736 2. Can't reproduce manually. But the issue is xenU report "xenbus error -12 while reading message" in its console. 3. VTI LTP is too slow to finish. So case report fail. Kernel build in VTI is also slower than before. 4. Can not reproduce. But crash xen0 in nightly running. 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
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |