socket: 0.988 device: 0.961 files: 0.914 PID: 0.905 debug: 0.856 vnc: 0.839 permissions: 0.832 performance: 0.826 network: 0.777 boot: 0.758 graphic: 0.636 KVM: 0.623 semantic: 0.539 other: 0.423 qemu crashes with assertion error `!mr->container' failed Re-production steps: git clone today's qemu git tree (4th Oct 2017) ./configure --target-list=ppc64-softmmu && make -j 8 Run the device-crash-test from scripts folder, seeing the following error INFO: running test case: machine=bamboo binary=ppc64-softmmu/qemu-system-ppc64 device=pcie-pci-bridge accel=kvm WARNING: qemu received signal -6: ppc64-softmmu/qemu-system-ppc64 -chardev socket,id=mon,path=/var/tmp/qemu-30972-monitor.sock -mon chardev=mon,mode=control -display none -vga none -S -machine bamboo,accel=kvm -device pcie-pci-bridge CRITICAL: failed: machine=bamboo binary=ppc64-softmmu/qemu-system-ppc64 device=pcie-pci-bridge accel=kvm CRITICAL: cmdline: ppc64-softmmu/qemu-system-ppc64 -S -machine bamboo,accel=kvm -device pcie-pci-bridge CRITICAL: log: qemu-system-ppc64: /home/nasastry/qemu/memory.c:1699: memory_region_finalize: Assertion `!mr->container' failed. CRITICAL: log: warning: KVM does not support watchdog CRITICAL: exit code: -6 I think this should be fixed by this patch here: https://lists.gnu.org/archive/html/qemu-devel/2017-09/msg06696.html ("hw/pci-bridge/pcie_pci_bridge: properly handle MSI unavailability case") With the mentioned patch not seeing the Abort. # ppc64-softmmu/qemu-system-ppc64 -S -machine bamboo,accel=kvm -device pcie-pci-bridge gtk initialization failed warning: KVM does not support watchdog Thanks!! As per previous comments, this bug was fixed by commit https://git.qemu.org/?p=qemu.git;a=commitdiff;h=d659d94013390238961fac741572306c95496bf5 (released in QEMU v2.11.0): commit d659d94013390238961fac741572306c95496bf5 Author: Aleksandr Bezzubikov