Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NAp0O-000497-1v for qemu-devel@nongnu.org; Wed, 18 Nov 2009 13:11:48 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NAp0J-00045j-8h for qemu-devel@nongnu.org; Wed, 18 Nov 2009 13:11:47 -0500 Received: from [199.232.76.173] (port=55471 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NAp0I-00045T-VI for qemu-devel@nongnu.org; Wed, 18 Nov 2009 13:11:43 -0500 Received: from thunk.org ([69.25.196.29]:33685 helo=thunker.thunk.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NAp0I-0005f1-9l for qemu-devel@nongnu.org; Wed, 18 Nov 2009 13:11:42 -0500 From: "Theodore Ts'o" Message-Id: Date: Wed, 18 Nov 2009 13:11:32 -0500 Subject: [Qemu-devel] Need a way disable gPXE boot List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org, kvm-devel@lists.sourceforge.net 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? Thanks, - Ted