WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Test results on Unisys ES7000 48x 166gb using unstable c/s 1

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Test results on Unisys ES7000 48x 166gb using unstable c/s 16471 - 2 old issues; 1 new but already being fixed
From: "Krysan, Susan" <KRYSANS@xxxxxxxxxx>
Date: Wed, 28 Nov 2007 08:48:34 -0600
Delivery-date: Wed, 28 Nov 2007 06:52:56 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <CE091CB077F4A74A9CBA33A4E4A8A3BF0B225EE8@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <EF8D308BE33AF54D8934DF26520252D3069BD48F@xxxxxxxxxxxxxxxxxxxxxxxxxxxx><FE7BBCFBB500984A9A7922EBC95F516E27D344@xxxxxxxxxxxxxxxxxxxxxxxxxxxx><EF8D308BE33AF54D8934DF26520252D3069BD4F8@xxxxxxxxxxxxxxxxxxxxxxxxxxxx><EF8D308BE33AF54D8934DF26520252D3069BD54A@xxxxxxxxxxxxxxxxxxxxxxxxxxxx><EF8D308BE33AF54D8934DF26520252D3069BD57A@xxxxxxxxxxxxxxxxxxxxxxxxxxxx><EF8D308BE33AF54D8934DF26520252D3069BD5BD@xxxxxxxxxxxxxxxxxxxxxxxxxxxx><CE091CB077F4A74A9CBA33A4E4A8A3BF0B225D0C@xxxxxxxxxxxxxxxxxxxxxxxxxxxx><CE091CB077F4A74A9CBA33A4E4A8A3BF0B225D66@xxxxxxxxxxxxxxxxxxxxxxxxxxxx><CE091CB077F4A74A9CBA33A4E4A8A3BF0B225DAD@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <CE091CB077F4A74A9CBA33A4E4A8A3BF0B225DED@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <CE091CB077F4A74A9CBA33A4E4A8A3BF0B225E34@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <CE091CB077F4A74A9CBA33A4E4A8A3BF0B225E62@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <CE091CB077F4A74A9CBA33A4E4A8A3BF0B225E65@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <CE091CB077F4A74A9CBA33A4E4A8A3BF0B225EE8@USEA-EXCH4 .na.uis. unisys.com>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcdJ4UYHnZd8QwLHTMSjo0sqxNkrmgE+CxDgAZa+3qABVnT68AFk5dvwAufQgQABArjgkAIyIiNQA7uSpdABgtM2EAIyrZhAAA2mOPADEjFQkAeOTDJwAbZ/6+AETqFeYAMnFGQQBBWRQcADAUxrYAH1Vh2QAxmfzJABYo/kIAAu5NxwA/TQXMABPD35QA==
Thread-topic: Test results on Unisys ES7000 48x 166gb using unstable c/s 16471 - 2 old issues; 1 new but already being fixed

Host:  Unisys ES7000/one, x86_64, 48 processors, 166gb memory (host has 192gb, but truncates to 166gb)

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

 

NEW ISSUE (fix on the way):

-four xm-test failures: ERROR Internal error: No extended context for VCPU0

 

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 

-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 1 through 8 simultaneously):

1)    8-processor 64-bit SLES10 domU with 32gb memory - run kernbench

2)    8-processor 64-bit SLES10 domVT with 32gb memory – run kernbench

3)    8-processor 32-bit SLES10 domU with 16gb memory – run kernbench

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

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

6)    8-processor 32-bit Windows 2003 Enterprise Edition domVT with 32gb memory – run cpu intensive program

7)    8-processor 64-bit Windows Datacenter with 32gb memory – run cpu intensive program

8)    2-processor 32-bit Windows XP domVT with 4gb memory – run cpu intensive program

9)    32-processor 64-bit SLES10 domU with 160gb memory - run kernbench

10)  32-processor 64-bit SLES10 domVT with 160gb memory - run kernbench

 

RESULTS:

All tests were successful, except for 2 old issues (see above).

 

Xm-test timing summary:

  Run Started : Tue, 27 Nov 2007 15:16:42 -0500

  Run Stoped  : Tue, 27 Nov 2007 16:04:37 -0500

Xm-test execution summary:

  PASS:  106

  FAIL:  6

  XPASS: 1

  XFAIL: 2

 

Details:

 

 FAIL: 01_migrate_localhost_pos

         xm migrate 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.

 

 FAIL: 01_restore_basic_pos

         save command exited 256 != 0

 

FAIL: 04_restore_withdevices_pos

         xm save exited with 256 != 0

 

 FAIL: 01_save_basic_pos

         save command exited 256 != 0

 

Thanks,

Sue Krysan

Linux Systems Group

Unisys Corporation

 

 

 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>