From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CmHiu-0005fv-W5 for qemu-devel@nongnu.org; Wed, 05 Jan 2005 15:25:41 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CmHit-0005fN-VE for qemu-devel@nongnu.org; Wed, 05 Jan 2005 15:25:40 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CmHit-0005fK-Rt for qemu-devel@nongnu.org; Wed, 05 Jan 2005 15:25:39 -0500 Received: from [213.165.64.20] (helo=mail.gmx.net) by monty-python.gnu.org with smtp (Exim 4.34) id 1CmHPs-0005pw-Mk for qemu-devel@nongnu.org; Wed, 05 Jan 2005 15:06:00 -0500 Subject: Re: [Qemu-devel] NETDEV WATCHDOG: eth0: transmit timed out From: Horst Schlonz In-Reply-To: <20050105195042.GA13437@jbrown.mylinuxbox.org> References: <1104899444.20758.26.camel@localhost.localdomain> <20050105154352.GA11125@jbrown.mylinuxbox.org> <1104948769.29588.11.camel@localhost.localdomain> <20050105195042.GA13437@jbrown.mylinuxbox.org> Content-Type: text/plain Date: Wed, 05 Jan 2005 21:06:31 +0100 Message-Id: <1104955592.29588.15.camel@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit 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 Am Mittwoch, den 05.01.2005, 14:50 -0500 schrieb Jim C. Brown: > On Wed, Jan 05, 2005 at 07:12:49PM +0100, Horst Schlonz wrote: > > Am Mittwoch, den 05.01.2005, 10:43 -0500 schrieb Jim C. Brown: > > > On Wed, Jan 05, 2005 at 05:30:44AM +0100, Horst Schlonz wrote: > > > > the problem is: > > > > root@guest # ping -c1 172.20.0.1 > > > > PING 172.20.0.1 (172.20.0.1) 56(84) bytes of data > > > > NETDEV WATCHDOG: eth0: transmit timed out > > > > NETDEV WATCHDOG: eth0: transmit timed out > > > > >From 172.20.0.2 icmp_seq=1 Destination Host Unreachable > > > > > > > > --- 172.20.0.1 ping statistics --- > > > > 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms > > > > root@guest # > > > > > > > > can anyone confirm this? is something wrong with the emulated > > > > realtek-network-device? > > > > > > > > > > Looks like you may need to set up iptables. E.g. make sure the kernel firewall > > > isn't blocking it. > > > > > > Also possible that you are using the wrong driver in the guest OS, so it doesn't > > > see the ethernet card. > > > > > > > so, this is supposed to work, right? does it work for you? or am i > > missing something here? i have tried various drivers (kernels, indeed). > > suse 9.2, latest knoppix... same problem there. > > Show us what is in your /etc/qemu-ifup script. > user@host # cat /etc/qemu-ifup #!/bin/sh sudo -p "Password for $0:" /sbin/ifconfig $1 172.20.0.1 user@host # > > > > maybe it's the tun-driver of my host kernel. i have ubuntu hoary with > > stock kernel 2.6.9-1-686 here. firewall tables are all clean on host and > > guest, i have checked this already with iptables -L. > > That isn't good enough, you need to add several rules to get it to work. > i just followed the documentation: quote 3.7.1 Using tun/tap network interface This is the standard way to emulate network. QEMU adds a virtual network device on your host (called tun0), and you can then configure it as if it was a real ethernet card. As an example, you can download the `linux-test-xxx.tar.gz' archive and copy the script `qemu-ifup' in `/etc' and configure properly sudo so that the command ifconfig contained in `qemu-ifup' can be executed as root. You must verify that your host kernel supports the TUN/TAP network interfaces: the device `/dev/net/tun' must be present. /quote