From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HplFd-0007WQ-UZ for qemu-devel@nongnu.org; Sun, 20 May 2007 09:15:09 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HplFc-0007U4-EO for qemu-devel@nongnu.org; Sun, 20 May 2007 09:15:09 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HplFc-0007Tv-9U for qemu-devel@nongnu.org; Sun, 20 May 2007 09:15:08 -0400 Received: from squawk.glines.org ([72.36.206.66]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HplFb-0001ih-Vf for qemu-devel@nongnu.org; Sun, 20 May 2007 09:15:08 -0400 Date: Sun, 20 May 2007 06:15:02 -0700 From: Mark Glines Subject: Re: [Qemu-devel] emulated lance device crashes in debian-sparc32 Message-ID: <20070520061502.2e76772f@chirp> In-Reply-To: <200705201125.26929.paul@codesourcery.com> References: <20070519071656.74105a87@chirp> <20070520021123.7b01da02@chirp> <200705201125.26929.paul@codesourcery.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paul Brook Cc: Blue Swirl , qemu-devel@nongnu.org On Sun, 20 May 2007 11:25:25 +0100 Paul Brook wrote: > > In my past experience, -net user implies -net nic.=20 >=20 > You are mistaken. -net user does not imply -net nic. I just tested this. You are absolutely right, I was wrong about the behavior on x86. > > Hmm. =C2=A0-net performs 2 separate functions. =C2=A0First, it sets up = the > > network card in the guest machine (nic, model, and macaddr). > > Second, it specifies how that card behaves on the host side of > > things (vlan, user, tap, or socket). >=20 > -net creates devices and attaches them to the virtual network, > whether they be emulated devices on the host, or devices for > communication with the "real" world. Thanks for explaining. So the issue on sparc was that the device is relied on by the SS-5 platform code (it sounds like sun4m has this device on-board at a fixed offset, non-pci), but not initialized properly due to the lack of -net nic? Should sun4m imply -net nic,model=3Dlance then? It doesn't make much sense to me to ever turn the lance port off, if its integrated into the platform itself (not a daughter card). I apologize for the additional confusion; I guess I was confused by the fact that "-net nic -net user" is the default when no -net options are provided, and passing "-net user" on the cmdline disabled the implicit -net nic. Mark