From: Mats Liljegren <liljegren.mats2@gmail.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] How to debug packet sends to virtual functions
Date: Fri, 31 Jan 2014 19:30:38 +0100 [thread overview]
Message-ID: <CA+xJJ19NNcsyRx_N12SB9JyaBicFXOXcMqBhgoUbesaruJVQPA@mail.gmail.com> (raw)
In-Reply-To: <CA+xJJ1-74cZALNj4M8-P5FUVV8hNYbdB90Fk+i+v2sTQ6QqkSw@mail.gmail.com>
I have a follow-up on this:
ixgbe version 3.13.10-k
ixgbevf version 2.7.12-k
(These are what was provided by Ubuntu 13.10)
I tried the following sequence on the host, before starting the guest:
1) sudo rmmod ixgbe
2) sudo modprobe ixgbe max_vfs=2
3) sudo ifconfig em1 up # This is the physical function
4) sudo ifconfig em1_0 192.168.2.2 # This is the virtual function
5) ping 192.168.2.1
I can see that the ping request reaches its target, and a reply is
sent back. But this reply is not received by the ping shell command.
Why?
Regards,
Mats
On Wed, Jan 29, 2014 at 6:56 PM, Mats Liljegren
<liljegren.mats2@gmail.com> wrote:
> I'm trying to get a modified version of the l2fwd example running, and
> have problems with packets being silently thrown away. I can receive
> packets, and my printf's indicates that the packets are being sent to
> the correct port, using correct MAC address as source address. And
> still, the packets are lost.
>
> Since the port is a virtual function, it seems like I cannot use
> tcpdump on it to see the network traffic. There is nothing coming out
> of the cable (activity light not flashing, the receiving end running
> tcpdump does not see any traffic).
>
> I'm using two X540 with two virtual functions each. The application
> runs in a KVM/Qemu environmen.
>
> Any suggestions how to debug this?
>
> Regards,
> Mats
next prev parent reply other threads:[~2014-01-31 18:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 17:56 Mats Liljegren
2014-01-31 18:30 ` Mats Liljegren [this message]
2014-02-03 11:13 ` Mats Liljegren
2014-02-04 10:08 ` Mats Liljegren
2014-02-04 10:26 ` jigsaw
2014-02-04 10:45 ` Mats Liljegren
2014-02-04 11:14 ` jigsaw
2014-02-04 11:31 ` Mats Liljegren
2014-02-04 12:11 ` jigsaw
2014-02-04 11:21 ` Burakov, Anatoly
2014-02-04 11:47 ` Mats Liljegren
2014-02-04 11:52 ` Burakov, Anatoly
2014-02-04 13:03 ` Mats Liljegren
2014-02-04 13:40 ` Burakov, Anatoly
2014-02-13 15:32 ` Mats Liljegren
2014-02-13 15:39 ` Burakov, Anatoly
2014-02-17 11:05 ` Mats Liljegren
2014-02-17 12:11 ` Burakov, Anatoly
2014-02-17 12:29 ` Mats Liljegren
2014-02-17 14:35 ` Mats Liljegren
2014-02-17 14:36 ` Burakov, Anatoly
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=CA+xJJ19NNcsyRx_N12SB9JyaBicFXOXcMqBhgoUbesaruJVQPA@mail.gmail.com \
--to=liljegren.mats2@gmail.com \
--cc=dev@dpdk.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).