qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rjones@redhat.com>
To: Sebastian Herbszt <herbszt@gmx.de>
Cc: kvm-devel@lists.sourceforge.net, Theodore Ts'o <tytso@mit.edu>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Need a way disable gPXE boot
Date: Tue, 9 Mar 2010 14:11:20 +0000	[thread overview]
Message-ID: <20100309141120.GA21444@amd.home.annexia.org> (raw)
In-Reply-To: <B9BCEF33F9314A329E29C81475B41A63@FSCPC>

On Wed, Nov 18, 2009 at 09:19:53PM +0100, Sebastian Herbszt wrote:
> Theodore Ts'o wrote:
>
> [snip]
>
>> I was ultimately able to work around the solution by deleting the
>> /usr/local/share/qemu/pxe-*.bin files, but that's a bit of a botch.  It
>> would be nice if there was a way to disable the gPXE boot option roms;
>> if you know you are booting off of a passed in hard drive image or
>> passed in a kernel for a direct boot, there's no reason why we might
>> want to do a gPXE boot.
>>
>> It would be nice if there was a way to disable option roms automatically
>> if -kernel is specified, or if -boot order doesn't include 'n', or
>> perhaps with an explicit option to suppress all boot option roms (or all
>> networking options).
>>
>> What sort of approach would be considered acceptable?  Did I miss
>> some way of making the right thing happen other than deleting the
>> installed pxe-*.bin files?
>
> I would suggest dropping the auto nic option rom loading and extend "-net"
> with a rom option like "-net nic,model=e1000,rom=pxe-e1000.bin".

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.

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.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine.  Supports Linux and Windows.
http://et.redhat.com/~rjones/virt-df/

  reply	other threads:[~2010-03-09 14: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 [this message]
2010-03-10  2:03     ` Kevin O'Connor
2010-03-10  9:51       ` Richard W.M. Jones
2010-03-10  3:35     ` Anthony Liguori
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=20100309141120.GA21444@amd.home.annexia.org \
    --to=rjones@redhat.com \
    --cc=herbszt@gmx.de \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=qemu-devel@nongnu.org \
    --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).