I was able to reproduce a crashing bug in qemu-system-arm on armv7 host. I'm _not_ going to claim this is the same bug that Debian is seeing, but it might be.
It's deep inside TCG and unfortunately there is not a lot of useful information in the stack trace. However it's clearly a bug in qemu. Core was generated by `/usr/bin/qemu-system-arm -global virtio-blk-device.scsi=off -enable-fips -nodef'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0xab6a7aa8 in ?? () [Current thread is 1 (Thread 0xaa9f7f90 (LWP 25252))] (gdb) bt #0 0xab6a7aa8 in ?? () #1 0xaba87ad0 in code_gen_buffer () #2 0x006291e0 in cpu_tb_exec (itb=<optimized out>, itb=<optimized out>, cpu=<optimized out>) at /usr/src/debug/qemu-2.11.0-4.fc28.arm/accel/tcg/cpu-exec.c:167 #3 cpu_loop_exec_tb (tb_exit=<synthetic pointer>, last_tb=<synthetic pointer>, tb=<optimized out>, cpu=<optimized out>) at /usr/src/debug/qemu-2.11.0-4.fc28.arm/accel/tcg/cpu-exec.c:627 #4 cpu_exec (cpu=<optimized out>) at /usr/src/debug/qemu-2.11.0-4.fc28.arm/accel/tcg/cpu-exec.c:736 #5 0x005efae4 in qemu_tcg_cpu_thread_fn (arg=0x13ce3e0) at /usr/src/debug/qemu-2.11.0-4.fc28.arm/cpus.c:1270 #6 0xb53f3f1c in start_thread () from /lib/libpthread.so.0 #7 0xb53790d8 in ?? () from /lib/libc.so.6 Backtrace stopped: previous frame identical to this frame (corrupt stack?) I'm using: * qemu-system-arm-2.11.0-4.fc28.armv7hl * kernel-lpae-4.15.0-0.rc9.git2.1.fc28.armv7hl Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v