From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] KVM emulation failure with recent kernel and QEMU Seabios
Date: Thu, 12 Mar 2015 09:14:55 +0100 [thread overview]
Message-ID: <55014AFF.60304@siemens.com> (raw)
In-Reply-To: <1426147889.1722.13.camel@nilsson.home.kraxel.org>
Am 2015-03-12 um 09:11 schrieb Gerd Hoffmann:
> On Do, 2015-03-12 at 09:09 +0100, Jan Kiszka wrote:
>> Hi,
>>
>> apparently since the latest QEMU updates I'm getting this once in a
>> while:
>
> http://www.seabios.org/pipermail/seabios/2015-March/008897.html
OK... So we are waiting on a stable release to pull in new binaries with
this fix? A matter of days?
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2015-03-12 8:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 8:09 [Qemu-devel] KVM emulation failure with recent kernel and QEMU Seabios Jan Kiszka
2015-03-12 8:11 ` Gerd Hoffmann
2015-03-12 8:14 ` Jan Kiszka [this message]
2015-03-12 8:23 ` Gerd Hoffmann
2015-03-16 18:16 ` Bandan Das
2015-03-17 7:05 ` Gerd Hoffmann
2015-03-17 17:08 ` Bandan Das
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=55014AFF.60304@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--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).