From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MJ8TQ-0001pu-9E for qemu-devel@nongnu.org; Tue, 23 Jun 2009 12:03:52 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MJ8TL-0001lt-K0 for qemu-devel@nongnu.org; Tue, 23 Jun 2009 12:03:51 -0400 Received: from [199.232.76.173] (port=56884 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MJ8TL-0001lg-1U for qemu-devel@nongnu.org; Tue, 23 Jun 2009 12:03:47 -0400 Received: from fg-out-1718.google.com ([72.14.220.153]:32380) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MJ8TK-00039Z-Dd for qemu-devel@nongnu.org; Tue, 23 Jun 2009 12:03:46 -0400 Received: by fg-out-1718.google.com with SMTP id e21so59642fga.8 for ; Tue, 23 Jun 2009 09:03:45 -0700 (PDT) Message-ID: <4A40FCDB.6090204@codemonkey.ws> Date: Tue, 23 Jun 2009 11:03:39 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] the qemu-iotests test suite is now available References: <20090622210523.GA8024@lst.de> In-Reply-To: <20090622210523.GA8024@lst.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Christoph Hellwig Cc: qemu-devel@nongnu.org Christoph Hellwig wrote: > I've now uploaded the qemu-iotests suite which exercises the I/O > path using qemu-img, qemu-io and basic qemu use without a guest. > > It's available from my personal kernel.org area at: > > git://git.kernel.org/pub/scm/linux/kernel/git/hch/qemu-iotests.git > > with gitweb at > > http://git.kernel.org/?p=linux/kernel/git/hch/qemu-iotests.git > > To run it simply do a ./check (defaults to raw format) or ./check > -qcow2. > > Thanks to Kevin Wolf for sharing his qcow2 test script which make up > the most interesting scripts in the test suite, and for SGI for beeing > able to re-use the xfsqa test driver. > This is great! 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. Why does it need to run qemu? Shouldn't qemu-io/qemu-img be enough? Regards, Anthony Liguori