From: "Jim C. Brown" <jbrown106@phreaker.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] NETDEV WATCHDOG: eth0: transmit timed out
Date: Wed, 5 Jan 2005 10:43:52 -0500 [thread overview]
Message-ID: <20050105154352.GA11125@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <1104899444.20758.26.camel@localhost.localdomain>
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.
next prev parent reply other threads:[~2005-01-05 15:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-05 4:30 [Qemu-devel] NETDEV WATCHDOG: eth0: transmit timed out Horst Schlonz
2005-01-05 15:43 ` Jim C. Brown [this message]
2005-01-05 15:50 ` Jim C. Brown
2005-01-05 18:12 ` Horst Schlonz
2005-01-05 18:25 ` Magnus Damm
2005-01-06 21:57 ` Jim C. Brown
2005-01-06 22:47 ` Magnus Damm
2005-01-05 19:50 ` Jim C. Brown
2005-01-05 20:06 ` Horst Schlonz
2005-01-05 21:33 ` Jim C. Brown
2005-01-06 0:27 ` Horst Schlonz
2005-01-06 0:58 ` Magnus Damm
2005-01-06 1:34 ` Horst Schlonz
2005-01-06 1:53 ` Jim C. Brown
2005-01-06 3:09 ` Horst Schlonz
2005-01-08 10:14 ` [Qemu-devel] " Anand Kumria
2005-01-06 2:41 ` [Qemu-devel] " Herbert Poetzl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050105154352.GA11125@jbrown.mylinuxbox.org \
--to=jbrown106@phreaker.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).