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

[Xen-devel] Test results on Unisys ES7000 32x 128gb using xen-unstable (c/s 15080) - 1 new issue


  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Krysan, Susan" <KRYSANS@xxxxxxxxxx>
  • Date: Wed, 30 May 2007 18:21:11 -0400
  • Delivery-date: Wed, 30 May 2007 15:19:27 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcdJ4UYHnZd8QwLHTMSjo0sqxNkrmgE+CxDgAZa+3qABVnT68AFk5dvwAufQgQABArjgkAIyIiNQA7uSpdABgtM2EAIyrZhAAA2mOPADEjFQkA==
  • Thread-topic: Test results on Unisys ES7000 32x 128gb using xen-unstable (c/s 15080) - 1 new issue

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

 

xen-unstable changeset 15080 booted with dom0_mem=512M

 

ISSUES:

New: host halts upon shutdown of 126000mb domU and domVT

Old: 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.  Bug # 940

Domain #1 and #2 – host crashes upon shutdown of domU (reducing the memory in config file to 124000mb works fine)

Rest ran successfully.

 

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

 

Xm-test timing summary:

  Run Started : Wed, 30 May 2007 08:02:22 -0400

  Run Stoped  : Wed, 30 May 2007 08:49:15 -0400

Xm-test execution summary:

  PASS:  111

  FAIL:  1

  XPASS: 2

  XFAIL: 1

 

Details:

 

XFAIL: 02_network_local_ping_pos

         ping loopback failed for size 65507. ping eth0 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®.