sorry about that
# ovs-vsctl get Open_vSwitch . other_config
{dpdk-init="true", n-dpdk-rxqs="2", pmd-cpu-mask="0x6"}
On Tue, Sep 19, 2017 at 8:02 PM, Flavio Leitner wrote:
> On Tue, 19 Sep 2017 13:43:25 +0800
> Sun Paul wrote:
>
>> Hi
>>
>> below is the output. currently, I am only able to set
Finally got around to tracing this bug.
As indicated by Ben I used git bisect to find the issue. Very neat feature of
git!
Copy paste of my findings:
<<
Attending to the instructions received in the mailing list, I have managed to
find the culprit via git bisect.
The bug I am experiencing seem
On 9/19/17, 8:48 AM, "Darrell Ball" wrote:
On 9/19/17, 8:22 AM, "Loftus, Ciara" wrote:
> On 09/19/2017 08:58 AM, Loftus, Ciara wrote:
> >> Thanks for confirming Devendra
> >>
> >> Adding Ciara
> >> T
On 9/19/17, 8:22 AM, "Loftus, Ciara" wrote:
> On 09/19/2017 08:58 AM, Loftus, Ciara wrote:
> >> Thanks for confirming Devendra
> >>
> >> Adding Ciara
> >> There have been some offline discussions regarding the issue.
> >
> > The workarou
> On 09/19/2017 08:58 AM, Loftus, Ciara wrote:
> >> Thanks for confirming Devendra
> >>
> >> Adding Ciara
> >> There have been some offline discussions regarding the issue.
> >
> > The workaround discussed is a patch to enable backwards compatibility
> with the old port IDs. Something like the foll
On 09/19/2017 08:58 AM, Loftus, Ciara wrote:
>> Thanks for confirming Devendra
>>
>> Adding Ciara
>> There have been some offline discussions regarding the issue.
>
> The workaround discussed is a patch to enable backwards compatibility with
> the old port IDs. Something like the following:
>
>
Hi Wang,
Typically I reserve between 512M and 1G on each Numa.
There is no formula I am aware of for how much memory is actually required.
Fundamentally this will be determined by the maximum number and size of packets
in-flight at any given time. Which is determined by the ingress packet rate,
On Tue, 19 Sep 2017 13:43:25 +0800
Sun Paul wrote:
> Hi
>
> below is the output. currently, I am only able to set to use two CPU for PMD.
I was referring to the output of
ovs-vsctl get Open_vSwitch . other_config
fbl
>
> # ovs-vsctl show
> ea7f2b40-b7b3-4f11-a81f-cf25a56f8172
> Bridge "
Hi Vikrant,
Please note that you won't see the metadata namespace getting created
right after creating a network. The namespace will be present only when
necessary; ie., when a port is bound to a chassis and then the metadata
agent
will detect that condition and create/provision the metadata names
Hi Vikrant,
Please see this link -
https://gist.github.com/russellb/4ab0a9641f12f8ac66fdd6822ee7789e and grep
for "add_phys_port".
Can you see what is the value of "ovn_metadata_enabled" in the file
/etc/neutron/plugins/ml2/ml2_conf.ini.
If it is false, then please change it to true and restart
> Thanks for confirming Devendra
>
> Adding Ciara
> There have been some offline discussions regarding the issue.
The workaround discussed is a patch to enable backwards compatibility with the
old port IDs. Something like the following:
– set Interface portX options:dpdk-devargs=dpdkportid0
Lo
Hi actually I solved this myself. I call the solution to this problem "The
Lawnmower Man" solution. The updated solution is here:
https://sites.google.com/site/nandydandyoracle/openvswitch-ovs/networking-problem-1
___
discuss mailing list
disc...@ope
12 matches
Mail list logo
