From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 108381] New: KVM crashes when using qemu/kvm with specific BIOS
Date: Tue, 24 Nov 2015 01:46:04 +0000 [thread overview]
Message-ID: <bug-108381-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=108381
Bug ID: 108381
Summary: KVM crashes when using qemu/kvm with specific BIOS
Product: Virtualization
Version: unspecified
Kernel Version: 4.2.5
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: mytbk920423@gmail.com
Regression: No
Created attachment 195281
--> https://bugzilla.kernel.org/attachment.cgi?id=195281&action=edit
The BIOS that triggers the bug, and dmesg log
I've built a coreboot image with UEFI payload and used it in QEMU, but it
causes a KVM crash. What's more, the system freezes if I run QEMU in X.
the command line I use:
$ qemu-system-x86_64 -enable-kvm -M q35 -m 2G -bios coreboot_uefi.rom
I ran it on a tty with -nographic option and I got a kernel log.
This bug doesn't appear in Linux 4.1.12 LTS kernel.
--
You are receiving this mail because:
You are watching the assignee of the bug.
reply other threads:[~2015-11-24 1:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-108381-28872@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox