From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:33019) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RikG8-0002Ru-Sy for qemu-devel@nongnu.org; Thu, 05 Jan 2012 05:09:24 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RikG7-0006Lu-Fb for qemu-devel@nongnu.org; Thu, 05 Jan 2012 05:09:20 -0500 Received: from chello084112167138.7.11.vie.surfer.at ([84.112.167.138]:56884 helo=wiesinger.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RikG7-0006Lh-55 for qemu-devel@nongnu.org; Thu, 05 Jan 2012 05:09:19 -0500 Date: Thu, 5 Jan 2012 11:08:10 +0100 (CET) From: Gerhard Wiesinger In-Reply-To: <4F05730A.3000607@redhat.com> Message-ID: References: <4F055827.50202@redhat.com> <4F056613.5020607@redhat.com> <4F05730A.3000607@redhat.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: [Qemu-devel] Boot order problem and disable iPXE/gPXE List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: qemu-devel@nongnu.org On Thu, 5 Jan 2012, Gerd Hoffmann wrote: > On 01/05/12 10:24, Gerhard Wiesinger wrote: >> On Thu, 5 Jan 2012, Gerd Hoffmann wrote: >>> 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. >> >> Old command line (relevant parameters): >> -net nic,model=rtl8139,macaddr=1a:46:0b:ca:bc:7c,vlan=0 > > creates a nic (with rom). > >> -net tap,ifname=tap0,script=no,downscript=no,vlan=0 > > creates a tap device > >> -device rtl8139,romfile= > > creates a nic too (without rom), so you have two rtl8139 devices now ... > > You probably want this: > > -net tap,ifname=tap0,script=no,downscript=no,vlan=0 > -device rtl8139,romfile=,macaddr=1a:46:0b:ca:bc:7c,vlan=0 > > Or when using netdevs instead of vlans: > > -netdev tap,ifname=tap0,script=no,downscript=no,id=net0 > -device rtl8139,romfile=,macaddr=1a:46:0b:ca:bc:7c,netdev=net0 > > Likewise for the second nic, just with vlan=1 (or a different name for > the netdev). Tried: -device rtl8139,macaddr=1a:46:0b:ca:bc:7c,vlan=0,romfile= -net tap,ifname=tap0,script=no,downscript=no,vlan=0 -device pcnet,macaddr=1a:46:0b:ca:bc:7e,vlan=1,romfile= -net tap,ifname=tap1,script=no,downscript=no,vlan=1 qemu-system-x86_64: -device rtl8139,macaddr=1a:46:0b:ca:bc:7c,vlan=0,romfile=: Property 'rtl8139.macaddr' not found So therefore as I suggested in the first email the rom (or romfile) parameter in the "-net nic parameter" Any other ideas? Thnx for help. Ciao, Gerhard -- http://www.wiesinger.com/