From: Gleb Natapov <gleb@redhat.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: Glauber Costa <glommer@redhat.com>,
Naphtali Sprei <nsprei@redhat.com>,
gpxe@etherboot.org, Avi Kivity <avi@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Stack corruption problem with SeaBIOS/gPXE under QEMU
Date: Wed, 18 Nov 2009 11:39:49 +0200 [thread overview]
Message-ID: <20091118093949.GA18543@redhat.com> (raw)
In-Reply-To: <20091117022620.GA25962@morn.localdomain>
On Mon, Nov 16, 2009 at 09:26:20PM -0500, Kevin O'Connor wrote:
> On Mon, Nov 16, 2009 at 04:02:20PM +0200, Avi Kivity wrote:
> >> Something that is likely related, I am seeing reboot failures in
> >> seabios's pmm_free. Immediately after loading gpxe, seabios is in an
> >> endless loop there, likely due to memory corruption.
> >>
> >> This is with -smp 2, rebooting Fedora 9 after installation.
> >
> > With gpxe disabled, rebooting works as expected.
> >
> > Note the tests were performed with the stack at 64K to avoid triggering
> > the known issue.
>
> Hi Avi,
>
> Can you send the full qemu command line that you used? I can't seem
> to reproduce this on my setup.
>
> I do see an issue if SeaBIOS's reboot vector is called (eg, by using
> "sendkey ctrl-alt-delete" while still in the bios) because seabios
> allows gpxe to modify itself, and on a seabios only reboot the gpxe
> rom isn't recopied and gpxe therefore gets confused. However, on a
> linux invoked reboot, it looks like a full machine reset occurs and
> qemu recopies the gpxe rom, so that doesn't seem to be an issue.
>
Do we have the same problem with tpr patching rom (vapic,bin)? It modifies
itself too.
> BTW, how did you change the stack location? I've been changing
> seabios by setting BUILD_STACK_ADDR to 0x7000 (or 0xfff0) in
> src/config.h.
>
> -Kevin
>
--
Gleb.
next prev parent reply other threads:[~2009-11-18 9:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 11:20 [Qemu-devel] Stack corruption problem with SeaBIOS/gPXE under QEMU Naphtali Sprei
2009-11-14 19:47 ` Kevin O'Connor
2009-11-15 9:43 ` Naphtali Sprei
2009-11-16 13:36 ` Avi Kivity
2009-11-16 14:02 ` Avi Kivity
2009-11-17 2:26 ` Kevin O'Connor
2009-11-17 13:23 ` Avi Kivity
2009-11-21 0:47 ` Kevin O'Connor
2009-11-29 10:58 ` Avi Kivity
2009-11-18 9:39 ` Gleb Natapov [this message]
2009-11-18 9:49 ` Alexander Graf
2009-11-18 9:53 ` Gleb Natapov
2009-11-18 12:58 ` Kevin O'Connor
2009-11-18 13:06 ` Kevin O'Connor
2009-11-18 14:22 ` Gleb Natapov
2009-11-18 15:38 ` [gPXE] " Joshua Oreman
2009-11-19 1:07 ` Kevin O'Connor
2009-11-18 13:50 ` Avi Kivity
2009-11-18 14:19 ` Gleb Natapov
2009-11-18 14:21 ` Avi Kivity
2009-11-20 22:39 ` 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=20091118093949.GA18543@redhat.com \
--to=gleb@redhat.com \
--cc=avi@redhat.com \
--cc=glommer@redhat.com \
--cc=gpxe@etherboot.org \
--cc=kevin@koconnor.net \
--cc=nsprei@redhat.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).