qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Confused
Date: Sat, 26 Mar 2005 19:56:44 -0500	[thread overview]
Message-ID: <20050327005644.GA3001@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <a089cb1671c3812747e56634fccea5ab@comcast.net>

On Fri, Mar 25, 2005 at 10:52:11PM -0800, Jamie Aczel wrote:
> Hello,
> 
> I'm attempting to sort out the discrepancies between a "WINE for PPC"  
> guide posted on some mailing lists last year  
> (http://lists.terrasoftsolutions.com/pipermail/yellowdog-general/2004- 
> June/014468.html) which makes references to the "qemu-i386" binary;
> 
> The reality, which is that none of the bundled versions of QEMU for PPC  
> I've found, nor a self-compile of QEMU 0.6.1, include this binary;
> 

qemu-i386 was still included in 0.6.0 - I haven't checked more recent versions
but I don't remember it being removed from the source.

Normally qemu is used to emulate an entire system: cpu, ram, hard disk, etc.
qemu-i386 provides translations for individual linux binaries - also
provided a translation layer so the binary could make syscalls to the native
kernel. You need to do a './configure --target-list=i386' in order to enable
it.

> and another mailing list post (URL lost, unfortunately) that explained  
> that the "qemu-i386" binary is the 'fast' version of the program for  
> x86 virtualization on x86 hosts, with no instruction set translation,  
> and should not exist or run on PPC systems.

This is wrong. The person was either thinking about qemu-fast (now defunct)
or the qemu accelerator (also known as kqemu). qemu-i386 is perfect for
running x86 binaries on PPC (such as Wine) via translation.

> 
> If that's correct, how did the writer of the first post get it to work?  
> Is there any way to run Linux/x86 programs (specifically WINE) in  
> recent QEMU versions without installing an entire host system? I'm  
> actually using OS X, so if the platforms are too different for seamless  
> emulation across them, this searching may all be useless...
> 

The catch is that qemu-i386 will only work when you are trying to run Linux
x86 binaries on a non-x86 Linux host. It works by translating between different
kernel archs. To get it to work on OSX, you'd have to do what (last I heard -
this may no longer be correct) Darwine is doing: provide a translation layer
between qemu-i386 and OSX, that converts Linux syscalls into OSX calls.

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.

      parent reply	other threads:[~2005-03-27  1:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-26  6:52 [Qemu-devel] Confused Jamie Aczel
2005-03-26 18:03 ` Mike Swanson
2005-03-27  0:56 ` Jim C. Brown [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=20050327005644.GA3001@jbrown.mylinuxbox.org \
    --to=jma5@umd.edu \
    --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).