qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-iotests: look for qemu-iotests-$ARCH
Date: Wed, 8 Jul 2009 13:21:14 +0200	[thread overview]
Message-ID: <20090708112114.GA15008@lst.de> (raw)
In-Reply-To: <4A547E5A.7050404@redhat.com>

On Wed, Jul 08, 2009 at 01:09:14PM +0200, Kevin Wolf wrote:
> I'm not sure that the KVM point of view really matters here. I can see
> two possible use cases for qemu: Either we just start it up without a
> guest OS to do things like a simple savevm, then TCG is just as good. Or
> we boot up a guest OS, then we obviously need the architecture matching
> the guest, not the host.

Right now we don't use any guest so that it doesn't really matter.  If
we actually end up running a guest we should agree on an architecture,
and also boundle the require guest (which would have to be a really
minimal one) in the qemu-iotests repository.  But for now I'd just avoid
requiring any guests.

> Maybe something like trying qemu-system-x86_64, then qemu-kvm, then
> qemu? We could use i386 guests on every host then. If it's accelerated
> with KVM, kqemu or not at all doesn't really matter.

Ok, fine with me.  I'll respin the patch.

      reply	other threads:[~2009-07-08 11:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-07 18:03 [Qemu-devel] [PATCH] qemu-iotests: look for qemu-iotests-$ARCH Christoph Hellwig
2009-07-08  8:34 ` Kevin Wolf
2009-07-08 10:59   ` Christoph Hellwig
2009-07-08 11:09     ` Kevin Wolf
2009-07-08 11:21       ` Christoph Hellwig [this message]

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=20090708112114.GA15008@lst.de \
    --to=hch@lst.de \
    --cc=kwolf@redhat.com \
    --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).