On Tue, Oct 19, 2021 at 6:53 PM Ilya Maximets wrote:
> Hi. The ERR log above likely means that you reached the maximum
> number of DPDK ports. Most likely, your DPDK is built with default
> max_ethports, which is 32, and your system has more devices.
> You need to increase
Hello Satish,
On Tue, Oct 19, 2021 at 6:02 PM Ilya Maximets wrote:
>
> On 10/19/21 16:37, Satish Patel wrote:
> > Thank you for reply,
> >
> > I figured out what my issue was. In ubuntu 20.04 you need to install
> > libdpdk-dev package to install all librte drivers. after installing
> > that
On 10/19/21 18:45, David Marchand wrote:
> Hello Satish,
>
> On Tue, Oct 19, 2021 at 6:02 PM Ilya Maximets wrote:
>>
>> On 10/19/21 16:37, Satish Patel wrote:
>>> Thank you for reply,
>>>
>>> I figured out what my issue was. In ubuntu 20.04 you need to install
>>> libdpdk-dev package to install
On 10/19/21 16:37, Satish Patel wrote:
> Thank you for reply,
>
> I figured out what my issue was. In ubuntu 20.04 you need to install
> libdpdk-dev package to install all librte drivers. after installing
> that package my issue got resolved and able to bind nic to ovs bridge.
Hmm. Interesting.
We try to fix issues about that unable to get metadata from localport on
gateway node by the folllowing patch. And this patch assumes that in a logical
switch has only a ha-chassis-group for external ports, put a high priority
flows to forward traffic from localport to localnet in
Thank you for reply,
I figured out what my issue was. In ubuntu 20.04 you need to install
libdpdk-dev package to install all librte drivers. after installing
that package my issue got resolved and able to bind nic to ovs bridge.
On Tue, Oct 19, 2021 at 9:46 AM Ilya Maximets wrote:
>
> > Update:
> Update:
>
> After upgrade firmware still same errors
>
> # ethtool -i ext1
> driver: ixgbe
> version: 5.1.0-k
> firmware-version: 0x800013d1, 20.0.16
> expansion-rom-version:
> bus-info: :af:00.1
> supports-statistics: yes
> supports-test: yes
> supports-eeprom-access: yes
>
Now we using external port type for a sriov interface，but when vm booting，the
following problems occur：
[ 98.774250] cloud-init[805]: 2021-10-15 18:49:10,676 -
url_helper.py[WARNING]: Calling
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [3/120s]:
request error
When I get a chance will try in my lab, but first I have to chase down
an ovs-switchd SEG
that we see very frequently.
On 18/10/2021 16:36, Numan Siddique wrote:
On Mon, Oct 18, 2021 at 9:01 AM Brendan Doyle wrote:
Actually looking at the comments in those patches I'm a little worried.
