From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N3y99-0003ez-Ap for qemu-devel@nongnu.org; Fri, 30 Oct 2009 16:32:31 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N3y94-0003dp-DG for qemu-devel@nongnu.org; Fri, 30 Oct 2009 16:32:30 -0400 Received: from [199.232.76.173] (port=43946 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N3y94-0003dk-3H for qemu-devel@nongnu.org; Fri, 30 Oct 2009 16:32:26 -0400 Received: from fmmailgate02.web.de ([217.72.192.227]:33565) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N3y93-0002Od-Es for qemu-devel@nongnu.org; Fri, 30 Oct 2009 16:32:25 -0400 Message-ID: <4AEB4D52.6000906@web.de> Date: Fri, 30 Oct 2009 21:32:18 +0100 From: Jan Kiszka MIME-Version: 1.0 References: <4AEB1F84.4010400@siemens.com> <4AEB25B1.8040709@us.ibm.com> <4AEB3F4F.4060407@web.de> <4AEB41A2.1060401@us.ibm.com> <4AEB45F5.4040204@web.de> <4AEB488B.4070603@us.ibm.com> In-Reply-To: <4AEB488B.4070603@us.ibm.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig19D924A9C1FDA2374C2F1506" Sender: jan.kiszka@web.de Subject: [Qemu-devel] Re: Regression due to "Fall back to network boot..." List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: qemu-devel This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig19D924A9C1FDA2374C2F1506 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Anthony Liguori wrote: > Jan Kiszka wrote: >> Anthony Liguori wrote: >> =20 >>> Jan Kiszka wrote: >>> =20 >>>> OK, thanks. Still one complaint: gPXE comes with an annoying boot de= lay >>>> 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... >>>> =20 >>> Nothing seemed obvious to me. If anyone has ideas/patches I'm all >>> for it. >>> =20 >> >> Found it: BANNER_TIMEOUT=3D0. >> =20 >=20 > But it's not a tunable and I was hoping to not have to pull gpxe into > the tree and start adding patches. It's tunable: Customize -> Console Options -> BANNER_TIMEOUT >=20 > 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 the= y > seem pretty receptive. That would let us define how long the timeout w= as. >=20 > 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 bar= e > 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=3D3. That leaves us with a fair chance to break in but keeps the delay regression low. Jan --------------enig19D924A9C1FDA2374C2F1506 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkrrTVYACgkQitSsb3rl5xRx2QCfY3qKEm9hShV0WAxAkHOoHA6F 4YQAn23ePqg3zbMxasKfKBnklxDAVVLj =9lVT -----END PGP SIGNATURE----- --------------enig19D924A9C1FDA2374C2F1506--