From: Anthony Liguori <anthony@codemonkey.ws>
To: Christoph Hellwig <hch@lst.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] the qemu-iotests test suite is now available
Date: Tue, 23 Jun 2009 11:03:39 -0500 [thread overview]
Message-ID: <4A40FCDB.6090204@codemonkey.ws> (raw)
In-Reply-To: <20090622210523.GA8024@lst.de>
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
next prev parent reply other threads:[~2009-06-23 16:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 21:05 [Qemu-devel] the qemu-iotests test suite is now available Christoph Hellwig
2009-06-23 9:16 ` Kevin Wolf
2009-06-23 14:31 ` Christoph Hellwig
2009-06-23 14:36 ` Kevin Wolf
2009-06-23 16:41 ` Christoph Hellwig
2009-06-24 7:35 ` Kevin Wolf
2009-07-06 11:18 ` Kevin Wolf
2009-07-06 17:36 ` Christoph Hellwig
2009-07-07 7:30 ` Kevin Wolf
2009-09-11 14:04 ` Kevin Wolf
2009-09-11 18:40 ` Christoph Hellwig
2009-09-14 8:03 ` Kevin Wolf
2009-06-23 16:03 ` Anthony Liguori [this message]
2009-06-23 16:36 ` Christoph Hellwig
2009-06-24 9:12 ` Kevin Wolf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A40FCDB.6090204@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=hch@lst.de \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.