Host:  Unisys ES7000/one, x86_64, 32 physical
processors, 128 GB RAM
 
Xen-3.1-testing changeset 15006 booted with dom0_mem=512M
 
ISSUES: still cannot boot of 32-bit SLES10 DomVTs –
bug #940; narrowed down to c/s 14436
 
Testing includes running xm-test and also attempting to boot
and run programs in the following domUs and domVTs (running domains #s 3
through 9 simultaneously):
 
1.       32-processor
64-bit SLES10 DomU with 62GB memory – run kernbench optimal load
2.       32-processor
64-bit SLES10 DomVT with 62GB memory – run kernbench optimal load
3.       4-processor
64-bit SLES10 DomU with 16GB memory - run kernbench optimal load
4.       4-procesor
32-bit SLES10 DomVT with 2GB memory – doesn’t boot
5.       4-processor
32-bit PAE SLES10 DomVT with 16GB memory – doesn’t boot
6.       4-processor
64-bit SLES10 DomVT with 16GB memory – run kernbench optimal load
7.       1-processor
Windows XP DomVT with 4GB memory – run 100% cpu intensive program
8.       1-processor
Windows 2003 Server DomVT with 4GB memory – run 100% cpu intensive
program
           
9.   8-processor Windows 2003 Enterprise
Edition DomVT with 8GB memory – run 100% cpu intensive program
 
Results:
Domains #4 and #5 (32-bit) do not boot.  Bug # 940
Rest ran successfully.
 
Ran xm-test (PV) on dom0 with the following results:
 
Xm-test timing summary:
  Run Started : Thu, 03 May 2007 09:23:44 -0400
  Run Stoped  : Thu, 03 May 2007 10:10:50 -0400
Xm-test execution summary:
  PASS:  110
  FAIL:  2
  XPASS: 1
  XFAIL: 2
 
Details:
 
XFAIL: 02_network_local_ping_pos
         ping
loopback failed for size 65507. ping eth0 failed for size 65507.
 
XFAIL: 11_network_domU_ping_pos
         Ping failed for size 65507.
 
Thanks,
Sue Krysan
Linux Systems Group
Unisys Corporation