[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Test results on Unisys ES7000 32x 128gb using xen-3.1.2-rc1 c/s 15489 -no new issues, 2 old issues


  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Krysan, Susan" <KRYSANS@xxxxxxxxxx>
  • Date: Thu, 25 Oct 2007 07:56:40 -0500
  • Delivery-date: Thu, 25 Oct 2007 05:58:23 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcdJ4UYHnZd8QwLHTMSjo0sqxNkrmgE+CxDgAZa+3qABVnT68AFk5dvwAufQgQABArjgkAIyIiNQA7uSpdABgtM2EAIyrZhAAA2mOPADEjFQkAeOTDJwAbZ/6+AETqFeYAMnFGQQBBWRQcADAUxrYAH1Vh2QAxmfzJA=
  • Thread-topic: Test results on Unisys ES7000 32x 128gb using xen-3.1.2-rc1 c/s 15489 -no new issues, 2 old issues

Host:  Unisys ES7000/one, x86_64, 32 processors, 128 gb memory

 

xen-3.1.2 –rc1 changeset 15489 compiled with max_phys_cpus=64 and booted with dom0_mem=1024M and numa=on

 

OLD ISSUES:

 

  • 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) – for example, shutdown of 180gb domu causes 5 min 15 sec dom0 unresponsiveness  FYI  the patch submitted with preemption code does get called but it is not working for us.  Our team is still looking into it
  • 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

 

TESTS include running xm-test and also attempting to boot and run programs in the following domUs and domVTs (running domains #s 3 through 10 simultaneously):

 

1.       32-processor 64-bit SLES10 domU with 124gb memory – run kernbench

2.       32-processor 64-bit SLES10 domVT with 124gb memory – run kernbench

3.       8-processor 64-bit SLES10 domU with 16gb memory - run kernbench

4.       8-processor 64-bit SLES10 domVT with 16gb memory – run kernbench

5.       8-processor 32-bit SLES10 domU with 4gb memory – run kernbench

6.       8-processor 32-bit SLES10 domVT with 4gb memory (booted with hpet=disable) - run kernbench

7.       8-processor 32-bit PAE SLES10 domVT with 16gb memory (booted with hpet=disable) - run kernbench

8.       8-processor 64-bit Windows 2003 Enterprise Edition domVT with 16gb memory – run 100% cpu intensive program

9.       2-processor 32-bit Windows XP domVT with 4gb memory – run 100% cpu intensive program

10.   1-processor 32-bit Windows 2003 Server domVT with 4gb memory – run 100% cpu intensive program

 

RESULTS:

 

All tests were successful, except for the 2 old issues above.

 

Xm-test timing summary:

  Run Started : Wed, 24 Oct 2007 10:43:30 -0400

  Run Stoped  : Wed, 24 Oct 2007 11:35:03 -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

 

 

 

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.