From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MOUs1-0006QL-1N
	for qemu-devel@nongnu.org; Wed, 08 Jul 2009 06:59:25 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MOUrw-0006K4-Hk
	for qemu-devel@nongnu.org; Wed, 08 Jul 2009 06:59:24 -0400
Received: from [199.232.76.173] (port=47291 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MOUrw-0006Jw-DB
	for qemu-devel@nongnu.org; Wed, 08 Jul 2009 06:59:20 -0400
Received: from verein.lst.de ([213.95.11.210]:44799)
	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 1MOUrv-00015z-Tb
	for qemu-devel@nongnu.org; Wed, 08 Jul 2009 06:59:20 -0400
Date: Wed, 8 Jul 2009 12:59:15 +0200
From: Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] [PATCH] qemu-iotests: look for qemu-iotests-$ARCH
Message-ID: <20090708105915.GA14142@lst.de>
References: <20090707180346.GA6233@lst.de> <4A545A1B.1080606@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4A545A1B.1080606@redhat.com>
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: Kevin Wolf <kwolf@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>, qemu-devel@nongnu.org

On Wed, Jul 08, 2009 at 10:34:35AM +0200, Kevin Wolf wrote:
> Christoph Hellwig schrieb:
> > Look for the binary as installed by qemu make install instead of
> > requiring the qemu symlink.  Note that we need a couple of regular
> > expressions to munge the uname output into the architecture name
> > qemu expects.
> 
> I don't completely understand your goal here. Why would you want to use
> the host architecture for the guest, too? If anything this makes tests
> behave differently on different hosts. If, say, qemu-system-x86_64 is
> available depends on the configure options rather than on the host. And
> qemu isn't a symlink AFAIK, but the traditional name of qemu-system-i386
> (or has this changed recently?).

I did this from the kvm point of view where normally host equals guest
(modulo differences like i386 vs x86_64).  In my installation qemu was a
symlink, not sure if this was the original or if I did it manually at
some point.

So what method of finding a suitable qemu binary do you suggest instead?
I'm pretty open for doing anything that works.