From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NLmAr-0000kR-Bb for qemu-devel@nongnu.org; Fri, 18 Dec 2009 18:23:53 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NLmAm-0000cR-KA for qemu-devel@nongnu.org; Fri, 18 Dec 2009 18:23:52 -0500 Received: from [199.232.76.173] (port=44950 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NLmAm-0000cE-Ao for qemu-devel@nongnu.org; Fri, 18 Dec 2009 18:23:48 -0500 Received: from mail-gx0-f223.google.com ([209.85.217.223]:39684) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NLmAm-0005oP-LG for qemu-devel@nongnu.org; Fri, 18 Dec 2009 18:23:48 -0500 Received: by gxk23 with SMTP id 23so3790940gxk.2 for ; Fri, 18 Dec 2009 15:23:47 -0800 (PST) Message-ID: <4B2C0F00.30209@codemonkey.ws> Date: Fri, 18 Dec 2009 17:23:44 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] ne2k_isa: how to specify a custom iobase and irq? References: <154639B97697400DB13CEC80171644F1@FSCPC> <4B2B3F52.4020407@redhat.com> <90808A6C76FB43D7ACAAF92D940271C5@FSCPC> <4B2BEBF4.6070202@codemonkey.ws> <934349ECE007414393806679A9601B59@FSCPC> In-Reply-To: <934349ECE007414393806679A9601B59@FSCPC> 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: Sebastian Herbszt Cc: qemu-devel@nongnu.org, Gerd Hoffmann , Markus Armbruster Sebastian Herbszt wrote: > Actually you have to else networking doesn't work at all. Without > specifying > "vlan" with the "-device" syntax you end up with vlan= and not > vlan=0 > with "info qtree". -netdev type=tap,id=mynic -device ne2k_isa,irq=5,iobase=0x280,id=mynic One of the changes in 0.12 allows for a network configuration that does not have the builtin hub (aka vlans). This is really important for a number of reasons. The main is that it allows for much more aggressive optimization without having to teach the vlan code how to deal with things like software GSO. That might look awkward, but that's because it's designed to be used from a config file. The config entry for that is: [device "mynic"] driver = "ne2k_isa" irq = "5" iobase = "0x280" [netdev "mynic"] type = "tap" Which looks pretty nice IMHO. Regards, Anthony Liguori