qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Horst Schlonz <horst.schlonz@gmx.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] NETDEV WATCHDOG: eth0: transmit timed out
Date: Thu, 06 Jan 2005 01:27:21 +0100	[thread overview]
Message-ID: <1104971241.29588.46.camel@localhost.localdomain> (raw)
In-Reply-To: <20050105213319.GA14108@jbrown.mylinuxbox.org>

Am Mittwoch, den 05.01.2005, 16:33 -0500 schrieb Jim C. Brown:
> On Wed, Jan 05, 2005 at 09:06:31PM +0100, Horst Schlonz wrote:
> > > 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 #
> 
> Yes, you are missing the iptables lines. (Personally I prefer ipchains to
> iptables, but alas ...)
> 
> [script for setting up masquerading snipped]

well, i don't see how masquerading and forwarding will help me in
pinging from guest to host or vice versa. but i did as you say and - as
expected - it does not work. see subject for failure message.

> can you test out that script and see if it works?
> 

actually in the past few days i tried every qemu networking
configuration i could get my hands on. i tried -user-net and vde, i
fiddled with iptables, arp and tcpdump, masquerading, forwarding,
bridging, everything.

after manually filling all arp-caches with correct mac-adresses i can
even see icmp-packet coming out of the guest (with the ususal
WATCHDOG-failure, though). but the icmp-replys never show up in the
guest.

i think, the problem is, that every time network traffic is issued from
or to the guest, it does not work and these failure shows up
in /var/log/messages on the guest:
Jan  5 03:53:14 guest kernel: NETDEV WATCHDOG: eth0: transmit timed out

last hope for me was asking qemu devs on this list, but now i will try
one last thing. ditch the ubuntu-qemu and compile it myself.

  reply	other threads:[~2005-01-06  0:38 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
2005-01-05 21:33         ` Jim C. Brown
2005-01-06  0:27           ` Horst Schlonz [this message]
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=1104971241.29588.46.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).