qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	seabios <seabios@seabios.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Boot failure with MS-Dos 6.22 (due to bad BIOS build?)
Date: Wed, 29 Feb 2012 09:19:52 +0000	[thread overview]
Message-ID: <20120229091952.GE5050@redhat.com> (raw)
In-Reply-To: <20120229084513.GA17676@morn.localdomain>

On Wed, Feb 29, 2012 at 03:45:13AM -0500, Kevin O'Connor wrote:
> On Mon, Feb 27, 2012 at 04:25:09PM +0100, Jan Kiszka wrote:
> > On 2012-02-27 10:51, Daniel P. Berrange wrote:
> > > I'm seeing current QEMU GIT fail to boot MS-Dos 6.22 with the following
> > > crash:
> > > 
> > > # qemu-system-x86_64 -fda ~/MS-DOS\ 6.22.img  -m 1 -curses
> 
> Does the error persist when run with "-m 2"?  If more memory fixes the
> issue, then it is likely already fixed in upstream (commit 890d9851).
> The bugs fixed in that commit are null pointer derefernce errors - in
> SeaBIOS, a write to "NULL" actually alters the memory at address 0,
> which can corrupt the interrupt table - these can lead to
> unpredictable errors, as the timing between when an irq fires and when
> the corruption occurs can vary.  DOS might overwrite the irq entries
> with its own settings, and thus depending on timing may cover up the
> error.  In short, I wouldn't assume the problem is the toolchain.

The error occurs no matter what '-m XX' setting I give it. I did a git
bisect across a Seabios GIT from master down torel-1.6.3.1 and could
not reproduce it with any BIOS I built myself. Hence the only conclusion
I could come to is that the QEMU binary was broken in some way.

Regards,
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 :|

  reply	other threads:[~2012-02-29  9:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-27  9:51 [Qemu-devel] Boot failure with MS-Dos 6.22 (due to bad BIOS build?) Daniel P. Berrange
2012-02-27 15:25 ` Jan Kiszka
2012-02-27 16:00   ` [Qemu-devel] [SeaBIOS] " Peter Stuge
2012-02-27 16:10     ` Jan Kiszka
2012-02-27 16:20       ` Peter Stuge
2012-02-29  8:45   ` [Qemu-devel] " Kevin O'Connor
2012-02-29  9:19     ` Daniel P. Berrange [this message]
2012-02-29  9:51       ` [Qemu-devel] [SeaBIOS] " Fred .
2012-03-19  0:29   ` [Qemu-devel] " Kevin O'Connor
2012-03-19 20:03     ` Jan Kiszka
2012-03-20  2:17       ` Kevin O'Connor

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=20120229091952.GE5050@redhat.com \
    --to=berrange@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kevin@koconnor.net \
    --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).