From: Horst Schlonz <horst.schlonz@gmx.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] NETDEV WATCHDOG: eth0: transmit timed out
Date: Wed, 05 Jan 2005 21:06:31 +0100 [thread overview]
Message-ID: <1104955592.29588.15.camel@localhost.localdomain> (raw)
In-Reply-To: <20050105195042.GA13437@jbrown.mylinuxbox.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
next prev parent reply other threads:[~2005-01-05 20:25 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
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 [this message]
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=1104955592.29588.15.camel@localhost.localdomain \
--to=horst.schlonz@gmx.de \
--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).