From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CmDW8-0003Vk-0O for qemu-devel@nongnu.org; Wed, 05 Jan 2005 10:56:12 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CmDW7-0003VF-1B for qemu-devel@nongnu.org; Wed, 05 Jan 2005 10:56:11 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CmDW6-0003V5-TZ for qemu-devel@nongnu.org; Wed, 05 Jan 2005 10:56:10 -0500 Received: from [38.113.3.61] (helo=smtp-out.hotpop.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CmDKo-0006mB-PI for qemu-devel@nongnu.org; Wed, 05 Jan 2005 10:44:30 -0500 Received: from phreaker.net (kubrick.hotpop.com [38.113.3.103]) by smtp-out.hotpop.com (Postfix) with SMTP id 066B2C98DAE for ; Wed, 5 Jan 2005 15:44:27 +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 897C6132A75A for ; Wed, 5 Jan 2005 15:44:23 +0000 (UTC) Date: Wed, 5 Jan 2005 10:43:52 -0500 From: "Jim C. Brown" Subject: Re: [Qemu-devel] NETDEV WATCHDOG: eth0: transmit timed out Message-ID: <20050105154352.GA11125@jbrown.mylinuxbox.org> References: <1104899444.20758.26.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1104899444.20758.26.camel@localhost.localdomain> 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 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. -- Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection.