From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NnOYd-00065V-Jh for qemu-devel@nongnu.org; Thu, 04 Mar 2010 22:50:35 -0500 Received: from [199.232.76.173] (port=54628 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NnOYd-00064s-1F for qemu-devel@nongnu.org; Thu, 04 Mar 2010 22:50:35 -0500 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1NnOYa-0007Hg-RE for qemu-devel@nongnu.org; Thu, 04 Mar 2010 22:50:34 -0500 Received: from mail-gx0-f209.google.com ([209.85.217.209]:64077) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NnOYa-0007Ha-I1 for qemu-devel@nongnu.org; Thu, 04 Mar 2010 22:50:32 -0500 Received: by gxk1 with SMTP id 1so224267gxk.16 for ; Thu, 04 Mar 2010 19:50:31 -0800 (PST) Message-ID: <4B907F83.3060007@codemonkey.ws> Date: Thu, 04 Mar 2010 21:50:27 -0600 From: Anthony Liguori MIME-Version: 1.0 References: <4B903859.7070808@msgid.tls.msk.ru> In-Reply-To: <4B903859.7070808@msgid.tls.msk.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: pc-bios/bios.bin - where it comes from? List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Michael Tokarev Cc: "qemu-devel@nongnu.org" , KVM list , Dustin Kirkland 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 > > 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. > 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. > 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. > 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. > > 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. Regards, Anthony Liguori > Thanks! > > /mjt > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >