On Thu, 8 Mar 2012 14:37:47 +0000
"Daniel P. Berrange" <berrange@redhat.com> wrote:

> On Thu, Mar 08, 2012 at 11:28:25AM -0300, Luiz Capitulino wrote:
> > On Thu, 8 Mar 2012 14:09:05 +0000
> > "Daniel P. Berrange" <berrange@redhat.com> wrote:
> >
> > > On Thu, Mar 08, 2012 at 09:01:12AM -0500, Kevin O'Connor wrote:
> > > > On Thu, Mar 08, 2012 at 10:56:01AM -0300, Luiz Capitulino wrote:
> > > > > On Wed, 7 Mar 2012 06:31:31 -0800 (PST)
> > > > > Alain Ribière <alain_ribiere@yahoo.com> wrote:
> > > > >
> > > > > > I ran qemu 1.0.1 and the latest SeaBIOS (from the git) with the following options :
> > > > >
> > > > > What's the git HEAD?
> > > > >
> > > > > Coincidentally, I was playing with MS-DOS 6.22 yesterday and hit an issue right
> > > > > during bootup. After debugging a bit, I found out that latest seabios fixes the
> > > > > problem but couldn't identify the actual commit.
> > > > >
> > > > > The git HEAD of my seabios repo is c5c488f46b.
> > > >
> > > > Daniel reported a similar error.  I haven't had a chance to look at it
> > > > yet.
> > >
> > > This was the issue where QEMU's binary build of Seabios was broken.
> > > Rebuilding the exact same Seabios changeset from source works fine.
> >
> > Are you running qemu 1.0 or latest from git?
>
> Using GIT
>
> > qemu 1.0 has seabios from commit 8e301472e324, I don't get the problem with
> > this one. But latest qemu from git has seabios 1.6.3.1, it's with that
> > version that I get my problem.
>
> That's the same I found - simply rebuilding 1.6.3.1 gives a binary that
> works fine.

Yeah, just tried it, worked.

I think we're thinking in updating our seabios version soon?