From: tytso@mit.edu Subject: [tytso@MIT.EDU: Need a way disable gPXE boot] Date: Wed, 18 Nov 2009 14:40:09 -0500 Message-ID: <20091118194009.GB10380@thunk.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="5vNYLRcllDrimb99" To: kvm@vger.kernel.org Return-path: Received: from thunk.org ([69.25.196.29]:57692 "EHLO thunker.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758284AbZKRTkF (ORCPT ); Wed, 18 Nov 2009 14:40:05 -0500 Content-Disposition: inline Sender: kvm-owner@vger.kernel.org List-ID: --5vNYLRcllDrimb99 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline --5vNYLRcllDrimb99 Content-Type: message/rfc822 Content-Disposition: inline Return-Path: Received: from po14.mit.edu ([unix socket]) by po14.mit.edu (Cyrus v2.1.5) with LMTP; Wed, 18 Nov 2009 13:12:00 -0500 X-Sieve: CMU Sieve 2.2 Received: from mit-mailsec-scanner-1.mit.edu by po14.mit.edu (8.13.6/4.7) id nAIIBsMk001952; Wed, 18 Nov 2009 13:11:59 -0500 (EST) Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by (Symantec Brightmail Gateway) with SMTP id 53.A9.13421.0F8340B4; Wed, 18 Nov 2009 13:12:00 -0500 (EST) Received: from dmz-mailsec-scanner-4.mit.edu (DMZ-MAILSEC-SCANNER-4.MIT.EDU [18.9.25.15]) by fort-point-station.mit.edu (8.13.6/8.9.2) with ESMTP id nAIHTWCL013483 for ; Wed, 18 Nov 2009 13:11:53 -0500 (EST) X-AuditID: 12074f0c-b7b4cae00000346d-d6-4b0438f0f533 Received: from thunker.thunk.org (thunk.org [69.25.196.29]) by (Symantec Brightmail Gateway) with SMTP id CA.7F.26952.FD8340B4; Wed, 18 Nov 2009 13:11:43 -0500 (EST) Received: from root (helo=closure.thunk.org) by thunker.thunk.org with local-esmtp (Exim 4.50 #1 (Debian)) id 1NAp0D-0005Fe-O5; Wed, 18 Nov 2009 13:11:37 -0500 Received: from root by closure.thunk.org with local (Exim 4.69) (envelope-from ) id 1NAp08-0004pq-EP; Wed, 18 Nov 2009 13:11:32 -0500 To: qemu-devel@nongnu.org, kvm-devel@lists.sourceforge.net Subject: Need a way disable gPXE boot From: "Theodore Ts'o" Phone: (781) 391-3464 Message-Id: Date: Wed, 18 Nov 2009 13:11:32 -0500 X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: root@thunk.org X-SA-Exim-Scanned: No (on thunker.thunk.org); SAEximRunCond expanded to false X-Brightmail-Tracker: AAAAAA== X-Spam-Score: 1.217 X-Spam-Level: * (1.217) X-Spam-Flag: NO X-Scanned-By: MIMEDefang 2.42 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 --5vNYLRcllDrimb99--