From: Jan Kiszka <jan.kiszka@siemens.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Pierre Riteau <Pierre.Riteau@irisa.fr>, KVM list <kvm@vger.kernel.org>
Subject: Re: Seabios incompatible with Linux 2.6.26 host?
Date: Fri, 05 Feb 2010 17:53:18 +0100 [thread overview]
Message-ID: <4B6C4CFE.7010409@siemens.com> (raw)
In-Reply-To: <20100205150858.GA32671@infradead.org>
Christoph Hellwig wrote:
> On Thu, Feb 04, 2010 at 03:34:24PM +0100, Pierre Riteau wrote:
>> I think I traced back the issue to the switch from Bochs BIOS to Seabios. By forcing the usage of Bochs BIOS 5f08bb45861f54be478b25075b90d2406a0f8bb3 works, while it dies without the -bios override.
>> Unfortunately, newer versions don't seem to work with Bochs BIOS.
>>
>> Upgrading the host kernel to 2.6.32 (Debian Squeeze) solves the issue. No problem on Fedora 12 as well.
>
> Even Linux 2.6.31 stopped working as a host for me since that commit.
At least kvm-kmod-2.6.31.6 worked fine here, just recently run it with
various versions of qemu-kvm.
Does it bail out at the same address like Pierre? Looking at the code
that fails, ljmp $0xf000,$0xdeb5, it might be affected by the KVM commit
ee3d29e8be (KVM: x86 emulator: fix jmp far decoding (opcode 0xea)) which
predates 2.6.31.1...
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2010-02-05 16:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 14:34 Seabios incompatible with Linux 2.6.26 host? Pierre Riteau
2010-02-05 14:27 ` Pierre Riteau
2010-02-05 14:46 ` Jan Kiszka
2010-02-05 15:05 ` Pierre Riteau
2010-02-05 15:07 ` Jan Kiszka
2010-02-08 11:05 ` Pierre Riteau
2010-02-08 11:13 ` Jan Kiszka
2010-02-08 12:21 ` Avi Kivity
2010-02-09 22:49 ` Pierre Riteau
2010-02-05 15:08 ` Christoph Hellwig
2010-02-05 16:53 ` Jan Kiszka [this message]
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=4B6C4CFE.7010409@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Pierre.Riteau@irisa.fr \
--cc=hch@infradead.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