Does coreboot do anything to set up an SMI handler? Does it relocate SMBASE for all processors?
Misbehavior upon raising an SMI is fully expected, unless the guest (usually the guest firmware) sets up SMI handling properly. The bug report currently includes only two bits of information about guest actions, namely "coreboot.rom" and "writing 0x00 in IO port 0xB2". Thus far a guest crash looks entirely reasonable to me. Did you intend to attach "1.txt"? -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1888971 Title: SMI trigger causes hang with multiple cores Status in QEMU: New Bug description: When using qemu , SMI trigger causes hang/reboot under following conditions: 1. No KVM but there are more than 1 threads (-smp > 1) 2. When using KVM. Info: qemu-system-x86_64 --version QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.29) Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers SMI trigger was done by writing 0x00 in IO port 0xB2. Command: No failure in SMI trigger when using the below command: qemu-system-x86_64 -M pc-q35-bionic -smp 1 -bios build/coreboot.rom -serial stdio -hda ../linux.img -m 2048 | tee 1.txt Hang/resets with below commands: qemu-system-x86_64 -M pc-q35-bionic -smp 2 -bios build/coreboot.rom -serial stdio -hda ../linux.img -m 2048 | tee 1.txt sudo qemu-system-x86_64 -M pc-q35-bionic,accel=kvm -smp 1 -bios build/coreboot.rom -serial stdio -hda ../linux.img -m 2048 | tee 1.txt To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1888971/+subscriptions
