Hi Scott, thank you very much for your infos are really appreciated because let me know better this hardware
Kind regards Luigi Burdo AmigaOne X5000 beta Tester > From: o...@buserror.net > To: intermedi...@hotmail.com > Date: Thu, 17 Mar 2016 11:23:10 -0500 > Subject: Re: Freescale P5020 cpu will be kvm-pr? > CC: linuxppc-dev@lists.ozlabs.org; matt...@a-eon.com; cont...@a-eon.com; > chzigot...@xenosoft.de > > On Thu, 2016-03-17 at 14:38 +0100, luigi burdo wrote: > > Hi Scott, > > this is my Kernel 4.5 dmesg > > > > dmesg | grep -i MMU > > [ 0.000000] MMU: Supported page sizes > > [ 0.000000] MMU: Book3E HW tablewalk not supported > > [ 0.000000] mmu_features = 0x000a0010 > > [ 0.000000] MMU: Allocated 2112 bytes of context maps for 255 contexts > > > > dmesg | grep -i e500 > > [ 0.001787] e500 family performance monitor hardware support registered > > > > > > dmesg | grep -i hypervisor > > > > [ 0.396726] ePAPR hypervisor byte channel driver > > [ 3.240020] Freescale hypervisor management driver > > [ 3.240024] fsl-hv: no hypervisor found > > None of these messages are a problem. > > "Book3E HW tablewalk" is for e6500, not e5500. fsl-hv is for the Freescale > Embedded Hypervisor (Topaz), not KVM. > > > > i attached my kenrel .config > > > > My qemu-ppc-64 crash, note i have the same crash > > > > qemu: fatal: This KVM version does not support PAPR > > You need to tell QEMU to use the appropriate CPU type (e5500) and platform > (ppce500). PAPR is for book3s, which is what QEMU defaults to. > > -Scott > > _______________________________________________ > Linuxppc-dev mailing list > Linuxppc-dev@lists.ozlabs.org > https://lists.ozlabs.org/listinfo/linuxppc-dev
_______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev