From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ewan Mellor Subject: Re: [PATCH][XM-TEST] Test for bug #533 Date: Tue, 14 Feb 2006 08:16:30 -0800 Message-ID: <20060214161630.GA3435@localhost.localdomain> References: <87slqmt0n3.fsf@caffeine.beaverton.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <87slqmt0n3.fsf@caffeine.beaverton.ibm.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Dan Smith Cc: Xen Developers List-Id: xen-devel@lists.xenproject.org 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! Ewan.