From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] wrong bios.bin file in Ubuntu Linux 7.10 causes blue screen on w2k guest
Date: Fri, 23 Nov 2007 14:48:34 +0100 [thread overview]
Message-ID: <fb249edb0711230548n4cab318alaf9bab295cd8ad9c@mail.gmail.com> (raw)
In-Reply-To: <20071123091353.GJ3975@atlas.linux2go.dk>
On 23/11/2007, Soren Hansen <soren@ubuntu.com> wrote:
> On Thu, Nov 22, 2007 at 01:47:22PM -0500, Markus Schulz wrote:
> > Thank you for your response; I think the file can be found here:
> > http://cvs.savannah.nongnu.org/viewvc/qemu/pc-bios/?root=qemu
>
> > As far as I understand Qemu uses the BIOS from the Bochs project and
> > the diff is applied for Qemu and it becomes the Qemu BIOS.
>
> If that's really the case, I'm curious why it's distributed in its
> binary form rather than being built at runtime.
build-time?
Perhaps because the (cross-)compiler used to build the BIOS is not
present in many distros and would be a quite inconvenient dependency.
This is for the PC bios from bochs. Now if all bioses shipped with
qemu were built you would need some 4 cross-toolchains.
> Fabrice, can you shed
> some light on this?
>
> > I think every Qemu installation should use this Qemu BIOS, the BIOS
> > that is made for this project and not the original Bochs BIOS. Are you
> > able to fix this in Ubuntu?
>
> Debian and Ubuntu have fairly strict policies about stuff shipped in
> binary form in source packages, so unless qemu is changed to build this
> bios at build time, that's not going to happen.
Note that this code doesn't run in this form on the host Debian/Ubuntu
is on. It can well be treated as data, not code, like jpeg's shipped
in binary with a program. The data is only interpreted by this
program, but in case of an emulator the interpretation gives an
ilusion of "executing".
> I'm also not familiar with the changes in the bios.diff. Are they
> specific to qemu or could the theoretically be applied to upstream bochs
> without any ill side effects?
There are only two tiny changes, one is generic, one is qemu specific.
>
> > BTW the Ubuntu has the same problem like Windows, if I try to start a
> > image of Ubuntu with the wrong BIOS it crashes too.
>
> What do you mean exactly by "image"? Disk image + snapshot?
>
> --
> Soren Hansen
> Ubuntu Server Team
> http://www.ubuntu.com/
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFHRpnRonjfXui9pOMRAntUAJ9PF49Su0NPfBf+p6Y/NGp0q6ALRQCeIAkG
> HDcLSbfP0W0tZdOJB0jzFJQ=
> =hbXr
> -----END PGP SIGNATURE-----
>
>
next prev parent reply other threads:[~2007-11-23 13:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 18:47 [Qemu-devel] wrong bios.bin file in Ubuntu Linux 7.10 causes blue screen on w2k guest Markus Schulz
2007-11-23 9:13 ` Soren Hansen
2007-11-23 13:48 ` andrzej zaborowski [this message]
2007-11-23 15:20 ` Soren Hansen
2007-11-26 8:43 ` Soren Hansen
2007-11-23 15:10 ` Thiemo Seufer
-- strict thread matches above, loose matches on Subject: below --
2007-11-22 7:08 Markus Schulz
2007-11-22 9:18 ` Soren Hansen
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=fb249edb0711230548n4cab318alaf9bab295cd8ad9c@mail.gmail.com \
--to=balrogg@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).