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:51:03 -0500 [thread overview]
Message-ID: <4AEB51B7.2030708@us.ibm.com> (raw)
In-Reply-To: <4AEB4D52.6000906@web.de>
Jan Kiszka wrote:
> It's tunable: Customize -> Console Options -> BANNER_TIMEOUT
>
Ah, I missed that.
>> 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.
>>
>
> Yeah, you see this or even much longer netboot related timeouts these
> days everywhere. Specifically when every damn NIC adds its own delay to
> the boot, you quickly wait half a minute or more on this stage. Granted,
> it's by far not that bad with qemu and gpxe, but this delay is a
> regression from the nice speed we just gained a few months ago.
>
> OK, compromise until we have a proper FW interface: BANNER_TIMEOUT=3.
> That leaves us with a fair chance to break in but keeps the delay
> regression low
>
I'm okay with BANNER_TIMEOUT=0 until we get a proper FW interface.
--
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-10-30 20:51 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
2009-10-30 20:32 ` Jan Kiszka
2009-10-30 20:51 ` Anthony Liguori [this message]
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=4AEB51B7.2030708@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.