|
|
|
|
|
|
|
|
|
|
xen-ia64-devel
[Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#11460
Xen/IA64 Healthiness Report
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: 11460:da942e577e5e
Xen Schedule: credit
VTI Guest Firmware MD5: ea1815932b91e5a6481bb64468e50254
Summary Test Report:
-----------------------------
Total cases: 16
Passed: 10
Failed: 0
Detailed test cases info:
-----------------------------
1. One_VTI_without_vif pass
2. One_VTI __fail__(pass in retest) Note 1
3. One_XenU pass
4. Two_VTI_Coexist pass
5. One_VTI_and_One_XenU pass
6. Two_XenU_Coexist __fail__ Note2
7. One_VTI_4096M pass
8. VTI_Network pass
9. XenU_Network __fail__(pass in retest) Note 2
10. One_SMP_XenU __fail__(pass in retest) Note 2
11. One_SMP_VTI __fail__(pass in retest) Note 2
12. UP_VTI_LTP pass
13. VTI_Kernel_Build pass
14. Four_VTI_Coexist pass
15. VTI_Windows pass
16. VTI_Win_Linux_XenU_Coexist __fail__(pass in retest) Note 1
Notes:
-----------------------------
1) 2 cases failed because "can not allocate memory" issue.
2) Create 2 XenU domain at the same time is likely to cause problem to Xen. It
could report "Device 769 not connected" and refused to create XenU. If meeting
this problem once, all later xenU domains can not be created successfully, and
command "xm vcpu-list" will also fail. Bug #747 is the easiest way to reproduce.
The last stable changeset:
-----------------------------
11456:3e4fa8b5b245
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#11460,
You, Yongkang <=
|
|
|
|
|