Le mer. 15 avr. 2020 à 15:08, Dennis Clarke <dcla...@blastwave.org> a écrit :
> This is inside a qemu ppc64 instance wherein attempting to use POWER9
> or the POWER8 cpu types. Seems to result in a kernel panic repeatedly :
I have a QEMU PPC64EL image running Debian Buster, and it has been
rock-solid for my usage (I checked my AltiVec code for ZFS was working
on little-endian system in there, along with some AltiVec crypto - all
my PPC hardware is big-endian).
I'm running 4.19.0-6 from Buster, but from the command-line in the
host filesystem, not from inside the image. I'm also using a newer
QEMU (4.1, I've had issue with SSH'ing into the machine with 4.2),
machine & CPU definitions:
/usr/local/qemu-4.1.0/bin/qemu-system-ppc64 \
-machine pseries-4.1 -cpu power9 -smp 12 -m 12G \
-drive file=/dev/x10drldatapool/vm-ppc64el,format=raw \
-monitor stdio -vnc :2 \
-kernel vmlinux-4.19.0-6-powerpc64le \
-append "root=/dev/qemuppc64el-vg/root" \
-initrd initrd.img-4.19.0-6-powerpc64le \
-device virtio-net-pci,netdev=usernet -netdev
user,id=usernet,hostfwd=tcp::10002-:22
Just dist-upgrade'd it from ~10.1 to the 10.3 of today, and didn't
have any issue...
Maybe the newer kernels are the problem, did you try standard Buster ?
(PPC64EL is officially supported by Debian, unlike the big-endian
versions which are ports).
Cordially,
--
Romain Dolbeau
