All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Fabrice Toppi <fabrice.toppi@openweb.be>
Cc: kvm@vger.kernel.org
Subject: Re: Network packet size over MTU in guests
Date: Wed, 07 Oct 2009 15:25:15 +0400	[thread overview]
Message-ID: <4ACC7A9B.4080407@msgid.tls.msk.ru> (raw)
In-Reply-To: <4ACC5364.6010602@openweb.be>

Fabrice Toppi wrote:
> Hi,
> 
> We use KVM 75 on Gentoo hosts with kernel 2.6.27.8 with a variety of 
> guests (Windows XP, 2000, 2003 & several Linux distributions) in a 
> production setup.
> The hosts are Intel Xeon based. We use bridged networking with E1000 
> model inside of guests.
> 
> Recently, we began to have network problem (slowdowns, lags, timeouts) 
> on several guests. Inside those guests, we saw with tcpdump that there 
> were packets with a size well over MTU. On the host, tcpdump on the 
> guest tap did show packets of 1500 bytes and that's all.
> For some of the guests (Debian based), changing the NIC model to rtl8139 
> instead of e1000 "fixed" the problem, but for others (Gentoo kernel 
> 2.6.27.19) it didn't.
> 
> Would it be a glitch in the KVM code or a driver problem ? Does this 
> ring a bell to anyone ?

I'm not sure anymore but I think it's very similar to what I had here with
pre-78 (approx again, since it was quite some time ago) versions of kvm
compiled with older kernel headers (without appropriate if_tun.h definitions).

I'd say try to reproduce it with 0.11.0 kvm userspace compiled against
2.6.27+ kernel headers.  But yet again: kvm-75 is quite old by now, so
it's difficult to remember all the details.

/mjt



      reply	other threads:[~2009-10-07 11:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-07  8:37 Network packet size over MTU in guests Fabrice Toppi
2009-10-07 11:25 ` Michael Tokarev [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=4ACC7A9B.4080407@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=fabrice.toppi@openweb.be \
    --cc=kvm@vger.kernel.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.