From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Farkas Levente <lfarkas-lWVWdrzSO4GHXe+LvDLADg@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: network problem with kvm-40
Date: Wed, 19 Sep 2007 12:44:14 +0200 [thread overview]
Message-ID: <46F0FD7E.5070006@qumranet.com> (raw)
In-Reply-To: <46F0E9D2.4080904-lWVWdrzSO4GHXe+LvDLADg@public.gmane.org>
Farkas Levente wrote:
> hi,
> with kvm-40 in a x86_64 host bridged mode:
> ---------------------------
> e1000: peth0: e1000_watchdog_task: NIC Link is Up 100 Mbps Full Duplex
> e1000: peth0: e1000_watchdog_task: 10/100 speed: disabling TSO
> ---------------------------
> while on the guests (both x86_64 and i386) are full with such lines:
> ---------------------------
> Sep 19 09:23:40 devel-i386 kernel: eth0: link up, 100Mbps, full-duplex,
> lpa 0x05E1
> Sep 19 09:24:47 devel-i386 kernel: NETDEV WATCHDOG: eth0: transmit timed out
> Sep 19 09:24:50 devel-i386 kernel: eth0: link up, 100Mbps, full-duplex,
> lpa 0x05E1
> Sep 19 09:25:08 devel-i386 kernel: NETDEV WATCHDOG: eth0: transmit timed out
>
kvm-41, out soon, will fix this.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
prev parent reply other threads:[~2007-09-19 10:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 9:20 network problem with kvm-40 Farkas Levente
[not found] ` <46F0E9D2.4080904-lWVWdrzSO4GHXe+LvDLADg@public.gmane.org>
2007-09-19 10:44 ` Avi Kivity [this message]
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=46F0FD7E.5070006@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=lfarkas-lWVWdrzSO4GHXe+LvDLADg@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.