From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Np0XE-000728-K6 for qemu-devel@nongnu.org; Tue, 09 Mar 2010 09:35:48 -0500 Received: from [199.232.76.173] (port=44126 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Np0Wv-0006mN-RT for qemu-devel@nongnu.org; Tue, 09 Mar 2010 09:35:29 -0500 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1Np0IO-0006FX-Bz for qemu-devel@nongnu.org; Tue, 09 Mar 2010 09:20:29 -0500 Received: from mx20.gnu.org ([199.232.41.8]:6952) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Np0IN-00066O-3a for qemu-devel@nongnu.org; Tue, 09 Mar 2010 09:20:27 -0500 Received: from mx1.redhat.com ([209.132.183.28]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Np0AX-0002Hk-S9 for qemu-devel@nongnu.org; Tue, 09 Mar 2010 09:12:22 -0500 Date: Tue, 9 Mar 2010 14:11:20 +0000 From: "Richard W.M. Jones" Subject: Re: [Qemu-devel] Re: Need a way disable gPXE boot Message-ID: <20100309141120.GA21444@amd.home.annexia.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Sebastian Herbszt Cc: kvm-devel@lists.sourceforge.net, Theodore Ts'o , qemu-devel@nongnu.org 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/