From: acrux <acrux_it@libero.it>
To: Alexander Graf <agraf@suse.de>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu-0.12.2 compiling error (on ppc32/ppc64): kvm.c:50: error: 'struct kvm_sregs' has no member named 'pvr'
Date: Thu, 28 Jan 2010 01:28:47 +0100 [thread overview]
Message-ID: <20100128012847.c18fae31.acrux_it@libero.it> (raw)
In-Reply-To: <958679C7-6D2F-4E6F-98DE-1B78CEDC704E@suse.de>
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
On Thu, 28 Jan 2010 00:30:23 +0100
Alexander Graf <agraf@suse.de> wrote:
_omissis__
> > I've encuntered two issues under my quick test with CRUX PPC 2.6
> > (32bit) as host. This was my start command:
> >
> > $ qemu-system-ppc -m 256 -localtime -hda 25a_qcow.img -cdrom
> > crux-ppc-2.5a.iso -boot d
> >
> > The apple32 boot kernel on that iso image is linux-2.6.29.4
> >
> > 1) with -M g3beige it boots fine but segfaults loading the system.
>
> Please use gdb's backtrace feature to find out why/where it breaks.
>
ok, i'll give a try
> > 2) with -M mac99 it boots but seems to be unable to find a proper
> > IDE device.
>
> Yeah, that's because your guest kernel doesn't have cmd64x support
> compiled in.
>
it's the same bootkernel as above with cmd64x module builtin therefore
it's an unexpected error.
--acrux
--
GNU/Linux on Power Architecture
CRUX PPC - http://cruxppc.org/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2010-01-28 1:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 21:16 [Qemu-devel] qemu-0.12.2 compiling error (on ppc32/ppc64): kvm.c:50: error: 'struct kvm_sregs' has no member named 'pvr' acrux
2010-01-25 9:25 ` Alexander Graf
2010-01-25 10:28 ` [Qemu-devel] " Michael S. Tsirkin
2010-01-25 10:33 ` Alexander Graf
2010-01-27 19:17 ` [Qemu-devel] " acrux
2010-01-27 23:30 ` Alexander Graf
2010-01-28 0:28 ` acrux [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=20100128012847.c18fae31.acrux_it@libero.it \
--to=acrux_it@libero.it \
--cc=agraf@suse.de \
--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).