From: Jamie Aczel <7hs@comcast.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Confused
Date: Fri, 25 Mar 2005 22:52:11 -0800 [thread overview]
Message-ID: <a089cb1671c3812747e56634fccea5ab@comcast.net> (raw)
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;
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.
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...
next reply other threads:[~2005-03-26 7:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-26 6:52 Jamie Aczel [this message]
2005-03-26 18:03 ` [Qemu-devel] Confused Mike Swanson
2005-03-27 0:56 ` Jim C. Brown
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=a089cb1671c3812747e56634fccea5ab@comcast.net \
--to=7hs@comcast.net \
--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).