qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: kvm-devel@lists.sourceforge.net, Theodore Ts'o <tytso@mit.edu>,
	qemu-devel@nongnu.org, Sebastian Herbszt <herbszt@gmx.de>
Subject: Re: [Qemu-devel] Re: Need a way disable gPXE boot
Date: Tue, 09 Mar 2010 21:35:11 -0600	[thread overview]
Message-ID: <4B97136F.7010807@codemonkey.ws> (raw)
In-Reply-To: <20100309141120.GA21444@amd.home.annexia.org>

On 03/09/2010 08:11 AM, Richard W.M. Jones wrote:
> Did anyone attempt this?
>
> I noticed also with libguestfs that boot times have spiralled out of
> control again, and it seems to be down to the SeaBIOS change.  SeaBIOS
> accounts for _9_ seconds of the boot sequence, up from very small
> (fraction of a second) for the old Bochs BIOS[1].
>
> rm -rf /usr/share/gpxe directory reduces the SeaBIOS share of the boot
> time down to about 5 seconds, but that's still a huge regression
> compared to the old Bochs BIOS.
>    

Sounds like you're using a distro and that the distro has improperly 
built the GPXE binaries.  We don't look for roms in /usr/share/gpxe in 
upstream...

For the ROMs we ship, we set BANNER_TIMEOUT=0.

You should file a bug against your distro and try to reproduce with an 
upstream build.  SeaBIOS takes no time at all with upstream.

Regards,

Anthony Liguori

> I'm sure it's waiting for a keypress or something stupid like that.
> It'd be nice if the BIOS could be configured in a "just boot, dammit"
> mode where it avoids all interaction with keyboards, network cards,
> option ROMs etc.
>
> Rich.
>
> [1] Once I'd put a patch into Bochs BIOS to disable a 3 second
> keypress wait.
>
>    

  parent reply	other threads:[~2010-03-10  3:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-18 18:11 [Qemu-devel] Need a way disable gPXE boot Theodore Ts'o
2009-11-18 19:53 ` Anthony Liguori
2009-11-18 22:37   ` tytso
2009-11-18 20:19 ` [Qemu-devel] " Sebastian Herbszt
2010-03-09 14:11   ` Richard W.M. Jones
2010-03-10  2:03     ` Kevin O'Connor
2010-03-10  9:51       ` Richard W.M. Jones
2010-03-10  3:35     ` Anthony Liguori [this message]
2010-03-10 10:00       ` Richard W.M. Jones

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=4B97136F.7010807@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=herbszt@gmx.de \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=qemu-devel@nongnu.org \
    --cc=rjones@redhat.com \
    --cc=tytso@mit.edu \
    /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).