From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1C1Dim-0001cs-AZ for qemu-devel@nongnu.org; Sat, 28 Aug 2004 20:39:00 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1C1Dik-0001aB-AS for qemu-devel@nongnu.org; Sat, 28 Aug 2004 20:38:59 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1C1Dik-0001a1-5G for qemu-devel@nongnu.org; Sat, 28 Aug 2004 20:38:58 -0400 Received: from [38.113.3.61] (helo=smtp-out.hotpop.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1C1Ddg-0002ZE-19 for qemu-devel@nongnu.org; Sat, 28 Aug 2004 20:33:44 -0400 Received: from phreaker.net (kubrick.hotpop.com [38.113.3.103]) by smtp-out.hotpop.com (Postfix) with SMTP id 40CDF7DE102 for ; Sun, 29 Aug 2004 00:33:40 +0000 (UTC) Received: from jbrown.mylinuxbox.org (pcp03144805pcs.midval01.tn.comcast.net [68.59.228.236]) by smtp-3.hotpop.com (Postfix) with ESMTP id 8E2CC109E3F9 for ; Sun, 29 Aug 2004 00:33:37 +0000 (UTC) Date: Sat, 28 Aug 2004 20:33:35 -0400 From: "Jim C. Brown" Subject: Re: [Qemu-devel] eth0 problems Message-ID: <20040829003335.GA15499@jbrown.mylinuxbox.org> References: <4130FF10.4040502@neenet.com> <200408281813.50144.menola@sbcglobal.net> <41310F8E.5070001@neenet.com> <200408281918.38859.menola@sbcglobal.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200408281918.38859.menola@sbcglobal.net> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Sat, Aug 28, 2004 at 07:18:38PM -0500, Joe Menola wrote: > On Sat August 28 2004 6:04 pm, Lonnie Cumberland wrote: > > No, the /etc/qemu-ifup does not exist and my host eth0 is there but the > > guest linux.img eth0 does not show. Only the "lo" loopback. > > -user-net doesn't provide eth0 in your qemu host. It provides internet access > only. To get full networking (eth0) you need to setup a tun device. > > -jm > > Technically, tun doesn't provide eth0 for the host either. In fact, the kernel documentation says you need to have eth0 first, or else you cant use tuntap (that may no longer be true though, remember this is from the offical kernel docs :). tuntap provides a tun0/tap0 device in the host and an eth0 device in the guest. user net should provide an eth0 as well, but it won't add anything to the host. If eth0 doesn't show, that may be due to lack of hardware support. Be sure your kernel has support for the ne2k-pci module. user net isn't just for internet access .. the guest can still access the LAN or the WAN/intranet .. they just can't initiate a talk to it. > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel > -- Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection.