|
|
|
|
|
|
|
|
|
|
xen-devel
RE: [Xen-devel] Re: Error while running the xm test suite: Cannot handle
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx wrote on 09/17/2008
05:45:14 PM:
> Daniel Magenheimer <dan.magenheimer@xxxxxxxxxx>
> Sent by: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>
> 09/17/2008 05:45 PM
>
> To
>
> Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Stefan Berger/Watson/IBM@IBMUS
>
> cc
>
> xen-devel@xxxxxxxxxxxxxxxxxxx
>
> Subject
>
> RE: [Xen-devel] Re: Error while running the xm test suite: Cannot
> handle page request order 0!
>
> Perhaps the cset numbers refer to 3.3-testing, not xen-unstable?
No, they refer to the staging tree. If no one else
is encountering these errors, please disregard for now. I'll find out what's
going on.
Stefan
> -----Original Message-----
> From: Keir Fraser [mailto:keir.fraser@xxxxxxxxxxxxx]
> Sent: Wednesday, September 17, 2008 3:40 PM
> To: Stefan Berger
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] Re: Error while running the xm test suite:
> Cannot handle page request order 0!
> On 17/9/08 22:23, "Stefan Berger" <stefanb@xxxxxxxxxx>
wrote:
> > I suspect a memory leak in your particular
configuration. It?x2019;d be
> > good to try to narrow down which changeset or range of changesets
> > introduced the problem.
>
> I narrowed it down as far as : 18411 fails and 18407 works, which
is
> very strange since I don't see any critical changes in between...
>
> Yes. 18411 affects only ia64. 18410 affects only internal ioemu (not
> used by default build). 18409 reverts 18408, and simply adds a
> wrapper around ?x2018;install?x2019; inside the tools/ directory.
Weird!
>
> -- Keir_______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- Re: [Xen-devel] Re: Error while running the xm test suite: Cannot handle page request order 0!, (continued)
|
|
|
|
|