Messages in this thread | | | Date | Tue, 5 Jul 2022 18:07:17 +0200 | Subject | Re: [PATCH 2/2] kvm: rename KVM_MAX_VCPU_ID to, KVM_MAX_VCPU_IDS | From | Christian Zigotzky <> |
| |
On 14 September 2021 at 05:59 pm, Christian Zigotzky wrote: > Hello Juergen, > Hello All, > > Since the RC1 of kernel 5.13, -smp 2 and -smp 4 don't work with a > virtual e5500 QEMU KVM-HV machine anymore. [1] > I see in the serial console, that the uImage doesn't load. I use the > following QEMU command for booting: > > qemu-system-ppc64 -M ppce500 -cpu e5500 -enable-kvm -m 1024 -kernel > uImage -drive format=raw,file=MintPPC32-X5000.img,index=0,if=virtio > -netdev user,id=mynet0 -device virtio-net,netdev=mynet0 -append "rw > root=/dev/vda" -device virtio-vga -device virtio-mouse-pci -device > virtio-keyboard-pci -device pci-ohci,id=newusb -device > usb-audio,bus=newusb.0 -smp 4 > > The kernels boot without KVM-HV. > > Summary for KVM-HV: > > -smp 1 -> works > -smp 2 -> doesn't work > -smp 3 -> works > -smp 4 -> doesn't work > > I used -smp 4 before the RC1 of kernel 5.13 because my FSL P5040 BookE > machine [2] has 4 cores. > > Does this patch solve this issue? [3] > > Thanks, > Christian > > [1] https://lists.ozlabs.org/pipermail/linuxppc-dev/2021-May/229103.html > [2] http://wiki.amiga.org/index.php?title=X5000 > [3] > https://lists.ozlabs.org/pipermail/linuxppc-dev/2021-September/234152.html Hello,
Since the RC5 of kernel 5.19, -smp 2 and -smp 4 work again. I don't know which patch has solved the issue.
Cheers, Christian
| |