[Xen-devel] Test results on Unisys ES7000 32x 128gb using xen-unstable (c/s 15470) - 2 old issues; 2 new issue

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

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

 

xen-unstable changeset 15470 booted with dom0_mem=512M

 

2 NEW ISSUES:

Networking does not work when a default gateway is not specified

All xm-test tests fail with XmTestLib.NetConfig.NetworkError: Failed to show vif0.0 aliases: 65280 – workaround is to comment out the call to cleanDom0Aliases in xm-test/lib/XmTestLib/NetConfig.py

 

2 OLD ISSUES:

Host halts upon shutdown of 126000mb domU and domVT

Must specify hpet=disable kernel parameter to get 32-bit SLES10 domVTs to boot – 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 126gb (126000mb) memory – run kernbench optimal load

2.       32-processor 64-bit SLES10 domVT with 126gb (126000mb) 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 without hpet=disable parameter.  Bug # 940

Domain #1 and #2 – able to run kernbench in these domains, but host crashes when shut them down; serport does not provide a reason why. 

Reducing the memory of these domains to 124000mb used to work, but have tested 122000mb and 120000mb and host still halts. Still running tests to determine the largest size domain that works.

 

The other 5 tests 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

 

Xm-test timing summary:

  Run Started : Sat, 07 Jul 2007 12:28:04 -0400

  Run Stoped  : Sat, 07 Jul 2007 12:59:19 -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