[Xen-devel] xen test results on Unisys ES7000 using changeset 13898

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

Host:  Unisys ES7000/one, x86_64, 16 physical processors, 64 GB RAM

 

xen-unstable changeset 13898 booted with dom0_mem=512M

 

Issue:  When attempt to start a domain for which there is not enough memory, get “Error: an integer is required” instead of a message indicating there is not enough memory. See xend.log output attached.

 

Booted, logged into, and ran SLES top command or Windows task manager in the following domUs and domVTs (#s 2 through 7 ran simultaneously):

 

1. 32-processor 64-bit SLES10 DomU with 62GB memory
2. 4-processor 64-bit SLES10 DomU with 16GB memory
3. 4-procesor 32-bit SLES10 DomVT with 2GB memory
4. 4-processor 32-bit PAE SLES10 DomVT with 16GB memory
5. 4-processor 64-bit SLES10 DomVT with 16GB memory
6. 1-processor Windows XP DomVT with 4GB memory
7. 1-processor Windows 2003 Server DomVT with 4GB memory

 

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

 

Xm-test timing summary:

  Run Started : Mon, 12 Feb 2007 09:50:01 -0500

  Run Stoped  : Mon, 12 Feb 2007 10:36:11 -0500

Xm-test execution summary:

  PASS:  109

  FAIL:  3

  XPASS: 2

  XFAIL: 1

 

 

Details:

 

 FAIL: 04_memset_smallmem_pos

         Bug #145 Ballooning DomU too low caused run-away

 

XFAIL: 02_network_local_ping_pos

         ping loopback failed for size 65507. ping eth0 failed for size 65507.

 

 FAIL: 01_vcpu-pin_basic_pos

         failed to switch VCPU 0 to CPU 1

 

 

 

Thanks,

Sue Krysan

Linux Systems Group

Unisys Corporation

 

 

 

xendlog.txt
Description: xendlog.txt

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