From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Jacques Landru <landru@telecom-lille1.eu>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: qemu-kvm-0.12.2 hangs when booting grub, when kvm is disabled
Date: Thu, 18 Feb 2010 14:19:22 +0100 [thread overview]
Message-ID: <4B7D3E5A.1040902@siemens.com> (raw)
In-Reply-To: <20100218115915.GL14767@redhat.com>
Gleb Natapov wrote:
> On Thu, Feb 18, 2010 at 12:32:39PM +0100, Jan Kiszka wrote:
>> Jacques Landru wrote:
>>> Hi,
>>>
>>> Same problem here
>>>
>>> qemu-kvm-0.12.x hangs if I have at the same time "-no-kvm" and
>>> "file=essai-slitaz.raw,if=ide,index=0,boot=on" sometime with the
>>> message below
>>>
>>> but
>>>
>>> qemu-kvm with "-no-kvm" and without "boot=on" option for the file
>>> parameter, works
>>> qemu-kvm with "boot=on" option and kvm enable works. (kvm-kmod is 2.6.32.7)
>> I have to confirm this issue: Something badly crashes here as well,
>> either grub or the extboot ROM or Seabios.
>>
>> Does anyone has a good idea what makes the difference here, ie. where to
>> start debugging?
>>
> May be TCG interprets something incorrectly in extboot.bin. Sounds
> unlikely, but symptoms look like this is the case.
Looks like the old story again: extboot tries to write to ROM (old_int13
and old_int19 variables). That happens to work due to KVM limitations,
but breaks once true protection is established. Don't we have some heap
managed by Seabios that extension ROMs can use?
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2010-02-18 13:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 8:37 qemu-kvm-0.12.2 hangs when booting grub, when kvm is disabled Jacques Landru
2010-02-18 11:32 ` Jan Kiszka
2010-02-18 11:59 ` Gleb Natapov
2010-02-18 12:01 ` Jan Kiszka
2010-02-18 13:19 ` Jan Kiszka [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-22 0:26 Jim Paris
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=4B7D3E5A.1040902@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=landru@telecom-lille1.eu \
/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