qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alexander Graf <agraf@suse.de>
Cc: "kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Dushyant Bansal <cs5070214@cse.iitd.ernet.in>
Subject: [Qemu-devel] Re: qemu compiling error on ppc64: kvm.c:81: error:  ‘struct kvm_sregs’ has no member named ‘pvr’
Date: Fri, 04 Feb 2011 19:35:01 +0100	[thread overview]
Message-ID: <4D4C46D5.6070408@siemens.com> (raw)
In-Reply-To: <57F58C04-DDF3-4F8C-9BC3-DAED54D2D088@suse.de>

On 2011-02-04 15:43, Alexander Graf wrote:
> 
> On 04.02.2011, at 14:25, "Dushyant Bansal" <cs5070214@cse.iitd.ernet.in> wrote:
> 
>> Hi,
>>  I am trying to install kvm on ppc64 system (imac G5). I have built
>> kernel with kvm module. When I try to install qemu, I am getting this
>> error
>>
>> $ ./configure --enable-kvm --target-list="ppc-softmmu"
>> $ make
>>
>> [...]
>>  CC    slirp/tftp.o
>>  CC    libdis/ppc-dis.o
>>  GEN   config-target.h
>>  CC    ppc-softmmu/arch_init.o
>>  CC    ppc-softmmu/cpus.o
>>  GEN   ppc-softmmu/hmp-commands.h
>>  GEN   ppc-softmmu/qmp-commands.h
>>  CC    ppc-softmmu/monitor.o
>>  CC    ppc-softmmu/machine.o
>>  CC    ppc-softmmu/gdbstub.o
>>  CC    ppc-softmmu/balloon.o
>>  CC    ppc-softmmu/virtio-blk.o
>>  CC    ppc-softmmu/virtio-balloon.o
>>  CC    ppc-softmmu/virtio-net.o
>>  CC    ppc-softmmu/virtio-serial-bus.o
>>  CC    ppc-softmmu/virtio-pci.o
>>  CC    ppc-softmmu/vhost_net.o
>>  CC    ppc-softmmu/rwhandler.o
>>  CC    ppc-softmmu/kvm.o
>> /home/user/project/qemu/target-ppc/kvm.c: In function ‘kvm_arch_init_vcpu’:
>> /home/user/project/qemu/target-ppc/kvm.c:81: error: ‘struct kvm_sregs’ has
>> no member named ‘pvr’
> 
> Hrm. This means that your kernel headers in /usr/include/linux are too old. Can you try and find out which kernel version they are from please?

< 2.6.33. Lacking build-time KVM_CAP check? Or is such a kernel too old
anyway? Then catch it during configure and point the user to... well...
there is no kvm-kmod with kernel header updates for PowerPC. Hmm... ;)

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2011-02-04 18:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-04 13:25 [Qemu-devel] qemu compiling error on ppc64: kvm.c:81: error: ‘struct kvm_sregs’ has no member named ‘pvr’ Dushyant Bansal
2011-02-04 14:43 ` [Qemu-devel] " Alexander Graf
2011-02-04 18:35   ` Jan Kiszka [this message]
2011-02-04 20:03     ` Alexander Graf
2011-02-04 19:19   ` Dushyant Bansal
2011-02-04 20:04     ` Alexander Graf
2011-02-15 14:21       ` Dushyant Bansal
2011-02-15 14:33         ` Alexander Graf
2011-02-15 15:59           ` [Qemu-devel] Re: qemu compiling error on ppc64: kvm.c:81: error: 'struct kvm_sregs' has no member named 'pvr' Dushyant Bansal
2011-02-16  9:09             ` Avi Kivity
2011-02-25 16:17               ` Dushyant Bansal

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=4D4C46D5.6070408@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=agraf@suse.de \
    --cc=cs5070214@cse.iitd.ernet.in \
    --cc=kvm-ppc@vger.kernel.org \
    --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).