Ewan,
We are looking into the xm-test failures.
regarding
> FAIL: 01_enforce_dom0_cpus_basic_pos
> /proc/cpuinfo says xend didn't enforce dom0_cpus (30 != 1)
We noticed that when this test resets dom0_cpus to 1 it takes a few seconds for
/proc/cpuinfo to reduce from 32 processors to 1 processor. So we put in a
sleep of 10 seconds in the test script, right before it checks /proc/cpuinfo.
Then the test succeeds. We see the same failure with 16 processors, but not 8
processors. Should this test be patched to introduce a sleep statement for
systems with 16 or more processors?
Thanks,
Sue Krysan
Linux Systems Group
Unisys Corporation
-----Original Message-----
From: Ewan Mellor [mailto:ewan@xxxxxxxxxxxxx]
Sent: Wednesday, April 26, 2006 6:42 PM
To: Krysan, Susan
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx; Vessey, Bruce A; Ikhizgilov, Timur;
Carb, Brian A
Subject: Re: [Xen-devel] xm-test results
On Tue, Apr 25, 2006 at 03:52:58PM -0400, Krysan, Susan wrote:
> I am part of the Unisys xen team. We plan to run xm-test weekly and post the
> results.
>
> Here is our first posting.
>
> April 25, 2006
>
> Configuration:
>
> SLES 10 Beta 10
> Unisys ES7000/1
> x86_64
> 32 processors
> 16 GB RAM
> xen-unstable changeset 9734
>
> Xm-test execution summary:
> PASS: 108
> FAIL: 7
> XPASS: 0
> XFAIL: 3
>
>
> Details:
>
> FAIL: 13_create_multinic_pos
> (7 nics) Console didn't respond probably crashed!
>
> FAIL: 01_enforce_dom0_cpus_basic_pos
> /proc/cpuinfo says xend didn't enforce dom0_cpus (30 != 1)
>
> FAIL: 01_memset_basic_pos
> DomU reported incorrect memory amount 59 MB
>
> FAIL: 03_memset_random_pos
> Expected 61 MB, domU reported 59 MB
Will you be drilling down into these failures? That would certainly be
appreciated. The memset failures happen only on 64-bit platforms, and
no-one's had time to figure out whether this is a conversion issue somewhere
in the test or Xend or Xen itself. The enforce_dom0_cpus failure is odd,
given that 30 is neither the number of physical CPUs, nor a power of two, nor
the number that was requested! The multinic crash is certainly a real kernel
bug, and a backtrace or some debugging for that would be very useful too.
Thanks,
Ewan.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home