[Xen-devel] Test results on Unisys ES7000 32x 128gb using xen-unstable (c/s 15672 and es7000bigsmp patch) - 4 old issues, 0 new issues

["Krysan, Susan" <KRYSANS@xxxxxxxxxx>]

Host:  Unisys ES7000/one, x86_64, 32 physical processors, 128 GB RAM

 

xen-unstable changeset 15672 booted with dom0_mem=512M acpi=on numa=on and the es7000bigsmp patch applied (which cleans up ES7000 specific bootup code - submitted by Raj Subrahmanian)

 

OLD ISSUES:

• after c/s 15203, networking does not work unless a default gateway is specified
• after c/s 15203, all xm-test tests fail with XmTestLib.NetConfig.NetworkError: Failed to show vif0.0 aliases: 65280 – workaround is to comment out lines in cleanDom0Aliases in xm-test/lib/XmTestLib/NetConfig.py
• bug #940 - Must specify hpet=disable kernel parameter to get 32-bit SLES10 domVTs to boot; narrowed down to c/s 14436 but the patch originator cannot recreate on his hardware
• bug #1037 - Shutdown of large domains takes a long time, during which time dom0 is not interruptible (due to the synchronous tearing down of the memory map)

 

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 124gb memory – run kernbench optimal load

2.       32-processor 64-bit SLES10 domVT with 124gb 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 (booted with hpet=disable) - run kernbench optimal load

5.       4-processor 32-bit PAE SLES10 domVT with 16gb memory (booted with hpet=disable) - run kernbench optimal load

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 16gb memory – run 100% cpu intensive program

 

Results:

 

All domains ran successfully.

 

Ran xm-test (DomU) on dom0 with the following results:

 

(Could only run after commenting out the call to cleanDom0Aliases in xm-test/lib/XmTestLib/NetConfig.py and most of the failures are related to not finding device vif0.0 – this was not necessary before c/s 15203)

 

Xm-test timing summary:

  Run Started : Tue, 07 Aug 2007 15:57:51 -0400

  Run Stoped  : Tue, 07 Aug 2007 16:29:31 -0400

Xm-test execution summary:

  PASS:  100

  FAIL:  12

  XPASS: 0

  XFAIL: 3

 

Details:

 

 FAIL: 05_block_attach_and_dettach_device_repeatedly_pos

         xm block-attach returned invalid 256 != 0

 

 FAIL: 09_block_attach_and_dettach_device_check_data_pos

         xm block-attach returned invalid 256 != 0

 

 FAIL: 13_create_multinic_pos

        Unknown reason

 

XFAIL: 02_network_local_ping_pos

        Unknown reason

 

 FAIL: 03_network_local_tcp_pos

        Unknown reason

 

 FAIL: 04_network_local_udp_pos

        Unknown reason

 

XFAIL: 05_network_dom0_ping_pos

        Unknown reason

 

 FAIL: 06_network_dom0_tcp_pos

        Unknown reason

 

 FAIL: 07_network_dom0_udp_pos

        Unknown reason

 

XFAIL: 11_network_domU_ping_pos

        Unknown reason

 

 FAIL: 12_network_domU_tcp_pos

        Unknown reason

 

 FAIL: 13_network_domU_udp_pos

        Unknown reason

 

Thanks,

Sue Krysan

Linux Systems Group

Unisys Corporation

 

 

 

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