Re: ppc32 build failed

[Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>]

(2010/11/19 15:01), Yang Rui Rui wrote:
> Hi,
>
> I searched the archive found some discutions about this, not fixed yet?
> could someone tell, is g4 kvm available now?

Hi, (added kvm-ppc to Cc)

I'm using g4 (Mac mini box) to run KVM.
   - though not tried 2.6.37-rc2 yet.

Aren't you using upstream qemu?
IIRC, ppc kvm needs to use upstream qemu.


You can see useful information on KVM "PowerPC port" page.
   http://www.linux-kvm.org/page/PowerPC

   -> no g4 example but we can find enough information.


BTW, why the entry "Book3S PPC32" in the processor support table
is still "NO", anyone?
   http://www.linux-kvm.org/page/Processor_support


I don't know well about PPC, so you need to ask Alex about
more technical issues.


Takuya


>
> powerpc g4 build failed (host kernel 2.6.37-rc2):
>
> CC ppc-softmmu/kvm.o
> /home/dave/qemu-kvm/target-ppc/kvm.c: In function 'kvm_arch_init_vcpu':
> /home/dave/qemu-kvm/target-ppc/kvm.c:81: error: 'struct kvm_sregs' has no member named 'pvr'
> /home/dave/qemu-kvm/target-ppc/kvm.c: In function 'kvm_arch_get_registers':
> /home/dave/qemu-kvm/target-ppc/kvm.c:168: error: 'struct kvm_sregs' has no member named 'u'
> /home/dave/qemu-kvm/target-ppc/kvm.c:180: error: 'struct kvm_sregs' has no member named 'u'
> /home/dave/qemu-kvm/target-ppc/kvm.c:185: error: 'struct kvm_sregs' has no member named 'u'
> /home/dave/qemu-kvm/target-ppc/kvm.c:186: error: 'struct kvm_sregs' has no member named 'u'
> /home/dave/qemu-kvm/target-ppc/kvm.c:187: error: 'struct kvm_sregs' has no member named 'u'
> /home/dave/qemu-kvm/target-ppc/kvm.c:188: error: 'struct kvm_sregs' has no member named 'u'
> /home/dave/qemu-kvm/target-ppc/kvm.c: At top level:
> /home/dave/qemu-kvm/target-ppc/kvm.c:261: error: conflicting types for 'kvm_arch_process_irqchip_events'
> /home/dave/qemu-kvm/qemu-kvm.h:692: error: previous declaration of 'kvm_arch_process_irqchip_events' was here
> make[1]: *** [kvm.o] Error 1
> make: *** [subdir-ppc-softmmu] Error 2
>