|   | 
      | 
  
  
      | 
      | 
  
 
     | 
    | 
  
  
     | 
    | 
  
  
    |   | 
      | 
  
  
    | 
         
xen-ia64-devel
[Xen-ia64-devel] Weekly Xen-IA64/VTI status report.
 
Hi all,
This week, IA64/Xen has good progress. There are several critical bugs have 
been fixed. Xen has changed default making mechanism. Only 1 kernel is built 
out for both xen0 and xenU. This will save some building time.
Main usage Issue:
1. Sometimes Xen0 will hang, when 2 VTI domains are booting with some work load 
in Xen0.
2. scp big file (>512M) sometimes will cause xen0 unusable and scp to be 
stalled. This problem doesn't happen in local cp after mount remote folder. 
This issue maybe because of lacking of memory of xen0 (at present xen0 only has 
512M memory as default)
Fixed obvious bugs:
1. XenU and VTI domains can be created and boot at the same time.
2. Destroy XenU won't crash xen0, when VTI domain is there.
3. Destroying 1 VTI domain of 2 won't hang Xen0.
The nightly testing includes 4 testing cases. Please look at the attachment 
file for the detailed info.
1 VTI creating/destroying               Pass
1 XenU creating/destroying              Pass
1 VTI run LTP                           Pass
2 VTI creating/destroying               Pass
My testing environment:
    Machine                     : Itanium 2 on Tiger4
        Xen Source tree : xen-ia64-unstable
    Changeset           : 9404 -> 9482
        Build method            : make -j5
    Xen0 OS                     : RHEL4 U2 (no SMP)
    VTI OS                      : RHEL4 U2 (no SMP)
    XenU OS                     : RHEL4 U2 (no SMP)
I also rerun some failed LTP cases in Xen0. The results are:. 
proc01 couldn't finish and return for more than 1 hour. I have to break it.
proc01  0       INFO: /proc/sa1/cpe/data: open: Cannot allocate memory
proc01  1       BROK : Unexpected signal 2 received.
fork12 will hang xen0 after run in 30 mins. Serial port kept report soft lockup 
detected on CPU#0 and call trace.
And another 2 system call cases madvise02 and setrlimit03 also failed. The 
following is the output. 
#./setrlimit03
setrlimit03    1  FAIL  :  call succeeded unexpectedly
#./madvise02
madvise02    1  PASS  :  expected failure - errno = 22 : Invalid argument
madvise02    2  PASS  :  expected failure - errno = 22 : Invalid argument
madvise02    3  PASS  :  expected failure - errno = 22 : Invalid argument
madvise02    4  PASS  :  expected failure - errno = 12 : Cannot allocate memory
madvise02    5  FAIL  :  madvise failed, expected return value = -1, got 0
Best Regards,
Yongkang (Kangkang) 永康
 
WW13.txt 
Description: WW13.txt 
_______________________________________________
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] Weekly Xen-IA64/VTI status report., You, Yongkang
- [Xen-ia64-devel] Weekly Xen-IA64/VTI status report., You, Yongkang
 
- RE: [Xen-ia64-devel] Weekly Xen-IA64/VTI status report., You, Yongkang
 
- [Xen-ia64-devel] Weekly Xen-IA64/VTI status report., You, Yongkang
 
- RE: [Xen-ia64-devel] Weekly Xen-IA64/VTI status report., You, Yongkang
 
- [Xen-ia64-devel] Weekly Xen-IA64/VTI status report.,
You, Yongkang <=
 
  
 
 
 |  
  
 | 
    | 
  
  
    |   | 
    |