[ovs-discuss] How to adding ixgbevf port on ovs bridge??

[Jesse Gross]

On Mon, Oct 28, 2013 at 2:30 AM, Sukyoung Oh <crystalring322 at gmail.com> wrote:
> Hi, I ended up that I have misunderstood concept of ovs. you was right,
> totally I was wrong.
>
> according to your advice, I am trying to experiment again.
>
> OK.
>
> as I mentioned before, I am still trying to use ovs on DomU domain through
> VFs.
>
> but, there seems like being problems.
>
> I have two node. One(node1) has IP address 10.0.1.1, and another(node2) has
> 10.0.1.2 individually.
>
> and In DomU domain, there is a ovs-bridge br0.
>
> eth1 connected to node1 and eth2 connected to node2 was added into br0 using
> ovs-vsctl add-port instruction.
>
> and I inserted simple rules in br0 using ovs-ofctl add-flow instruction.
>
> The flows are that "in_port=1, actions=output:2", "in_port=2,
> actions=output:1".  it is very simple.
>
> I was ping to node2(10.0.1.2) on node1.
>
> I checked dump-ports br0.
>
> eth1's rx was increased. and eth2's tx was increased. It looks that my
> simple flows are exactly matched and operated, vice versa.
>
> but node2 couldn't receive anything.
>
> I experimented the same setting and same flows on Dom0 through PFs.
>
> It worked as I wanted, pinging to each other was worked well.
>
> All other conditions are same. the only difference is interface driver.
> whether PFs or VFs.
>
>
> you told me ovs may not support SR-IOV VFs. I experienced that.
>
> Is there a way to solve this problem?

You would have to track down the exact cause of the limitation. It
might not be possible to change things or you might have to adjust
security policies, etc. The first thing that I would look at is
whether the use of promiscuous mode is causing a problem.