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

RE: [Xen-devel] xen test results on Unisys ES7000


  • To: "David F Barrera" <dfbp@xxxxxxxxxx>
  • From: "Krysan, Susan" <KRYSANS@xxxxxxxxxx>
  • Date: Fri, 14 Jul 2006 17:23:27 -0400
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 14 Jul 2006 14:24:52 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcanZ7zHPnDYtp3JS96GAXT6YiQkpQAId2wg
  • Thread-topic: [Xen-devel] xen test results on Unisys ES7000

Hi David,
We have not run yet with that changeset.  We usually do our weekly build
on Mondays, but we are starting a build tonight with changeset 10711 on
our ES7000/one and on a Dell and we will run xm-test on Monday.  We are
migrating to a new ES7000 system next week, so it is possible we do not
get to complete xm-test on that platform on Monday, but we will
certainly have results from the Dell.  

I'll let you know our results.

Thanks,
Sue Krysan
Linux Systems Group
Unisys Corporation
 

-----Original Message-----
From: David F Barrera [mailto:dfbp@xxxxxxxxxx] 
Sent: Friday, July 14, 2006 1:03 PM
To: Krysan, Susan
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] xen test results on Unisys ES7000

Susan,

Are you having any problems completing xm-test with changeset:   10680 
:f692a0a476c5? I am seeing xm-test not complete, the last test appears 
to be 07_destroy_stale_pos.

David

Krysan, Susan wrote:
> July 12, 2006
>
> Configuration:
>
> Unisys ES7000/one
> x86_64
> 32 physical processors 
> 48 GB RAM
> SLES10 RC3 with xen-unstable changeset  10648
>
> Issues: None (enforce_dom0_cpus actually passed - output shows number
of cpus dropping with each /proc/cpuinfo check, but the 20 second wait
loop in xm-test was just a second or two too short)
>
> Xm-test execution summary:
>   PASS:  106
>   FAIL:  6
>   XPASS: 0
>   XFAIL: 3
>
> Details:
>
>  FAIL: 01_enforce_dom0_cpus_basic_pos
>          /proc/cpuinfo says xend didn't enforce dom0_cpus (2 != 1)
>
> 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 1 48 64 512 1440 1500 1505 4096 4192
32767 65507.
>
>  FAIL: 12_network_domU_tcp_pos
>          TCP hping2 failed for size 16384 24567 32767 65495.
>
>  FAIL: 13_network_domU_udp_pos
>          UDP hping2 failed for size 32767 65495.
>
>   
>> Thanks,
>> Sue Krysan
>> Linux Systems Group
>> Unisys Corporation
>>
>>
>>     
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>   


-- 

Regards,

David F Barrera
Linux Technology Center
Systems and Technology Group, IBM

"The wisest men follow their own direction. "
        
                          Euripides



_______________________________________________
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®.