On Thu, Sep 22, 2016 at 5:44 PM, Flavio Fernandes wrote:
>> On Sep 22, 2016, at 6:53 PM, Jesse Gross wrote:
>> When an OVS vport is created, a reference is taken on the
>> corresponding vport-*.ko module. However, in the case of internal
>> ports created by the datapath, the internal device vport
> On Sep 22, 2016, at 6:53 PM, Jesse Gross wrote:
>
> I think this isn't actually related to tunnels - ovn-controller
> deletes the tunnel ports that it creates when it exits gracefully.
> Plus, it seems like vport-geneve was unloaded successfully.
>
That is right, unloading of vport-geneve ha
I think this isn't actually related to tunnels - ovn-controller
deletes the tunnel ports that it creates when it exits gracefully.
Plus, it seems like vport-geneve was unloaded successfully.
When an OVS vport is created, a reference is taken on the
corresponding vport-*.ko module. However, in the
On 22 September 2016 at 13:53, Flavio Fernandes wrote:
>
> > On Sep 22, 2016, at 2:48 PM, Guru Shetty wrote:
> >
> >
> >
> > On 22 September 2016 at 09:54, Flavio Fernandes
> wrote:
> >
> > > On Sep 22, 2016, at 10:59 AM, Guru Shetty wrote:
> > >
> > > I think it usually happens because the ge
> On Sep 22, 2016, at 2:48 PM, Guru Shetty wrote:
>
>
>
> On 22 September 2016 at 09:54, Flavio Fernandes wrote:
>
> > On Sep 22, 2016, at 10:59 AM, Guru Shetty wrote:
> >
> > I think it usually happens because the geneve tunnel exists in the kernel
> > datapath. The right way to do this i
On 22 September 2016 at 09:54, Flavio Fernandes wrote:
>
> > On Sep 22, 2016, at 10:59 AM, Guru Shetty wrote:
> >
> > I think it usually happens because the geneve tunnel exists in the
> kernel datapath. The right way to do this is via
> '/etc/init.d/openvswitch-switch
> force-reload-kmod'
> >
> On Sep 22, 2016, at 10:59 AM, Guru Shetty wrote:
>
> I think it usually happens because the geneve tunnel exists in the kernel
> datapath. The right way to do this is via '/etc/init.d/openvswitch-switch
> force-reload-kmod'
>
Oh cool. Thanks for showing me 'force-reload-kmod', Guru!
I can
On Thu, Sep 22, 2016 at 10:21:04AM +0200, Ashish Kurian wrote:
> After I installed OVS 2.5 on my machine and reboot it, I get this error
> when I try to start OVS. I could fix this by doing the following steps
> after every reboot, but I want to know if I can fix this permanently.
>
> sudo ovsdb-s
I think it usually happens because the geneve tunnel exists in the kernel
datapath. The right way to do this is via '/etc/init.d/openvswitch-switch
force-reload-kmod'
On 22 September 2016 at 01:46, Flavio Fernandes wrote:
> [cc: Jesse]
>
> Hi folks,
>
> While playing with branch-2.6, I've notice
Use a startup script.
On 22 September 2016 at 01:21, Ashish Kurian wrote:
> Dear Developers,
>
> After I installed OVS 2.5 on my machine and reboot it, I get this error
> when I try to start OVS. I could fix this by doing the following steps
> after every reboot, but I want to know if I can fix
Hi All,
Does Traffic Shaping supported on VhostUser ports, using either
linux TC utility or OVS HTB Qdisc ? My understanding is currently it
supports only Egress Policer.
Also is there way to rate limit the traffic (Bandwidth) from Guest Os
(It runs OVS) to Host Vm ? (the communication
[cc: Jesse]
Hi folks,
While playing with branch-2.6, I've noticed that something may not be cleaned
properly
in the kernel with openvswitch module; [only] when ovn was configured.
What I observe [below] is that as soon as I configure info used by
ovn-controller to
connect to sb db, I am unable
Dear Developers,
After I installed OVS 2.5 on my machine and reboot it, I get this error
when I try to start OVS. I could fix this by doing the following steps
after every reboot, but I want to know if I can fix this permanently.
sudo ovsdb-server --remote=punix:/usr/local/var/run/openvswitch/db.
13 matches
Mail list logo
