From: Anthony Liguori <aliguori@us.ibm.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: Regression due to "Fall back to network boot..."
Date: Fri, 30 Oct 2009 15:11:55 -0500 [thread overview]
Message-ID: <4AEB488B.4070603@us.ibm.com> (raw)
In-Reply-To: <4AEB45F5.4040204@web.de>
Jan Kiszka wrote:
> Anthony Liguori wrote:
>
>> Jan Kiszka wrote:
>>
>>> OK, thanks. Still one complaint: gPXE comes with an annoying boot delay
>>> even if you can boot from disk or have _explicitly_ specified this. I'm
>>> not familiar with it, but I bet there is some magic config switch to
>>> disable this...
>>>
>>>
>> Nothing seemed obvious to me. If anyone has ideas/patches I'm all for it.
>>
>
> Found it: BANNER_TIMEOUT=0.
>
But it's not a tunable and I was hoping to not have to pull gpxe into
the tree and start adding patches.
Maybe we could wait until 0.13 and then introduce the FW cfg interface
to gpxe? I've already talked to some of the gpxe devs about it and they
seem pretty receptive. That would let us define how long the timeout was.
The advantage of leaving in the timeout is that it lets a user access
the gPXE menu even if it's not set to be bootable. You see this on bare
metal all of the time with gPXE.
> It's just blocking the menu, even starting with -S, injecting ctrl-b via
> the monitor and then continuing doesn't help. Not sure if we loose much
> this way, though.
>
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-10-30 20:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-30 17:16 [Qemu-devel] Regression due to "Fall back to network boot..." Jan Kiszka
2009-10-30 17:43 ` [Qemu-devel] " Anthony Liguori
2009-10-30 19:32 ` Jan Kiszka
2009-10-30 19:42 ` Anthony Liguori
2009-10-30 20:00 ` Jan Kiszka
2009-10-30 20:11 ` Anthony Liguori [this message]
2009-10-30 20:32 ` Jan Kiszka
2009-10-30 20:51 ` Anthony Liguori
2009-10-30 21:20 ` Alexander Graf
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=4AEB488B.4070603@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=jan.kiszka@web.de \
--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).