From: Laszlo Ersek <lersek@redhat.com>
To: Gary Ching-Pang Lin <glin@suse.com>
Cc: edk2-devel@lists.sourceforge.net,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [edk2] OVMF hung on qemu 1.6.0 with KVM
Date: Wed, 28 Aug 2013 13:45:47 +0200 [thread overview]
Message-ID: <521DE2EB.9050404@redhat.com> (raw)
In-Reply-To: <20130828103552.GC2038@GaryOffice.site>
(qemu-devel CC'd)
On 08/28/13 12:35, Gary Ching-Pang Lin wrote:
> Hi,
>
> I recently updated qemu to 1.6.0 and found OVMF just showed a blank
> screen when kvm was enabled. I tried to dump OVMF log with the
> following commond but nothing was stored in debug.log.
>
> qemu-system-x86_64 -s -enable-kvm -bios OVMF.fd -debugcon file:debug.log -global isa-debugcon.iobase=0x402
>
> The kvm trace was recorded with "trace-cmd record -b 20000 -e kvm"
> and uploaded to the following link:
> https://docs.google.com/file/d/0B9hbtlc_aK_gcGh2TDZLUVlzWWc/edit?usp=sharing
>
> I found a similar case with kernel < 3.9, but I already upgraded linux
> kernel to 3.10.5, so this may be another bug.
Well, the usual first response in cases like this is...
Can you bisect qemu? :)
Laszlo
next parent reply other threads:[~2013-08-28 11:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130828103552.GC2038@GaryOffice.site>
2013-08-28 11:45 ` Laszlo Ersek [this message]
2013-08-28 11:49 ` [Qemu-devel] [edk2] OVMF hung on qemu 1.6.0 with KVM Andreas Färber
2013-08-28 12:10 ` Laszlo Ersek
2013-08-28 12:55 ` Andreas Färber
2013-08-28 14:09 ` Ludwig Nussel
2013-08-29 8:23 ` Gary Ching-Pang Lin
2013-08-29 16:04 ` Bruce Rogers
[not found] ` <521F1CB802000048000E30E0@suse.com>
2013-08-30 3:28 ` Gary Ching-Pang Lin
2013-08-30 5:59 ` Paolo Bonzini
2013-08-30 9:37 ` Laszlo Ersek
2013-08-30 11:58 ` Paolo Bonzini
2013-08-30 12:10 ` Gleb Natapov
2013-08-30 12:42 ` Paolo Bonzini
2013-08-30 17:33 ` Jordan Justen
2013-08-30 17:39 ` Jordan Justen
2013-08-30 18:44 ` Paolo Bonzini
2013-08-30 19:05 ` Jordan Justen
2013-08-31 7:00 ` Paolo Bonzini
2013-08-31 7:16 ` Jordan Justen
2013-09-02 2:58 ` Gary Ching-Pang Lin
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=521DE2EB.9050404@redhat.com \
--to=lersek@redhat.com \
--cc=edk2-devel@lists.sourceforge.net \
--cc=glin@suse.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).