This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH][XM-TEST] Test for bug #533

To: Dan Smith <danms@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH][XM-TEST] Test for bug #533
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Tue, 14 Feb 2006 08:16:30 -0800
Cc: Xen Developers <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 14 Feb 2006 18:21:11 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <87slqmt0n3.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <87slqmt0n3.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Tue, Feb 14, 2006 at 07:34:24AM -0800, Dan Smith wrote:

> This patch adds a test that attempts to create and destroy a domain
> 1025 times.  Currently, this causes xm to crash after the 1014th cycle
> with the following stack trace:
> > shared object file: Too many open files

Thanks Dan.  I'll apply your patch soon.  Meanwhile, could you run this
test and then send the output of lsof when you're a long way in (but
before it crashes).  It should be pretty easy to figure out where you're
leaking that file descriptor from that.

> Since this test takes a long time to run, I have not enabled it by
> default, but it should be included in the tree to make bug #533 easily
> reproducible.
> Perhaps xm-test should have a configure option that enables long,
> exhaustive tests?

I thought we already had two speeds of xm-test.  Do you mean add a
third?  If so, that's fine, and a patch would be welcome!


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>