[Xen-devel] Test results on Unisys ES7000 64x 256gb using unstable c/s 16693 on 3.2.0 Release Candidate

["Carb, Brian A" <Brian.Carb@xxxxxxxxxx>]

Test results on Unisys ES7000 64x 256gb using unstable c/s 16693 on 3.2.0 Release Candidate

 

HOST:

Unisys ES7000/one, x86_64, 64 processors, 256gb memory

unstable changeset 16693 compiled with max_phys_cpus=64 and booted with dom0_mem=4096M, numa=on, and xenheap_megabytes=64

from http://xenbits.xensource.com/staging/xen-unstable.hg pulled on 20080108:

 

OLD ISSUES:

-Bug #1037 - Shutdown of large domains takes a long time, during which time xend is unresponsive (due to the synchronous tearing down of the memory map); for example, shutdown of 180gb domu causes xend commands to hang for 5 min 15 sec

 

TESTS:

 

1)  32-processor 64-bit SLES10 para-virtualized VM with 240gb memory - run kernbench -ok

 

2)  32-processor 64-bit SLES10 hardware-virtualized VM with 240gb memory - run kernbench - ok

 

3)  32-processor 64-bit Windows Datacenter hardware-virtualized VM with 240gb memory – run cpu intensive program - ok

 

XM-TEST:

 

Issue: Had to set MAX_DOMS to 5 in 11_create_concurrent_pos.py - otherwise the test would hang forever after a varying number of domu creations and would produce no trace output.

 

Xm-test timing summary:
  Run Started : Wed, 09 Jan 2008 10:45:24 -0500
  Run Stoped  : Wed, 09 Jan 2008 11:35:14 -0500

Xm-test execution summary:
  PASS:  109
  FAIL:  3
  XPASS: 1
  XFAIL: 2

Details:

 FAIL: 02_block_attach_file_device_pos
         xm block-attach returned invalid 256 != 0

 

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.

 

brian carb
unisys corporation - malvern, pa

 

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