From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MJ8zG-0000tm-IA
	for qemu-devel@nongnu.org; Tue, 23 Jun 2009 12:36:46 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MJ8zB-0000pG-Me
	for qemu-devel@nongnu.org; Tue, 23 Jun 2009 12:36:45 -0400
Received: from [199.232.76.173] (port=35402 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MJ8zB-0000p5-B1
	for qemu-devel@nongnu.org; Tue, 23 Jun 2009 12:36:41 -0400
Received: from verein.lst.de ([213.95.11.210]:56814)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA1:24) (Exim 4.60)
	(envelope-from <hch@lst.de>) id 1MJ8zA-0001fE-OI
	for qemu-devel@nongnu.org; Tue, 23 Jun 2009 12:36:41 -0400
Date: Tue, 23 Jun 2009 18:36:37 +0200
From: Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] the qemu-iotests test suite is now available
Message-ID: <20090623163637.GA27211@lst.de>
References: <20090622210523.GA8024@lst.de> <4A40FCDB.6090204@codemonkey.ws>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4A40FCDB.6090204@codemonkey.ws>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Christoph Hellwig <hch@lst.de>, qemu-devel@nongnu.org

On Tue, Jun 23, 2009 at 11:03:39AM -0500, Anthony Liguori wrote:
> 
> The only thing that would be nice to have is the ability to point it at 
> a build directory.  Setting PATH isn't enough because it expects a qemu 
> executable whereas my build directory has a qemu-system-x86_64 executable.

Now that you remember it I remember the qemu-system-x86_64 problem.  I
think we can try the various qemu-system-$foo binaries instead.

> Why does it need to run qemu?  Shouldn't qemu-io/qemu-img be enough?

Test 007 uses the savevm command in the qemu monitor.  I suspect we
could appromiate it whith the snapshot commands in qemu-img, but
touching existing testcases is pretty nasty.