thr3ads.net - Xen devel - [Xen-devel] xen test results on Unisys ES7000 [Jul 2006]

If this information is useful, please help other people find it:
Share via:

Krysan, Susan

2006-Jul-12 18:16 UTC

[Xen-devel] xen test results on Unisys ES7000

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

David F Barrera

2006-Jul-14 17:03 UTC

head link

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@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



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

Krysan, Susan

2006-Jul-14 21:23 UTC

head link

RE: [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@us.ibm.com] 
Sent: Friday, July 14, 2006 1:03 PM
To: Krysan, Susan
Cc: xen-devel@lists.xensource.com
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 numberof 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



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

David F Barrera

2006-Jul-14 21:56 UTC

head link

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

Susan,

I retested with changeset 10710, and the test completed successfully. 
Also, we made a change to our automation scripts, so it is likely that 
my problem was due to that. At any rate, xm-test is running normally 
with changeset 10710.  Thanks.

David

Krysan, Susan wrote:> 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@us.ibm.com] 
> Sent: Friday, July 14, 2006 1:03 PM
> To: Krysan, Susan
> Cc: xen-devel@lists.xensource.com
> 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@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 



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

Krysan, Susan

2006-Jul-17 22:06 UTC

head link

[Xen-devel] xen test results on Unisys ES7000

July 17, 2006

 

Configuration:

 

Unisys ES7000/one

x86_64

16 physical processors 

24 GB RAM

SLES10 RC3 with xen-unstable changeset 10711

 

Ran xm-test (see results below) and successfully booted and ran LTP in
the following x86_64 SLES10 domUs:

            a. A uni-processor DomU with 1GB of memory

            b. A 4-processor DomU with 1GB of memory

            c. A uni-processor DomU with 8GB of memory

            d. A 4-processor DomU with 8GB of memory

            e. An 8-processor DomU with 23GB memory

 

Issues: None 

 

Xm-test execution summary:

  PASS:  105

  FAIL:  6

  XPASS: 0

  XFAIL: 3

 

Details:

 

 FAIL: 11_create_concurrent_pos

        Unknown reason

 

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

Krysan, Susan

2006-Jul-26 17:23 UTC

head link

[Xen-devel] xen test results on Unisys ES7000

July 26, 2006

 

Configuration:

 

Unisys ES7000/one

x86_64

32 physical processors 

32 GB RAM

SLES10 RC3 with xen-unstable changeset 10712

 

Ran xm-test (see results below) and successfully booted the following
x86_64 SLES10 domUs:

            a. A uni-processor DomU with 1GB of memory

            b. A 4-processor DomU with 1GB of memory

            c. A uni-processor DomU with 8GB of memory

            d. A 4-processor DomU with 8GB of memory

            e. An 32-processor DomU with 31GB memory

 

Issues: None 

 

Xm-test execution summary:

  PASS:  106

  FAIL:  5

  XPASS: 0

  XFAIL: 3

 

Details:

 

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

 

 

 

 

Thanks,

Sue Krysan

Linux Systems Group

Unisys Corporation

 

 



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

Krysan, Susan

2006-Jul-31 20:43 UTC

head link

[Xen-devel] xen test results on Unisys ES7000

July 31, 2006

 

Configuration:

 

Unisys ES7000/one

x86_64

32 physical processors 

32 GB RAM

SLES10 RC3 with xen-unstable changeset 10868

 

Ran xm-test (see results below) and successfully booted the following
x86_64 SLES10 domUs:

            a. A uni-processor DomU with 1GB of memory

            b. A 4-processor DomU with 1GB of memory

            c. A uni-processor DomU with 8GB of memory

            d. A 4-processor DomU with 8GB of memory

            e. A 32-processor DomU with 30GB memory

 

Issues: None 

 

Xm-test execution summary:

  PASS:  106

  FAIL:  5

  XPASS: 0

  XFAIL: 3

 

Details:

 

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

 

 

 

 

Thanks,

Sue Krysan

Linux Systems Group

Unisys Corporation

 

 

 

 

Thanks,

Sue Krysan

Linux Systems Group

Unisys Corporation

 

 



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

Ross Maxfield

2006-Jul-31 21:29 UTC

head link

[Xen-devel] [PATCH] Misaligned IO reads

Hello Keir,
This patch fixes a data corruption bug in hvm_pio_assist() of
xen/arch/x86/hvm/io.c.  When the OVERLAP flag is set and the guest is
running in real-mode regs->es is used in the generation of the
destination address passed to hvm_copy().  regs->es, however, has not
been initialized and bad happens.  Since __vmread() must be called to
obtain regs->es to remedy the bug, this patch instead calls __vmread to
obtain the GUEST_LINEAR_ADDRESS which removes the need to check if the
guest is in real-mode and hence also the need to adjust addr.  Since
this block of code is executed so rarely, there is no measurable
performance impact using this fix for real or protected mode guests.

Signed of by: Ross Maxfield <rmaxfiel@novell.com>


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

Woller, Thomas

2006-Aug-01 16:15 UTC

head link

RE: [Xen-devel] [PATCH] Misaligned IO reads

> This patch fixes a data corruption bug in hvm_pio_assist() of 
> xen/arch/x86/hvm/io.c.  When the OVERLAP flag is set and the 
> guest is running in real-mode regs->es is used in the 
> generation of the destination address passed to hvm_copy().  
> regs->es, however, has not been initialized and bad happens.  
> Since __vmread() must be called to obtain regs->es to remedy 
> the bug, this patch instead calls __vmread to obtain the 
> GUEST_LINEAR_ADDRESS which removes the need to check if the 
> guest is in real-mode and hence also the need to adjust addr. 
>  Since this block of code is executed so rarely, there is no 
> measurable performance impact using this fix for real or 
> protected mode guests.Ross, should a __vmread be in an hvm specific function? Maybe I''m
missing something but a __vmread VT instruction will GP on an AMD SVM
platform.
Thanks for any clarification
Tom 





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

Keir Fraser

2006-Aug-02 08:53 UTC

head link

Re: [Xen-devel] [PATCH] Misaligned IO reads

On 31 Jul 2006, at 22:29, Ross Maxfield wrote:
> This patch fixes a data corruption bug in hvm_pio_assist() of
> xen/arch/x86/hvm/io.c.  When the OVERLAP flag is set and the guest is
> running in real-mode regs->es is used in the generation of the
> destination address passed to hvm_copy().  regs->es, however, has not
> been initialized and bad happens.  Since __vmread() must be called to
> obtain regs->es to remedy the bug, this patch instead calls __vmread to
> obtain the GUEST_LINEAR_ADDRESS which removes the need to check if the
> guest is in real-mode and hence also the need to adjust addr.  Since
> this block of code is executed so rarely, there is no measurable
> performance impact using this fix for real or protected mode guests.
This is not the right fix -- VMX-specific code in a generic HVM 
function, and it''s too localised. I''ve made an alternative fix
in c/s
10894 which will initialise those extra fields in the regs structure 
for all PIO requests. Please test when it reaches the public tree.

  Thanks,
  Keir


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

Krysan, Susan

2006-Aug-08 18:03 UTC

head link

[Xen-devel] xen test results on Unisys ES7000

August 7, 2006

 

Configuration:

 

Unisys ES7000/one, x86_64

32 physical processors, 128 GB RAM

SLES10 RC3 with xen-unstable changeset 10949

 

Ran xm-test (see results below) and successfully booted the following
x86_64 SLES10 domUs:

            a. A uni-processor DomU with 1GB of memory

            b. A 4-processor DomU with 1GB of memory

            c. A uni-processor DomU with 8GB of memory

            d. A 4-processor DomU with 8GB of memory

 

Issues: bug #729 - domU migration causes fatal page fault crash

 

Xm-test fails when attempting to run 01_migrate_localhost_pos, so a
report file is not generated.  The output file is attached.

 

Thanks,

Sue Krysan

Linux Systems Group

Unisys Corporation

 

 




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

Xen devel - Jul 2006 - xen test results on Unisys ES7000

[Xen-devel] xen test results on Unisys ES7000

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

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

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

[Xen-devel] xen test results on Unisys ES7000

[Xen-devel] xen test results on Unisys ES7000

[Xen-devel] xen test results on Unisys ES7000

[Xen-devel] [PATCH] Misaligned IO reads

RE: [Xen-devel] [PATCH] Misaligned IO reads

Re: [Xen-devel] [PATCH] Misaligned IO reads

[Xen-devel] xen test results on Unisys ES7000