qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] iPXE/Etherboot prompts twice for booting?
Date: Tue, 19 Apr 2011 10:16:53 +0100	[thread overview]
Message-ID: <BANLkTi=QnYuebk-14WVL_dp=4V_tro5O+g@mail.gmail.com> (raw)
In-Reply-To: <1303143021.3110.37.camel@x201>

On Mon, Apr 18, 2011 at 5:10 PM, Alex Williamson
<alex.williamson@redhat.com> wrote:
> On Mon, 2011-04-18 at 10:45 +0100, Stefan Hajnoczi wrote:
>> On Sat, Apr 16, 2011 at 8:41 PM, Michael Tokarev <mjt@tls.msk.ru> wrote:
>> > I'm playing with iPXE ROM images again, and see
>> > iPXE prompts two times during bootup.  Once like
>> > this: "Press Ctrl-B to configure", at early stage,
>> > even if -boot n is not selected.  And second time
>> > when it actually tries to boot, like "Press Ctrl-B
>> > for the command line".
>> >
>> > The same behavor happens with old Etherboot, with
>> > the exception that during init stage it tries to
>> > boot too but fails.
>> >
>> > Any idea how to get rid of that?
>>
>> IIRC you need to #define BANNER_TIMEOUT 0 in src/config/general.h.
>
> I think src/local/config/general.h is the preferred location, which is
> what the script in my tree does and includes pre-built ipxe images:

Yeah, using the top-level config is just my bad habit.  The point of
local/ is to prevent conflicts if you update the code and to make git
ignore your local changes.

Stefan

      reply	other threads:[~2011-04-19  9:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-16 19:41 [Qemu-devel] iPXE/Etherboot prompts twice for booting? Michael Tokarev
2011-04-18  9:45 ` Stefan Hajnoczi
2011-04-18 16:10   ` Alex Williamson
2011-04-19  9:16     ` Stefan Hajnoczi [this message]

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='BANLkTi=QnYuebk-14WVL_dp=4V_tro5O+g@mail.gmail.com' \
    --to=stefanha@gmail.com \
    --cc=alex.williamson@redhat.com \
    --cc=mjt@tls.msk.ru \
    --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).