From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EQYRZ-0000J0-RI for qemu-devel@nongnu.org; Fri, 14 Oct 2005 18:54:29 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EQYRX-0000H5-SA for qemu-devel@nongnu.org; Fri, 14 Oct 2005 18:54:29 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EQYRX-0000Gq-JI for qemu-devel@nongnu.org; Fri, 14 Oct 2005 18:54:27 -0400 Received: from [128.8.10.163] (helo=po1.wam.umd.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EQYRX-0005a9-SR for qemu-devel@nongnu.org; Fri, 14 Oct 2005 18:54:27 -0400 Received: from jbrown.mylinuxbox.org (jma-box.student.umd.edu [129.2.253.219]) by po1.wam.umd.edu (8.12.10/8.12.10) with ESMTP id j9EMsOW5024428 for ; Fri, 14 Oct 2005 18:54:25 -0400 (EDT) Date: Fri, 14 Oct 2005 18:54:19 -0400 From: "Jim C. Brown" Subject: Re: [Qemu-devel] Setting up tun/tap network doesn't work Message-ID: <20051014225418.GA28497@jbrown.mylinuxbox.org> References: <43501FB5.5020303@mid.email-server.info> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43501FB5.5020303@mid.email-server.info> 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 Fri, Oct 14, 2005 at 11:14:29PM +0200, Alexander Skwar wrote: > Hello. > > I'm trying to get qemu 0.7.2 on Gentoo Linux to work with tun/tap > network - but fail to do so :/ > > Thus, network isn't setup properly inside the qemu "guest". > > Rather obviously, I seem to be missing something. But what > is it? Also, the documentation isn't that clear, as far as > the network part is concerned... Also, I'm sorry to bother > you on the devel list, but the "plain users" forum is down :( > > Thanks a lot for any help you can provide, > > Alexander Skwar > Make sure the guest supports the ne2k-pci driver (either compiled in or loaded as a module). from the output you provided, it appears that your guest kernel lacks the right ethernet driver. Check the output of dmesg to see if ne2k is mentioned. -- Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection.