Re: [ovs-discuss] DPDK vxlan not work
Hi,
On 28/08/2018 02:38, menkeyi wrote:
> [root@compute01 ~]# uname -r
> 3.10.0-862.el7.x86_64
>
> 1、Ovs vxlan mode is available
> 2、Ovs + DPDK vxlan mode is not available
>
Can you provide a bit more info here? What in specific do you see not
working, or not available? And when you say "Ovs vxlan" above (without
DPDK), is that the userspace or the kernel datapath you're referring to?
> DPDK ovs info:
>
> [root@compute01 ~]# ovs-vswitchd --version
> ovs-vswitchd (Open vSwitch) 2.9.0
> DPDK 17.11.0
>
Just a note that the advised version for using with 2.9.0 is (at least)
DPDK v17.11.2, for security concerns. More info here:
http://mails.dpdk.org/archives/announce/2018-April/000192.html
> [root@compute01 ~]# dpdk-devbind --status|head -n10
> Network devices using DPDK-compatible driver
>
> :81:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb'
> drv=vfio-pci unused=
> :84:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb'
> drv=vfio-pci unused=
>
> [root@compute01 ~]# ovs-vsctl show
> b79a7e81-2d68-4ecd-8cd8-bc2b7d1c52ef
> Manager "ptcp:6640:127.0.0.1"
> is_connected: true
> Bridge br-tun
> Controller "tcp:127.0.0.1:6633"
> is_connected: true
> fail_mode: secure
> Port patch-int
> Interface patch-int
> type: patch
> options: {peer=patch-tun}
> Port "vxlan-33000169"
> Interface "vxlan-33000169"
> type: vxlan
> options: {df_default="true", in_key=flow,
> local_ip="51.0.1.101", out_key=flow, remote_ip="51.0.1.105"}
> Port br-tun
> Interface br-tun
> type: internal
> Port "vxlan-330001ca"
> Interface "vxlan-330001ca"
> type: vxlan
> options: {df_default="true", in_key=flow,
> local_ip="51.0.1.101", out_key=flow, remote_ip="51.0.1.202"}
> Bridge br-provider
> Controller "tcp:127.0.0.1:6633"
> is_connected: true
> fail_mode: secure
> Port br-provider
> Interface br-provider
> type: internal
> Port phy-br-provider
> Interface phy-br-provider
> type: patch
> options: {peer=int-br-provider}
> Port "Team1"
> Interface "team1-enp132s0f0"
> type: dpdk
> options: {dpdk-devargs=":84:00.0"}
> Interface "team1-enp129s0f0"
> type: dpdk
> options: {dpdk-devargs=":81:00.0"}
> Bridge br-int
> Controller "tcp:127.0.0.1:6633"
> is_connected: true
> fail_mode: secure
> Port "vhu15e890ef-36"
> tag: 1
> Interface "vhu15e890ef-36"
> type: dpdkvhostuserclient
> options:
> {vhost-server-path="/var/run/openvswitch/vhu15e890ef-36"}
> Port patch-tun
> Interface patch-tun
> type: patch
> options: {peer=patch-int}
> Port int-br-provider
> Interface int-br-provider
> type: patch
> options: {peer=phy-br-provider}
> Port br-int
> Interface br-int
> type: internal
> Port "vhu82caa59c-d3"
> tag: 1
> Interface "vhu82caa59c-d3"
> type: dpdkvhostuserclient
> options:
> {vhost-server-path="/var/run/openvswitch/vhu82caa59c-d3"}
> Port "tapadb8cafa-a0"
> tag: 4095
> Interface "tapadb8cafa-a0"
> type: internal
> ovs_version: "2.9.0"
>
>
>
>
> Create a virtual machine and find that the error is found in the
> ovs-vswitchd.log log. I don't know if it is related to this：
> on vxlan_sys_4789 device failed: No such device
>
>
This shouldn't be related. I'm seeing this on my system as well even
though vxlan is working. It is a bit misleading though, so I'll check
what can lead to this and try to clean it up.
>
> 2018-08-25T02:34:54.453Z|01178|dpdk|INFO|VHOST_CONFIG: vhost-user
> client: socket created, fd: 83
> 2018-08-25T02:34:54.453Z|01179|netdev_dpdk|INFO|vHost User device
> 'vhu82caa59c-d3' created in 'client' mode, using client socket
> '/var/run/openvswitch/vhu82caa59c-d3'
> 2018-08-25T02:34:54.453Z|01180|dpdk|WARN|VHOST_CONFIG: failed to connect
> to /var/run/openvswitch/vhu82caa59c-d3: No such file or directory
> 2018-08-25T02:34:54.453Z|01181|dpdk|INFO|VHOST_CONFIG:
> /var/run/openvswitch/vhu82caa59c-d3: reconnecting...
> 2018-08-25T02:34:54.634Z|01182|dpif_netdev|INFO|Core 8 on numa node 1
> assigned port 'team1-enp129s0f0' rx queue 0 (measured processing cycles
> 587888).
> 2018-08-25T02:34:54.634Z|01183|dpif_netdev|INFO|Core 8 on numa node 1
> assigned port 'team1-enp132s0f0' rx queue 0 (measured processing cycles
> 402684).
>
[ovs-discuss] DPDK vxlan not work
[root@compute01 ~]# uname -r
3.10.0-862.el7.x86_64
1??Ovs vxlan mode is available
2??Ovs + DPDK vxlan mode is not available
DPDK ovs info:
[root@compute01 ~]# ovs-vswitchd --version
ovs-vswitchd (Open vSwitch) 2.9.0
DPDK 17.11.0
[root@compute01 ~]# dpdk-devbind --status|head -n10
Network devices using DPDK-compatible driver
:81:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb' drv=vfio-pci
unused=
:84:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb' drv=vfio-pci
unused=
[root@compute01 ~]# ovs-vsctl show
b79a7e81-2d68-4ecd-8cd8-bc2b7d1c52ef
Manager "ptcp:6640:127.0.0.1"
is_connected: true
Bridge br-tun
Controller "tcp:127.0.0.1:6633"
is_connected: true
fail_mode: secure
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Port "vxlan-33000169"
Interface "vxlan-33000169"
type: vxlan
options: {df_default="true", in_key=flow,
local_ip="51.0.1.101", out_key=flow, remote_ip="51.0.1.105"}
Port br-tun
Interface br-tun
type: internal
Port "vxlan-330001ca"
Interface "vxlan-330001ca"
type: vxlan
options: {df_default="true", in_key=flow,
local_ip="51.0.1.101", out_key=flow, remote_ip="51.0.1.202"}
Bridge br-provider
Controller "tcp:127.0.0.1:6633"
is_connected: true
fail_mode: secure
Port br-provider
Interface br-provider
type: internal
Port phy-br-provider
Interface phy-br-provider
type: patch
options: {peer=int-br-provider}
Port "Team1"
Interface "team1-enp132s0f0"
type: dpdk
options: {dpdk-devargs=":84:00.0"}
Interface "team1-enp129s0f0"
type: dpdk
options: {dpdk-devargs=":81:00.0"}
Bridge br-int
Controller "tcp:127.0.0.1:6633"
is_connected: true
fail_mode: secure
Port "vhu15e890ef-36"
tag: 1
Interface "vhu15e890ef-36"
type: dpdkvhostuserclient
options:
{vhost-server-path="/var/run/openvswitch/vhu15e890ef-36"}
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Port int-br-provider
Interface int-br-provider
type: patch
options: {peer=phy-br-provider}
Port br-int
Interface br-int
type: internal
Port "vhu82caa59c-d3"
tag: 1
Interface "vhu82caa59c-d3"
type: dpdkvhostuserclient
options:
{vhost-server-path="/var/run/openvswitch/vhu82caa59c-d3"}
Port "tapadb8cafa-a0"
tag: 4095
Interface "tapadb8cafa-a0"
type: internal
ovs_version: "2.9.0"
Create a virtual machine and find that the error is found in the
ovs-vswitchd.log log. I don't know if it is related to this??
on vxlan_sys_4789 device failed: No such device
2018-08-25T02:34:54.453Z|01178|dpdk|INFO|VHOST_CONFIG: vhost-user client:
socket created, fd: 83
2018-08-25T02:34:54.453Z|01179|netdev_dpdk|INFO|vHost User device
'vhu82caa59c-d3' created in 'client' mode, using client socket
'/var/run/openvswitch/vhu82caa59c-d3'
2018-08-25T02:34:54.453Z|01180|dpdk|WARN|VHOST_CONFIG: failed to connect to
/var/run/openvswitch/vhu82caa59c-d3: No such file or directory
2018-08-25T02:34:54.453Z|01181|dpdk|INFO|VHOST_CONFIG:
/var/run/openvswitch/vhu82caa59c-d3: reconnecting...
2018-08-25T02:34:54.634Z|01182|dpif_netdev|INFO|Core 8 on numa node 1 assigned
port 'team1-enp129s0f0' rx queue 0 (measured processing cycles 587888).
2018-08-25T02:34:54.634Z|01183|dpif_netdev|INFO|Core 8 on numa node 1 assigned
port 'team1-enp132s0f0' rx queue 0 (measured processing cycles 402684).
2018-08-25T02:34:54.634Z|01184|dpif_netdev|INFO|Core 0 on numa node 0 assigned
port 'vhu82caa59c-d3' rx queue 0 (measured processing cycles 0).
2018-08-25T02:34:54.635Z|01185|bridge|INFO|bridge br-int: added interface
vhu82caa59c-d3 on port 1
2018-08-25T02:34:54.723Z|01186|dpif_netdev|INFO|Core 8 on numa node 1 assigned
port 'team1-enp129s0f0' rx queue 0 (measured processing cycles 587888).
2018-08-25T02:34:54.723Z|01187|dpif_netdev|INFO|Core 8 on numa node 1 assigned
port 'team1-enp132s0f0' rx queue 0 (measured processing cycles 402684).
2018-08-25T02:34:54.723Z|01188|dpif_netdev|INFO|Core 0 on numa node 0 assigned
port 'vhu82caa59c-d3' rx queue 0 (measured processing cycles 0).
2018-08-25T02:34:54.770Z|01189|dpdk|INFO|VHOST_CONFIG: vhost-user client:
socket created, fd: 84
2018-08-25T02:34:54.770Z|01190|netdev_dpdk|INFO|vHost User device
'vhu15e890ef-36' created in
