[ovs-dev] [PATCH 2/3] ovs-dev: Hint that vport modules may need to be loaded manually

Thomas Graf tgraf at noironetworks.com
Tue Apr 7 18:14:55 UTC 2015


On 04/07/15 at 02:47pm, Flavio Leitner wrote:
> On Tue,  7 Apr 2015 12:43:42 +0200
> Thomas Graf <tgraf at noironetworks.com> wrote:
> 
> > In case the openvswitch.ko is loaded manually without dependencies
> > built, the vport modules need to be loaded manually as well.
> > 
> > Signed-off-by: Thomas Graf <tgraf at noironetworks.com>
> > ---
> >  utilities/ovs-dev.py | 3 +++
> >  1 file changed, 3 insertions(+)
> > 
> > diff --git a/utilities/ovs-dev.py b/utilities/ovs-dev.py
> > index 9467df5..987e3b0 100755
> > --- a/utilities/ovs-dev.py
> > +++ b/utilities/ovs-dev.py
> > @@ -316,6 +316,9 @@ Basic Configuration:
> >      # Install the kernel module
> >      sudo insmod %(ovs)s/datapath/linux/openvswitch.ko
> >  
> > +    # If needed, manually load required vport modules
> > +    sudo insmod %(ovs)s/datapath/linux/vport-vxlan.ko
> > +
> 
> To be backwards compatible, perhaps modinst() should load all
> available vport-* modules by default?
> 
> I don't know who is using, but since it's a helper I would
> assume that the kernel details are hidden from the user.

Good point. I'll add this.



More information about the dev mailing list