[ovs-discuss] VxLAN kernel module.

[Sudipto Biswas]

Hi Pravin, Fan Du,

Appreciate your help.

To conclude, for VxLAN to work on Kernel 3.10 - do I need to explicitly 
load the vxlan.ko and then re-build OVS to make use of it?

I can see that CONFIG_VXLAN is set to 'm'

Do I need to re-build OVS to use this module? (after i have used 
modprobe to load it?) Shouldn't the OVS install process take care of 
loading the VxLAN kernel module by itself?

Thanks,
Sudipto

On Wednesday 11 March 2015 12:49 PM, Sudipto Biswas wrote:
>
> On Wednesday 11 March 2015 12:36 PM, Sudipto Biswas wrote:
>>
>> On Wednesday 11 March 2015 12:12 PM, Fan Du wrote:
>>> 于 2015年03月11日 14:42, Sudipto Biswas 写道:
>>>>
>>>> On Wednesday 11 March 2015 11:35 AM, Fan Du wrote:
>>>>> 于 2015年03月11日 01:38, Sudipto Biswas 写道:
>>>>>> Hi,
>>>>>>
>>>>>> I have a very small query. I am using OVS 2.3.1 and i have built 
>>>>>> the kernel module etc following the instructions in the INSTALL 
>>>>>> file.
>>>>>>
>>>>>> I was also, able to create vxlan ports and communicate across two 
>>>>>> VMs on two different machines using VxLAN tunnels.
>>>>>>
>>>>>> However, if i do a lsmod on my machine, it doesn't list the vxlan 
>>>>>> kernel module.
>>>>>
>>>>> CONFIG_VXLAN is set as 'y' or 'm' ?
>>>>    Where would you want me to set this option? As in some file?
>>> oh...
>>>
>>> If you are using your host default config, then kernel config file 
>>> is at /boot/config-2.6.32-358.el6.x86_64,
>>> the suffix may varies depending on your kernel version.
>>>
>>> cat /boot/config-2.6.32-358.el6.x86_64 | grep CONFIG_VXLAN
>>>
>>   Thanks, I found that the vxlan module was built. Then did a 
>> modprobe of the vxlan module and now lsmod lists vxlan.
>>   However, like the gre module is being used/referenced by 
>> openvswitch - vxlan doesn't have a reference count:
>>
>>   lsmod | grep vxlan
>>     vxlan                  29379  0
>>     ip_tunnel              20094  1 vxlan
>>
>>   lsmod | grep gre
>>    gre                     5383  1 openvswitch
>>
>>   Shouldn't we have the vxlan being referenced by OVS as well? (since 
>> i have some vxlan ports created)
>>   I have a very basic knowledge of the kernel , so please bear with 
>> me :-)
>   To answer your first question though:
>
>   CONFIG_VXLAN=m - this is the setting in the kernel config.
>   I am guessing that the kernel module should be loaded by openvswitch 
> when we build it for the kernel?
>
>>>>>> lsmod | grep openvswitch
>>>>>> openvswitch           123112  0
>>>>>> gre                     5383  1 openvswitch
>>>>>> libcrc32c               1922  1 openvswitch
>>>>>>
>>>>>> Now i am beginning to think, if i should see the vxlan module 
>>>>>> there as well?
>>>>>> If yes, then i wonder how my setup is working? :-)
>>>>>>
>>>>>> Appreciate your help!
>>>>>>
>>>>>> Thanks.
>>>>>> Sudipto
>>>>>>
>>>>>> _______________________________________________
>>>>>> discuss mailing list
>>>>>> discuss at openvswitch.org
>>>>>> http://openvswitch.org/mailman/listinfo/discuss
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>
>> _______________________________________________
>> discuss mailing list
>> discuss at openvswitch.org
>> http://openvswitch.org/mailman/listinfo/discuss
>
> _______________________________________________
> discuss mailing list
> discuss at openvswitch.org
> http://openvswitch.org/mailman/listinfo/discuss