All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Laszlo Ersek \(Red Hat\)" <1888971@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1888971] Re: SMI trigger causes hang with multiple cores
Date: Mon, 27 Jul 2020 10:27:13 -0000	[thread overview]
Message-ID: <159584563401.18374.11528583449746322869.malone@soybean.canonical.com> (raw)
In-Reply-To: 159573587135.29737.8295812528041177661.malonedeb@chaenomeles.canonical.com

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


  reply	other threads:[~2020-07-27 10:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-26  3:57 [Bug 1888971] [NEW] SMI trigger causes hang with multiple cores Naresh GS
2020-07-27 10:27 ` Laszlo Ersek (Red Hat) [this message]
2020-07-31  6:32 ` [Bug 1888971] " Naresh GS
2020-07-31  9:44 ` Laszlo Ersek (Red Hat)
2020-08-12 11:35 ` Laszlo Ersek (Red Hat)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=159584563401.18374.11528583449746322869.malone@soybean.canonical.com \
    --to=1888971@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.