On Wed, Nov 26, 2014 at 6:54 PM, Dmitry Nikishov <dnikis...@mirantis.com> wrote: > I've just tried installing ovs-switch 2.3.0 and ovs-common 2.3.0, so > all the ovs packages versions are aligned. That didn't help: as long > as VFs are disabled, it works fine, but not when they are enabled. > > On Wed, Nov 26, 2014 at 4:27 PM, Andrey Korolyov <and...@xdel.ru> wrote: >> On Wed, Nov 26, 2014 at 3:17 PM, Dmitry Nikishov <dnikis...@mirantis.com> >> wrote: >>> Hello all. >>> >>> I'm trying to get OVS working with Intel 82599 and SR-IOV. >>> >>> Basically what I currently have is an Ubuntu 12.04 with custom kernel >>> (3.14.23) and Intel 82599 NIC (eth0) and OVS 1.10 installed. There is >>> also openvswitch-datapath-dkms 2.3.0 which was built for 3.14.23. >>> >>> There is a br-eth0 bridge in OVS, which is connected to eth0 >>> interface. Bridge br-mgmt is connected to br-eth0 and is using VLAN >>> tag 102. >>> >>> Network connectivity via br-mgmt -> br-eth0 -> eth0 chain work fine as >>> long as 82599 Virtual Functions (VFs) are disabled. Once I enable at >>> least 1 VF (echo 1 > /sys/bus/pci/devices/0000:04:00.0/sriov_numvfs), >>> server looses connectivity via this chain. If I try to set up VLAN 102 >>> via ip link directly on eth0, it works. >>> >>> With the help of tcpdump I've found out that packets don't go any >>> further than br-eth0. >>> >>> Software versions: >>> Ubuntu 12.04 with custom kernel 3.14.23 >>> openvswitch-switch 1.10.1+git20130823-0ubuntu3~cloud0 >>> openvswitch-datapath-dkms 2.3.0 >>> >>> On Ubuntu 12.04 with 3.11.8-generic, same openvswitch-switch and >>> openvswitch-datapath-dkms-lts-saucy there is no such issue. >>> >>> Any suggestions? Thanks. >>> _______________________________________________ >>> discuss mailing list >>> discuss@openvswitch.org >>> http://openvswitch.org/mailman/listinfo/discuss >> >> May be it is better to align dp and vswitch versions first, or try >> against -saucy dp with same 3.14, if it is new enough to be built >> against it.
As a VF initialization resulting in an effective interface reappearance with probably different udev name, did you checked that the interface with same name is still visible via netlink, sorry for a silly question? If so, try to re-add the interface first after VF initialization, if it will not help, please post 'ovs-vsctl list Interface eth0' output. Any hints for traffic flow, like inserting static flow with desired port# as a destination and looking into appropriate tcpdump output, if arp propagation is not likely working, are appreciated as well. _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
