[Xen-devel] UPDATE: Test results on Unisys ES7000 64x 256gb using xen-3.1.2-rc1 c/s 15490 -1 new issue, 2 old issues

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

The RESULTS section in the original message I sent needs to indicate that there is 1 new issue.

 

Additional info for this new issue, the serial port shows this entry:

  Cannot handle page request order 0!

When the host is booted with half of the resources, 32 processors and 128 gb memory, test 11_create_concurrent_pos of xm-test does not fail.

 

Any ideas what could be causing this to fail when there is ample host memory?

 

---

From: Krysan, Susan
Sent: Thursday, November 01, 2007 6:29 AM
To: 'xen-devel@xxxxxxxxxxxxxxxxxxx'
Subject: Test results on Unisys ES7000 64x 256gb using xen-3.1.2-rc1 c/s 15490 -1 new issue, 2 old issues

 

Host:  Unisys ES7000/one, x86_64, 64 processors, 256 gb memory

 

xen-3.1.2–rc1 changeset 15490 compiled with max_phys_cpus=64 and booted with dom0_mem=2048M 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 
• 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

 

NEW ISSUE:

• Xm-test gets this failure, but we had never run it with 256GB memory before so it may not be a regression:

11_create_concurrent_pos failed with:

Error: (12, 'Cannot allocate memory')

So increased dom0_mem parameter to 4096M, rebooted, and reran but get the same problem; will test today with less host memory to see if still fails

 

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 248gb memory – run kernbench

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

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

4.       32-processor 64-bit SLES10 domVT with 64gb 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 – booted but could not log in because OS needs to be activated

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 1 new issue and 2 old issues (see above).

 

Xm-test timing summary:

  Run Started : Wed, 31 Oct 2007 17:03:45 -0400

  Run Stoped  : Wed, 31 Oct 2007 17:53:49 -0400

Xm-test execution summary:

  PASS:  109

  FAIL:  3

  XPASS: 1

  XFAIL: 2

 

Details:

 

 FAIL: 11_create_concurrent_pos

         [34] Failed to create domain

 

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