From: Michael Tokarev <mjt@tls.msk.ru>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: KVM list <kvm@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Dustin Kirkland <kirkland@canonical.com>
Subject: Re: pc-bios/bios.bin - where it comes from?
Date: Fri, 05 Mar 2010 12:17:52 +0300 [thread overview]
Message-ID: <4B90CC40.1080008@msgid.tls.msk.ru> (raw)
In-Reply-To: <4B907F83.3060007@codemonkey.ws>
Anthony Liguori wrote:
> On 03/04/2010 04:46 PM, Michael Tokarev wrote:
>> 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
>>
[]
> pc-bios/bios.bin gets built from roms/seabios.
>
> We don't ship seabios 0.5.1 in 0.12.3, we ship 0.5.1-stable which is two
> commits ahead of 0.5.1.
[]
> One of the reasons we include a git submodule and the source for the
> bios is so that distributors don't have to deal with building the
> packages independently. Morale of the story is, just use the source we
> ship and don't try to be more clever than that :-)
>
>> 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.
The thing is that roms/seabios directory is _empty_ in
qemu-KVM-0.12.3.tar.gz. So I can't use the sources you
(the qemu-kvm team anyway) ship because there's no shipped
sources, so I have to try to be clever and find a way to
deal with the issue.
But now when you mentioned it and I _finally_ found the
bios source in qemu-0.12.3, maybe I'll be even more
clever and will patch qemu-kvm with bits missing in it
from qemu-0.12.3. Ugly but at least doable.
>> BTW, is there any reason preventing updating vgabios
>> to 0.6c version - the latest released one?
>
> There's no compelling improvement in 0.6c and updating vgabios is not
> something I'm eager to do unless there's a strong justification.
Maybe wider testing in debian and/or ubuntu is a good justification? :)
Thanks!
/mjt
next prev parent reply other threads:[~2010-03-05 9:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 22:46 pc-bios/bios.bin - where it comes from? Michael Tokarev
2010-03-05 3:50 ` Anthony Liguori
2010-03-05 9:17 ` Michael Tokarev [this message]
2010-03-05 13:56 ` Anthony Liguori
2010-03-05 14:55 ` Michael Tokarev
2010-03-05 12:40 ` Gerd Hoffmann
2010-03-05 13:39 ` [Qemu-devel] " 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=4B90CC40.1080008@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=anthony@codemonkey.ws \
--cc=kirkland@canonical.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