[ovs-discuss] Bridge does not specify output ; ignoring? (OVS-DPDK Ubuntu)

Aaron Conole aconole at redhat.com
Wed Dec 7 20:17:44 UTC 2016


"Stokes, Ian" <ian.stokes at intel.com> writes:

>> The mirror-related errors in the log.  ovs-tcpdump creates a mirror.
>
> Are there any other errors in the logs? (with a view to figuring out
> why traffic isn't reaching the VMs). Feel free to attach them if
> you're unsure.
>
> Can you provide some more detail with regards to your setup?
>
> OVS release/commit, DPDK release, QEMU version etc.
>
>> 
>> On Tue, Dec 06, 2016 at 03:05:32PM -0500, Lax Clarke wrote:
>> > Pardon?  What's caused by ovs-tcpdump??????
>> >
>> > On Tue, Dec 6, 2016 at 2:17 PM, Ben Pfaff <blp at ovn.org> wrote:
>> >
>> > > Oh, it's probably caused by ovs-tcpdump, now that I think about it.
>> > >
>> > > On Tue, Dec 06, 2016 at 01:20:19PM -0500, Lax Clarke wrote:
>> > > > I do not think we did.
>> > > >
>> > > > Only config we did:
>> > > >
>> > > > # Subscribers DPDK-based Bridge
>> > > > ovs-vsctl add-br flat-br-0 -- set bridge flat-br-0
>> > > > datapath_type=netdev ovs-vsctl add-port flat-br-0 dpdk0 -- set
>> > > > Interface dpdk0 type=dpdk ovs-vsctl add-port flat-br-0
>> > > > stack-1-pts-1-subscribers-1 -- set Interface
>> > > > stack-1-pts-1-subscribers-1 type=dpdkvhostuser
>> > > >
>> > > > # Internet DPDK-based Bridge
>> > > > ovs-vsctl add-br flat-br-1 -- set bridge flat-br-1
>> > > > datapath_type=netdev ovs-vsctl add-port flat-br-1 dpdk1 -- set
>> > > > Interface dpdk1 type=dpdk ovs-vsctl add-port flat-br-1
>> > > > stack-1-pts-1-internet-1 -- set Interface
>> > > > stack-1-pts-1-internet-1 type=dpdkvhostuser
>> > > >
>> > > > # Bring it up (not sure if needed) ip link set dev flat-br-0 up ip
>> > > > link set dev flat-br-1 up
>> > > >
>> > > > # Enable multi-queue on host side, 4 queues ovs-vsctl set
>> > > > interface dpdk0 options:n_rxq=2 ovs-vsctl set interface dpdk1
>> > > > options:n_rxq=2
>
> How are you launching the VMs (i.e. QEMU, libvirt)?
> What parameters are you using to launch & setup multi-queue for the VM interfaces?

+1 - I'd like to see this information, as well.

Can you also do an `ls -lah $OVS_RUNDIR` where OVS_RUNDIR= the path to
the runtime directory of the vswitchd (usually either
/var/run/openvswitch, or /usr/var/run/openvswitch, or
/usr/local/var/run/openvswitch).

and a `ps aux | grep qemu`

There may be permissions issues when using vhost-user server mode
(possibly even selinux issues with the unix domain socket).

> Thanks
> Ian
>
. . .

>> > > > > > The error I see in ovs switch log says:
>> > > > > > 2016-12-06T17:14:41.170Z|00092|bridge|ERR|bridge flat-br-0:
>> > > > > > mirror
>> > > > > > m_flat-br-0 does not specify output; ignoring
>> > > > > > 2016-12-06T17:14:41.170Z|00093|bridge|ERR|bridge flat-br-0:
>> > > > > > mirror
>> > > > > > m_flat-br-0 does not specify output; ignoring
>> > > > > > 2016-12-06T17:14:41.170Z|00094|bridge|ERR|bridge flat-br-0:
>> > > > > > mirror
>> > > > > > m_flat-br-0 does not specify output; ignoring
>> > > > > > 2016-12-06T17:14:41.171Z|00095|bridge|ERR|bridge flat-br-1:
>> > > > > > mirror
>> > > > > > m_flat-br-1 does not specify output; ignoring
>> > > > > > 2016-12-06T17:14:41.171Z|00096|bridge|ERR|bridge flat-br-1:
>> > > > > > mirror
>> > > > > > m_flat-br-1 does not specify output; ignoring
>> > > > > > 2016-12-06T17:14:41.171Z|00097|bridge|ERR|bridge flat-br-1:
>> > > > > > mirror
>> > > > > > m_flat-br-1 does not specify output; ignoring

Sorry for jumping into this late;  I agree with Ben, this is likely
a mirror error caused by ovs-tcpdump.  I never tried it on the bridge
port, so I'll do some tests and see if I can recreate it.  In the
meantime, if you didn't create those mirror ports, feel free to remove
them.

I doubt it is related to your connectivity issue, though.

>> > > > > > What does this mean?
>> > > > > > I browsed code here
>> > > > > > https://github.com/osrg/openvswitch/blob/master/
>> > > vswitchd/bridge.c#L3641
>> > > > > > It seems to suggest that I need either an output port or an
>> > > > > > output
>> > > vlan.
>> > > > >
>> > > > > How did you configure mirroring?
>> > > > >
>> > >


More information about the discuss mailing list