From: Rusty Russell <rusty@rustcorp.com.au>
To: Or Gerlitz <ogerlitz@voltaire.com>
Cc: Avi Kivity <avi@redhat.com>,
netdev@vger.kernel.org, Gregory Haskins <ghaskins@novell.com>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: user space virtio-net exits with "truncating packet" error
Date: Thu, 14 May 2009 21:28:57 +0930 [thread overview]
Message-ID: <200905142128.58111.rusty@rustcorp.com.au> (raw)
In-Reply-To: <Pine.LNX.4.64.0905141258570.31748@zuben.voltaire.com>
On Thu, 14 May 2009 07:37:42 pm Or Gerlitz wrote:
> Hi,
>
> When running with jumbo frames (i.e set tap0 and guest nic mtu to 9k)
> and using 8k sized packets with iperf, the qemu process exits with
> "virtio-net truncating packet" which I see in the code of
> qemu/hw/virtio-net.c
>
> :: virtio_net_receive(). This happens only when the VM is receiving, if I
>
> send 8K packets from the VM things go fine.
>
> I use virtio based NIC in the VM and Linux 2.6.29.1 in both the VM and the
> host. Qemu is the one provided by kvm release 84 - whose sources don't
> point me to a specific git tree nor a maintainer, so I hope you can help
> me...
Maintainer Cc'd. The answer is that virtio_net by default only supports 1500
MTU; I've not tried larger MTUs.
Rusty.
next prev parent reply other threads:[~2009-05-14 11:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 10:07 user space virtio-net exits with "truncating packet" error Or Gerlitz
2009-05-14 11:22 ` Mark McLoughlin
2009-05-14 11:22 ` [Qemu-devel] " Mark McLoughlin
2009-05-14 12:25 ` Or Gerlitz
2009-05-14 12:25 ` [Qemu-devel] " Or Gerlitz
2009-05-14 11:58 ` Rusty Russell [this message]
2009-05-14 14:04 ` Or Gerlitz
2009-05-14 18:04 ` Or Gerlitz
2009-05-15 5:18 ` Rusty Russell
2009-05-19 12:19 ` Or Gerlitz
2009-05-20 2:47 ` Rusty Russell
2009-05-20 6:20 ` Or Gerlitz
2009-05-20 6:59 ` Avi Kivity
2009-05-21 5:53 ` Rusty Russell
2009-05-15 7:07 ` Michael Tokarev
2009-05-19 10:00 ` Or Gerlitz
2009-05-19 10:13 ` Avi Kivity
2009-05-14 15:34 ` Sridhar Samudrala
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=200905142128.58111.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=ghaskins@novell.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@voltaire.com \
/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.