On 26/03/25 16:12, Cédric Le Goater wrote:
[ ... ]
You could use a buildroot image instead. :
https://github.com/buildroot/buildroot/blob/master/configs/qemu_ppc64le_powernv8_defconfig
Images pushed here :
https://github.com/legoater/qemu-ppc-boot/tree/main/buildroot/qemu_ppc64le_powernv8-2025.02
qemu-system-ppc64 -m 1G -M powernv10 \
-kernel ./buildroot/qemu_ppc64le_powernv8-2025.02/vmlinux \
-append root=/dev/nvme0n1 \
-device nvme,bus=pcie.2,addr=0x0,drive=drive0,serial=1234 \
-drive
file=./buildroot/qemu_ppc64le_powernv8-2025.02/rootfs.ext2,if=none,id=drive0,format=raw,cache=none
\
-device e1000e,bus=pcie.1,addr=0x0,netdev=net0 \
-netdev user,id=net0 \
-serial mon:stdio -nographic -snapshot
[ 0.010515922,5] OPAL v7.1-106-g785a5e307 starting...
...
[ 0.000000][ T0] Linux version 6.12.9 (legoater@ryzen)
(powerpc64le-buildroot-linux-gnu-gcc.br_real (Buildroot 2025.02)
13.3.0, GNU ld (GNU Binutils) 2.43.1) #1 SMP Wed Mar 26 11:11:35 CET 2025
...
Please use these images or the opbuild image which should also work but
the CPU won't be recognized as a POWER11.
Thank you, will use those images then.
opbuild image boots but since it doesn't "print" p11 in its dmesg log, the
powernv test fails with it. Will use your images.
Thanks,
- Aditya Gupta
Thanks,
C.
