From: Avi Kivity <avi@redhat.com>
To: Or Gerlitz <ogerlitz@voltaire.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
Rusty Russell <rusty@rustcorp.com.au>,
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: Tue, 19 May 2009 13:13:07 +0300 [thread overview]
Message-ID: <4A128633.4060800@redhat.com> (raw)
In-Reply-To: <4A12833B.4090804@Voltaire.com>
Or Gerlitz wrote:
>> One solution to this is just to copy that file from kernel-2.6.29. Or
>> maybe it's easier to add some -I flags to kvm compile commandline.
>>
>
> This would not be enough since it needs also the virtio_net header and I'm not clear what version, the kernel one on the one that comes with qemu... Now, all this comes into play only with the qemu provided by kvm releases since the savannah one doesn't have the code that uses TUNSETOFFLOAD, IFF_VNET_HDR etc.
>
> Avi - do you guys have some writeup / guidelines how to make all this work?
>
Modern distros have this sewn up correctly. For example my desktop runs
kernel-2.6.27.21-170.2.56.fc10.x86_64, and has matching headers from
kernel-headers-2.6.27.21-170.2.56.fc10.x86_64.
What are you using?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-05-19 10:13 UTC|newest]
Thread overview: 16+ 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 12:25 ` Or Gerlitz
2009-05-14 11:58 ` Rusty Russell
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 [this message]
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=4A128633.4060800@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=ghaskins@novell.com \
--cc=mjt@tls.msk.ru \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@voltaire.com \
--cc=rusty@rustcorp.com.au \
/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).