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

[Xen-devel] xen test results on Unisys ES7000



June 6, 2006

Configuration:

Unisys ES7000/one
x86_64
32 processors (16 procs with hyperthreading turned on)
16 GB RAM
SLES 10 RC1 with xen-unstable changeset 10269

Ran xm-test (see results below) and successfully booted the following SLES10 
domUs:
        a. A uni-processor DomU with 1GB of memory
        b. A 4-processor DomU with 1GB of memory
        c. A uniprocessory DomU with 8GB of memory
        d. A 4-processor DomU with 8GB of memory
        e. A 32-processor DomU with 15GB memory

xm-test results
Issue:  01_enforce_dom0_cpus_basic_pos seems to only release 7 processors 
(drops from 32 to 25).  When we boot as 16 procs with hyperthreading off, this 
test still only releases 7 processors (drops from 16 to 9).  Also changed the 
script to wait longer for the processors to release, but still get the same 
results. 
Xm-test execution summary:
  PASS:  110
  FAIL:  5
  XPASS: 0
  XFAIL: 3

Details:

 FAIL: 01_enforce_dom0_cpus_basic_pos
         /proc/cpuinfo says xend didn't enforce dom0_cpus (25 != 1)

 FAIL: 03_memset_random_pos
         Timed out waiting for console

XFAIL: 02_network_local_ping_pos
         ping loopback failed for size 65507. ping eth0 failed for size 65507.

XFAIL: 05_network_dom0_ping_pos
         Ping to dom0 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®.