From: acrux <acrux_it@libero.it>
To: Alexander Graf <agraf@suse.de>
Cc: 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: Wed, 27 Jan 2010 20:17:29 +0100 [thread overview]
Message-ID: <20100127201729.939169aa.acrux_it@libero.it> (raw)
In-Reply-To: <E5E3E1B3-7287-40F3-B819-5909F82320BB@suse.de>
[-- Attachment #1: Type: text/plain, Size: 950 bytes --]
On Mon, 25 Jan 2010 10:25:30 +0100
Alexander Graf <agraf@suse.de> wrote:
_omissis__
>
> Ugh. Please use --disable-kvm on such old kernel versions. KVM
> doesn't work on G4s (yet) anyway. I guess I'll need to add a minimum
> version check for KVM on ppc.
>
_cut__
thanks, it now compiles fine on both ppc32 and ppc64.
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.
2) with -M mac99 it boots but seems to be unable to find a proper IDE
device.
No problems, instead, with qemu-system-x86_64 when i
tried to install a guest linux x86 os on my ppc32 host.
greetings,
--
GNU/Linux on Power Architecture
CRUX PPC - http://cruxppc.org/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-01-27 20:17 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 ` acrux [this message]
2010-01-27 23:30 ` [Qemu-devel] " Alexander Graf
2010-01-28 0:28 ` acrux
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=20100127201729.939169aa.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).