i think it's expected behaviour, because dpdk is a userspace implementation
and doesn't have access to kernel space.
Best regads,
Erik Ilavský
On Sun, Apr 11, 2021 at 5:00 PM Erik Ilavsky <erik.ilav...@gmail.com> wrote:
> Hi,
> after openstack installation with charms:
> App Version Status Scale Charm
> Store Rev OS Notes
> ovn-central 20.03.1 active 3 ovn-central
> jujucharms 5 ubuntu
> ovn-chassis 20.03.1 active 3 ovn-chassis
> jujucharms 12 ubuntu
>
> with configuration:
> ovn-chassis:
> charm: cs:ovn-chassis
> bindings:
> "": *internal-space
> ovsdb: *internal-space
> data: *overlay-space
> options:
> ovn-bridge-mappings: physnet1:br-ex physnet2:br-ex physnet3:br-ex
> bridge-interface-mappings: br-ex:bond-dpdk
> enable-sriov: False
> enable-hardware-offload: False
> enable-dpdk: True
> dpdk-bond-mappings: bond-dpdk:84:8f:69:fd:82:4f
> bond-dpdk:84:8f:69:fd:82:50 bond-dpdk:84:8f:69:fd:4d:e7
> bond-dpdk:84:8f:69:fd:4d:e8 bond-dpdk:84:8f:69:fd:86:b7
> bond-dpdk:84:8f:69:fd:86:b8
> dpdk-bond-config: ":active-backup:off:fast"
> dpdk-socket-cores: 2
> dpdk-socket-memory: 1024
>
> kernel parameters, apparmor=0 selinux=0
>
> ovs-vsctl show:
> b8e6f29b-9a9c-405c-b017-f8fdf86fdc33
> Manager "ptcp:6640:127.0.0.1"
> is_connected: true
> Bridge br-ex
> fail_mode: standalone
> datapath_type: netdev
> Port bond-dpdk
> Interface dpdk-819328a
> type: dpdk
> options: {dpdk-devargs="0000:02:00.3"}
> Interface dpdk-c6aeb08
> type: dpdk
> options: {dpdk-devargs="0000:02:00.0"}
> Port br-ex
> Interface br-ex
> type: internal
> Port patch-provnet-58925895-a35e-4be6-a5e9-cafbf1e53c7f-to-br-int
> Interface
> patch-provnet-58925895-a35e-4be6-a5e9-cafbf1e53c7f-to-br-int
> type: patch
> options:
> {peer=patch-br-int-to-provnet-58925895-a35e-4be6-a5e9-cafbf1e53c7f}
> Bridge br-int
> fail_mode: secure
> datapath_type: netdev
> Port patch-br-int-to-provnet-58925895-a35e-4be6-a5e9-cafbf1e53c7f
> Interface
> patch-br-int-to-provnet-58925895-a35e-4be6-a5e9-cafbf1e53c7f
> type: patch
> options:
> {peer=patch-provnet-58925895-a35e-4be6-a5e9-cafbf1e53c7f-to-br-int}
> Port ovn-hp1113-0
> Interface ovn-hp1113-0
> type: geneve
> options: {csum="true", key=flow,
> remote_ip="172.16.180.203"}
> bfd_status: {diagnostic="No Diagnostic", flap_count="0",
> forwarding="false", remote_diagnostic="No Diagnostic", remote_state=down,
> state=down}
> Port ovn-hp1111-0
> Interface ovn-hp1111-0
> type: geneve
> options: {csum="true", key=flow,
> remote_ip="172.16.180.201"}
> bfd_status: {diagnostic="No Diagnostic", flap_count="0",
> forwarding="false", remote_diagnostic="No Diagnostic", remote_state=down,
> state=down}
> Port br-int
> Interface br-int
> type: internal
> ovs_version: "2.13.1"
>
> is problem with geneve tunnels, network interface is missing ():
>
> 2021-04-11T13:12:26.681Z|00278|netdev_linux|INFO|ioctl(SIOCGIFINDEX) on
> genev_sys_6081 device failed: No such device
> 2021-04-11T13:12:26.683Z|00279|netdev_linux|INFO|ioctl(SIOCGIFINDEX) on
> genev_sys_6081 device failed: No such device
>
> #ip link show genev_sys_6081
> Device "genev_sys_6081" does not exist.
> # lsmod | grep geneve
> nothing
>
> I try to set up geneve tunnel directly with ovs and is
> working, genev_sys_6081 is created, after that BFD showed up. I tried to
> delete geneve interface, for creating it with ovn-controller, created but
> with the same result. In strace i didn't find any steps to creating
> interface. It's bug, or I didn't understand something ?
>
> Thank you for your time,
> Best regads,
> Erik Ilavský
>
>
>
>
>
_______________________________________________
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
