From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:52257) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rij9B-0000CV-Hs for qemu-devel@nongnu.org; Thu, 05 Jan 2012 03:58:10 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Rij95-0002Ll-IQ for qemu-devel@nongnu.org; Thu, 05 Jan 2012 03:58:05 -0500 Received: from mx1.redhat.com ([209.132.183.28]:19500) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rij95-0002Lc-8n for qemu-devel@nongnu.org; Thu, 05 Jan 2012 03:57:59 -0500 Message-ID: <4F056613.5020607@redhat.com> Date: Thu, 05 Jan 2012 09:57:55 +0100 From: Gerd Hoffmann MIME-Version: 1.0 References: <4F055827.50202@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Boot order problem and disable iPXE/gPXE List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerhard Wiesinger Cc: qemu-devel@nongnu.org Hi, >> Better use a empty string as romfile argument, that will make the ROM >> pci bar go away instead of creating one with an invalid rom. > > Thnx. Works well by specifying no romfile, that's the trick. I had the > problem than otherwise devices were created. But I'm still getting the > following iPXE rom message: > iPXE v1.0.0-591-g7aee315 > iPXE (http://ipxe.org) 00:03.0 CA00 PCI2.10 PnP PMM+0FFCA670+0FF8A670 CA00 > > How to disable it, too? It shouldn't be there. I guess you've trapped into automagic device creation logic in qemu. When neither -net nor -netdev is specified on the command line qemu creates a default network setup for you, which includes a nic, and that probably is the rom of the automagically created nic. Try "qemu -netdev user,id=mynet -device rtl8139,romfile=,netdev=mynet", then it should work as expected. HTH, Gerd