On Fri, Nov 10, 2017 at 02:45:05PM -0800, Gurucharan Shetty wrote:
> From OVS 2.8, ovs-vswitchd, when it starts, will
> load the kernel modules for tunnels. It has logic
> inside it to choose either upstream kernel module
> or vport-* kernel module.
>
> So, when we run 'force-reload-kmod' to
On 13 November 2017 at 06:43, William Tu wrote:
> On Fri, Nov 10, 2017 at 2:45 PM, Gurucharan Shetty wrote:
> > From OVS 2.8, ovs-vswitchd, when it starts, will
> > load the kernel modules for tunnels. It has logic
> > inside it to choose either upstream kernel
On Fri, Nov 10, 2017 at 2:45 PM, Gurucharan Shetty wrote:
> From OVS 2.8, ovs-vswitchd, when it starts, will
> load the kernel modules for tunnels. It has logic
> inside it to choose either upstream kernel module
> or vport-* kernel module.
>
> So, when we run 'force-reload-kmod' to
>From OVS 2.8, ovs-vswitchd, when it starts, will
load the kernel modules for tunnels. It has logic
inside it to choose either upstream kernel module
or vport-* kernel module.
So, when we run 'force-reload-kmod' to upgrade to
OVS 2.8 from a previous version, we do not need to
remember the