From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NAqbA-0006xh-B0 for qemu-devel@nongnu.org; Wed, 18 Nov 2009 14:53:52 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NAqb5-0006wZ-7s for qemu-devel@nongnu.org; Wed, 18 Nov 2009 14:53:51 -0500 Received: from [199.232.76.173] (port=47271 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NAqb5-0006wV-3A for qemu-devel@nongnu.org; Wed, 18 Nov 2009 14:53:47 -0500 Received: from mail-qy0-f197.google.com ([209.85.221.197]:51926) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NAqb4-0006ll-NH for qemu-devel@nongnu.org; Wed, 18 Nov 2009 14:53:46 -0500 Received: by qyk35 with SMTP id 35so787824qyk.19 for ; Wed, 18 Nov 2009 11:53:45 -0800 (PST) Message-ID: <4B0450C6.2040208@codemonkey.ws> Date: Wed, 18 Nov 2009 13:53:42 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Need a way disable gPXE boot References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Theodore Ts'o Cc: kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org Hi Ted, Theodore Ts'o wrote: > I recently updated to the latest qemu-kvm git tree (commit c04b2ae) and > I ran into the following problem. I want to do a direct Linux boot for > some of my testing work, using the -kernel option. Apparently the the > gPXE boot code corrupts something in memory or other CPU state which > causes the loaded kernel to hang after the gPXE code gives up. I can > suppress this using -net none, but of course then I don't have any > networking access. > > 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? > We just did a flag day and switched our PXE rom and BIOS. We've encountered a few regressions and we're quickly fixing them. Alex Graf has already fixed the problem you describe above properly and I've merged that into upstream qemu. It will take a little bit of time for Avi and/or Marcelo to sync those changes into qemu-kvm. For now, using '-bios pcbios.bin' should be a reasonable work around. Regards, Anthony Liguori