From: Michael Tokarev <mjt@tls.msk.ru>
To: KVM list <kvm@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: pc-bios/bios.bin - where it comes from?
Date: Fri, 05 Mar 2010 01:46:49 +0300 [thread overview]
Message-ID: <4B903859.7070808@msgid.tls.msk.ru> (raw)
Hello.
There are a few bugs filed about an.. interesting
behavour. For example:
http://www.mail-archive.com/kvm@vger.kernel.org/msg29834.html
https://bugs.launchpad.net/qemu/+bug/513273
After quite some mix-n-matching, at least on my test machine,
I can say that the issue gets triggered by seabios. When
using pc-bios/bios.bin everything is ok. But when using
any other bios.bin, even downloading seabios-0.5.1.tar.gz
and building it - on a debian lenny system anyway - by
running `make', the problem triggers.
I tried different versions/variations of vgabios.bin
(it's only -vga std which triggers the issue so far),
including 0.6b and 0.6c built from sources, vgabios.bin
from debian packages (0.6b and 0.6c), and the one
included in qemu-0.12.3.tar.gz. And my conclusion
so far is that vgabios.bin has exactly _no_ effect on
the issue.
But when using bios.bin from qemu-kvm-0.12.3.tar.gz,
and _only_ that bios.bin, the problem goes away.
So the question arises: where that pc-bios/bios.bin
comes from into qemu-0.12.3.tar.gz? It is either
built from some other sources (not from seabios-0.5.1),
or built with some extra/different compiler/linker options,
or built using different compiler/linker.
This is partially confirmed on ubuntu as well, but,
as far as I understand, there the behavour is different
with different versions of vgabios.
In case it's not clear: I'm testing qemu-kvm-0.12.3;
bios.bin is the same in qemu-0.12.3 and qemu-kvm-0.12.3.
BTW, is there any reason preventing updating vgabios
to 0.6c version - the latest released one?
Thanks!
/mjt
WARNING: multiple messages have this Message-ID (diff)
From: Michael Tokarev <mjt@tls.msk.ru>
To: KVM list <kvm@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] pc-bios/bios.bin - where it comes from?
Date: Fri, 05 Mar 2010 01:46:49 +0300 [thread overview]
Message-ID: <4B903859.7070808@msgid.tls.msk.ru> (raw)
Hello.
There are a few bugs filed about an.. interesting
behavour. For example:
http://www.mail-archive.com/kvm@vger.kernel.org/msg29834.html
https://bugs.launchpad.net/qemu/+bug/513273
After quite some mix-n-matching, at least on my test machine,
I can say that the issue gets triggered by seabios. When
using pc-bios/bios.bin everything is ok. But when using
any other bios.bin, even downloading seabios-0.5.1.tar.gz
and building it - on a debian lenny system anyway - by
running `make', the problem triggers.
I tried different versions/variations of vgabios.bin
(it's only -vga std which triggers the issue so far),
including 0.6b and 0.6c built from sources, vgabios.bin
from debian packages (0.6b and 0.6c), and the one
included in qemu-0.12.3.tar.gz. And my conclusion
so far is that vgabios.bin has exactly _no_ effect on
the issue.
But when using bios.bin from qemu-kvm-0.12.3.tar.gz,
and _only_ that bios.bin, the problem goes away.
So the question arises: where that pc-bios/bios.bin
comes from into qemu-0.12.3.tar.gz? It is either
built from some other sources (not from seabios-0.5.1),
or built with some extra/different compiler/linker options,
or built using different compiler/linker.
This is partially confirmed on ubuntu as well, but,
as far as I understand, there the behavour is different
with different versions of vgabios.
In case it's not clear: I'm testing qemu-kvm-0.12.3;
bios.bin is the same in qemu-0.12.3 and qemu-kvm-0.12.3.
BTW, is there any reason preventing updating vgabios
to 0.6c version - the latest released one?
Thanks!
/mjt
next reply other threads:[~2010-03-04 22:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 22:46 Michael Tokarev [this message]
2010-03-04 22:46 ` [Qemu-devel] pc-bios/bios.bin - where it comes from? Michael Tokarev
2010-03-05 3:50 ` Anthony Liguori
2010-03-05 3:50 ` [Qemu-devel] " Anthony Liguori
2010-03-05 9:17 ` Michael Tokarev
2010-03-05 9:17 ` [Qemu-devel] " Michael Tokarev
2010-03-05 13:56 ` Anthony Liguori
2010-03-05 13:56 ` [Qemu-devel] " Anthony Liguori
2010-03-05 14:55 ` Michael Tokarev
2010-03-05 14:55 ` [Qemu-devel] " Michael Tokarev
2010-03-05 12:40 ` Gerd Hoffmann
2010-03-05 12:40 ` [Qemu-devel] " Gerd Hoffmann
2010-03-05 13:39 ` Aurelien Jarno
2010-03-05 13:51 ` Anthony Liguori
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=4B903859.7070808@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.