From: "J. Mayer" <l_indien@magic.fr>
To: qemu-devel@nongnu.org
Cc: marco <mmechelli@runbox.com>
Subject: Re: [Qemu-devel] qemu-system-ppc on a pc
Date: Sat, 05 Mar 2005 01:14:03 +0100 [thread overview]
Message-ID: <1109981643.5335.1238.camel@rapid> (raw)
In-Reply-To: <Pine.LNX.4.61.0503041517090.17058@pink.italy.ibm.com>
On Fri, 2005-03-04 at 15:26, marco wrote:
> Hello,
>
> I'm trying to run linux-ppc on an x86 pc host (Gentoo). I downloaded the
> disk image and kernel from freeoszoo and, when trying to run it, I get:
>
> pink qemu # qemu-system-ppc -prep -localtime -kernel ./zImage.prep ./linux-ppc.img
> *** ERROR: opcode 57 already assigned in opcode table 80
> *** ERROR: unable to insert opcode [00-80-57]
> *** ERROR initializing PPC instruction 0x00 0x80 0x57
> invalid/unsupported opcode: 12 - 02 - 18 (4bfffe05) 0xfffffffc 0
> Segmentation fault
Seems to me that you don't use qemu from CVS, but 0.6.1, am I right ?
Qemu PPC has long been broken when compiled with gcc 3.4.x.
Then, it seems you have two solutions:
- use gcc 3.3.x
- or use current qemu CVS repository.
--
J. Mayer <l_indien@magic.fr>
Never organized
next prev parent reply other threads:[~2005-03-05 0:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 14:26 [Qemu-devel] qemu-system-ppc on a pc marco
2005-03-05 0:14 ` J. Mayer [this message]
2005-03-07 13:58 ` marco
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=1109981643.5335.1238.camel@rapid \
--to=l_indien@magic.fr \
--cc=mmechelli@runbox.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).