From mboxrd@z Thu Jan  1 00:00:00 1970
From: David F Barrera <dfbp@us.ibm.com>
Subject: Re: xen test results on Unisys ES7000
Date: Fri, 14 Jul 2006 12:03:17 -0500
Message-ID: <44B7CE55.6050104@us.ibm.com>
References: <EF8D308BE33AF54D8934DF26520252D303504312@USTR-EXCH5.na.uis.unisys.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <EF8D308BE33AF54D8934DF26520252D303504312@USTR-EXCH5.na.uis.unisys.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: "Krysan, Susan" <KRYSANS@unisys.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

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@lists.xensource.com
> 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