Xen/IA64 Healthiness Report 11414 got regression. VTI and XenU couldn't be created, after doing several times creating and destroying. It is why nightly testing report shows so many testing cases failed. But they can be pass in manually retest.
Three main issues I met: 1. vif could not be connected. The domain creating failed. 2. vbd could not be connected. The domain creating failed. 3. The privileged domain did not balloon. The domain creating failed. 4. device 0 (/796) not connected. XenU creating failed. 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: 11414:1bab7d65171b Xen Schedule: credit VTI Guest Firmware MD5: b6277539d86d785d8859ea2f99cf6013 Summary Test Report: ----------------------------- Total cases: 15 Passed: 5 Failed: 10 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 __fail__ One_VTI_4096M __fail__ (pass in manually retest) 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__ (not retest) VTI_Windows __fail__ (pass in manually retest) Notes: ----------------------------- The last stable changeset: ----------------------------- 11333:586c5fe8cf3e Best Regards, Yongkang (Kangkang) 永康 _______________________________________________ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
