Hi John,
I have had some problems on Azure with my build lately similar to the MTU
errors you mentioned. The build that has problems is based on the
commit b0f0f8c8d ("memif: fix memif_process_desc indexing") from the
upstream master branch (so..master branch from 1 or 2 months ago using DPDK
21.1
Hello Matt,
Can you *please *confirm which DPDK and VPP versions you have that are
working in Azure?
I am hoping to get a base build with no errors and the ability to set MTU
size...
*Thank you in advance for your help!!!*
--
John M.
On Mon, May 2, 2022 at 1:42 PM Matthew Smith wrote:
>
> S
Hello Matt,
*Here is some more detail that may be useful:*
*Loaded modules (loaded by doing `* *modprobe uio_hv_generic`):*
*[root@demo001 vpp]# lsmod | grep uio*
*uio_pci_generic16384 0*
*uio_hv_generic 16384 12*
*hv_vmbus 143360 9
hv_balloon,hv_utils,uio_hv_
Hello Matt,
Thank you again for the response.
So we were able to compile but now are unable to start VPP.
We are seeing the following errors:
I rebuilt, and got:
May 02 20:20:24 demo001 vpp[2161]: vpp[2161]: perfmon: skipping source
'intel-uncore' - intel_uncore_init: no uncore units found
Ma
Sorry, there was a typo. You should use DPDK_MLX5_COMMON_PMD=y instead
of DPDK_MLX_COMMON_PMD=y.
-Matt
On Mon, May 2, 2022 at 11:28 AM Johnny Martinez
wrote:
> Hello Matt!
>
> *Thank you very much for the reply!*
>
> Our end goal is to be using Alma Linux but we went ahead and tried it in a
>
[Edited Message Follows]
Hi Matt,
I run two vpp instance (different prefix) in same hyper-v vm, the first vpp
instance prefix is vs, second is vc. I have eth1 and eth2, the config is below:
I start the vs and vc instance one by one, after vc instance started, the first
instance vs stuck in dpdk
Hi Matt,
I run two vpp instance (different prefix) in same hyper-v vm, the first vpp
instance prefix is vs, second is vc. I have eth1 and eth2, the config is below:
I start the vs and vc instance one by one, after vc instance started, the first
instance vs stuck in dpdk wait function. Does one hy
Hi John,
Are you using a stock build of VPP from packagecloud or did you build your
own? VPP's build of DPDK does not enable the Mellanox (mlx4, mlx5) PMDs by
default. If you didn't already, you would need to build VPP with the
environment variables DPDK_MLX4_PMD, DPDK_MLX5_PMD, and
DPDK_MLX_COMM
Johnny Martinez
9:57 AM (5 hours ago)
to Benoit
*@Ben *- thank you *VERY *much for the detailed response!
I had *partial *success but almost there - now I am seeing some DPDK errors
and other behavior outlined below.
On my test device I have 3 interfaces:
- Management interface (kernel inter
Thanks Matt!
-daw-
On 4/29/2022 2:40 PM, Matthew Smith via lists.fd.io wrote:
Hi Ben,
Sure, I'll work on an update to the doc.
-Matt
On Fri, Apr 29, 2022 at 3:48 AM Benoit Ganne (bganne)
wrote:
Hi Matt, John,
This is a great summary!
>> The only reference I could find for
Hi Ben,
Sure, I'll work on an update to the doc.
-Matt
On Fri, Apr 29, 2022 at 3:48 AM Benoit Ganne (bganne)
wrote:
> Hi Matt, John,
>
> This is a great summary!
>
> >> The only reference I could find for VPP in Azure was in this link
> >> but it is very outdated:
> >> https://fd.io/docs/vpp/
Hi Matt, John,
This is a great summary!
>> The only reference I could find for VPP in Azure was in this link
>> but it is very outdated:
>> https://fd.io/docs/vpp/v2101/usecases/vppinazure.html
> Yes, that doc is way outdated. I advise against following the instructions
> in it.
Matt or John, w
Hi John,
See answers inline below...
On Thu, Apr 28, 2022 at 12:51 PM John Martinez
wrote:
> Hello everyone!
>
> This is my first post to the list!
>
> I was able to setup VPP in AWS after
> properly identifying the instance type that would allow VPP to grap the PCI
> addresses that I needed to
13 matches
Mail list logo
