qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Christoph Hellwig <hch@lst.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] the qemu-iotests test suite is now available
Date: Tue, 23 Jun 2009 18:36:37 +0200	[thread overview]
Message-ID: <20090623163637.GA27211@lst.de> (raw)
In-Reply-To: <4A40FCDB.6090204@codemonkey.ws>

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.

  reply	other threads:[~2009-06-23 16:36 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
2009-06-23 16:36   ` Christoph Hellwig [this message]
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=20090623163637.GA27211@lst.de \
    --to=hch@lst.de \
    --cc=anthony@codemonkey.ws \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).