From: "Daniel P. Berrange" <berrange@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: "Alain Ribière" <alain_ribiere@yahoo.com>,
"Kevin O'Connor" <kevin@koconnor.net>,
"seabios@seabios.org" <seabios@seabios.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re : Regression: more 0.12 regression (SeaBIOS related?)
Date: Thu, 8 Mar 2012 14:37:47 +0000 [thread overview]
Message-ID: <20120308143747.GI25529@redhat.com> (raw)
In-Reply-To: <20120308112825.0daaec5c@doriath.home>
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.
> Using latest seabios makes it go away, didn't try re-building 1.6.3.1 though.
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2012-03-08 14:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 17:00 [Qemu-devel] Regression: more 0.12 regression (SeaBIOS related?) Alain Ribière
2012-03-07 13:38 ` Kevin O'Connor
2012-03-07 14:31 ` [Qemu-devel] Re : " Alain Ribière
2012-03-08 13:56 ` Luiz Capitulino
2012-03-08 14:01 ` Kevin O'Connor
2012-03-08 14:09 ` Daniel P. Berrange
2012-03-08 14:28 ` Luiz Capitulino
2012-03-08 14:36 ` [Qemu-devel] [SeaBIOS] " Peter Stuge
2012-03-08 14:37 ` Daniel P. Berrange [this message]
2012-03-08 14:45 ` [Qemu-devel] " Luiz Capitulino
2012-03-08 17:04 ` [Qemu-devel] Re : " Alain Ribière
2012-03-12 0:52 ` [Qemu-devel] " Kevin O'Connor
2012-03-12 10:38 ` [Qemu-devel] Re : " Alain Ribière
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=20120308143747.GI25529@redhat.com \
--to=berrange@redhat.com \
--cc=alain_ribiere@yahoo.com \
--cc=kevin@koconnor.net \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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).