Hey,

Have you tried with this commit?  Should be fine now,

commit 4ceb6c87968da7bcf025e4d4aef1a8da81eb24b4
Author: Thomas Graf <tg...@noironetworks.com>
Date:   Wed Feb 4 07:45:06 2015 -0800

    datapath: Fix missing symbols when required to use own VXLAN stack

    Fixes an insufficient ifdef in compat/vxlan.c which caused required
    symbols not to be included in the build. The declarations were properly
    enabled so the build would succeed but the module would spit missing
    symbols when being inserted.

    The fix uses a new define USE_UPSTREAM_VXLAN which is set in the compat
    header <net/vxlan.h> as required. This centralizes the decision when to
    include VXLAN compat code to a single place which eases further changes.

    Reported-by: Pravin Shelar <pshe...@nicira.com>
    Signed-off-by: Thomas Graf <tg...@noironetworks.com>
    Acked-by: Pravin B Shelar <pshe...@nicira.com>

Thanks,
Alex Wang,

On Thu, Feb 5, 2015 at 8:50 AM, eyal <eya...@hotmail.com> wrote:

> OS: Centos7
>
> kernel:* latest - 3.10.0-123.20.1.el7.x86_64*
>
> OVS : 2.3.90 . the latest master - openvswitch-ovs-4d9226a
>
>
>
> The H file datapath/linux/compat/include/net/vxlan.h  has :
>
> IFNDEF HAVE_VXLAN_METADATA
>
>
>
> Which define prototype *rpl_vxlan_xmit_skb.*
>
>
>
> *However the c file datapath/linux/compat/vxlan.c*
>
> *Doesn't implement this function because USE_KERNEL_TUNNEL_API  isn't
> define in the kernel header/ .config of 3.10.0-123.20.1.el7.x86_64.*
>
>
>
> For that reason I have on dmesg file :
>
> *dmesg | grep openvswitch*
>
> [ 7177.899305] openvswitch: Unknown symbol rpl_vxlan_xmit_skb (err 0)
>
> [ 7177.899338] openvswitch: Unknown symbol rpl_vxlan_sock_release (err 0)
>
> [ 7177.899371] openvswitch: Unknown symbol rpl_vxlan_sock_add (err 0)
>
>
>
> Which kernel version contain this feature ?
>
>
>
> Thanks !
>
>
>
> _______________________________________________
> discuss mailing list
> discuss@openvswitch.org
> http://openvswitch.org/mailman/listinfo/discuss
>
>
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to