[Xen-ia64-devel] Weekly Xen-IA64/VTI status report.

["You, Yongkang" <yongkang.you@xxxxxxxxx>]

Hi all,

This week Xen-IA64 has good news of adding reclaiming VTI memory after destroy 
it, although there are some important issues.

Main usage Issue:
1. If create XenU when Domain VTI is booting, VTI domain will hang. And XenU 
console also didn't output. Xm list can show xenU is running, but VTI is 
stopped. (old issue)
2. If VTI domain and xenU are both created, destroy xenU will cause system 
hang. (old issue)
3. If create 2 VTI domain, destroy 1 VTI domain will cause system hang. (new 
issue)

Fixed obvious bugs (see my last week report.):
1. Destroy VTI Domain can reclaim all memory and xm list shows right.
2. The 2nd xenU can be created after the 1st is destroyed.
3. VTI can be created by default with the workaround fixing of comment out vif.

The nightly testing result has been post to attachment. 2 new cases have been 
added, 1 is testing creating/destroying xenU, the 2nd is testing 
creating/destroying 2 VTI domain. Besides of hang machine issue, sometimes when 
creating 2 VTI domains, 1 of them will disappear in the middle of process.

My testing environment:
    Machine                     : Itanium 2 on Tiger4
        Xen Source tree : xen-ia64-unstable
    Changeset           : 9277 -> 9395
        Build method            : make -j5
    Xen0 OS                     : RHEL4 U2 (no SMP)
    VTI OS                      : RHEL4 U2 (no SMP)
    XenU OS                     : RHEL4 U2 (no SMP)

The LTP results for xen0 will be update in next week. 

Best Regards,
Yongkang (Kangkang) 永康

Attachment: WW12.txt
Description: WW12.txt

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel