But you run VPP from systemd unit files, are you sure LD_LIBRARY_PATH is still 
set?
Can you try:
~# sudo 
LD_LIBRARY_PATH=/home/chris/workspace/vpp/build/external/_build/dpdk-19.05/x86_64-native-linuxapp-gcc/lib
 /home/chris/workspace/vpp/build-root/install-vpp-native/vpp/bin/vpp "unix { 
interactive } dpdk { dev 0002:00:02.0 vdev net_vdev_netvsc0,iface=eth1 dev 
0003:00:02.0 vdev net_vdev_netvsc1,iface=eth2 }"
And share the output?

Best
ben

> -----Original Message-----
> From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of Chris King
> Sent: vendredi 31 janvier 2020 18:05
> To: vpp-dev@lists.fd.io
> Subject: Re: [vpp-dev] interface activation problem using VPP in Azure
> with DPDK failsafe interfaces #vpp #dpdk #azure
> 
> Ben,
> 
> I tried what you suggested but it didn't work for me (yet) :-(.  In order
> to get the *glue* libraries to build I had to go into
> vpp/build/external/packages and run 'make dpdk-install'. Then I set
> LD_LIBRARY_PATH (was previously unset) and I issued the following
> commands:
> 
> 
> echo $LD_LIBRARY_PATH
> /home/chris/workspace/vpp/build/external/_build/dpdk-19.05/x86_64-native-
> linuxapp-gcc/lib
> 
> 
> ll $LD_LIBRARY_PATH  | grep glue
> -rwxrwxr-x 1 chris chris   54704 Jan 31 16:19
> librte_pmd_mlx4_glue.so.18.02.0*
> -rwxrwxr-x 1 chris chris   71792 Jan 31 16:19
> librte_pmd_mlx5_glue.so.19.05.0*
> 
> 
> ~/workspace/vpp$ sudo systemctl restart vpp
> ~/workspace/vpp$ sudo vppctl show log
> 2020/01/31 16:53:33:240 warn       dpdk       EAL init args: -c 2 -n 4 --
> in-memory --vdev net_vdev_netvsc0,iface=eth1 --vdev
> net_vdev_netvsc1,iface=eth2 --file-prefix vpp -w 0002:00:02.0 -w
> 0003:00:02.0 --master-lcore 1
> 2020/01/31 16:53:33:453 warn       dpdk       unsupported rx offloads
> requested on port 0: jumbo-frame
> 2020/01/31 16:53:33:455 warn       dpdk       unsupported rx offloads
> requested on port 2: jumbo-frame
> 2020/01/31 16:53:33:457 notice     dpdk       EAL: Detected 4 lcore(s)
> 2020/01/31 16:53:33:457 notice     dpdk       EAL: Detected 1 NUMA nodes
> 2020/01/31 16:53:33:457 notice     dpdk       EAL: No available hugepages
> reported in hugepages-1048576kB
> 2020/01/31 16:53:33:457 notice     dpdk       EAL: No free hugepages
> reported in hugepages-1048576kB
> 2020/01/31 16:53:33:457 notice     dpdk       EAL: No available hugepages
> reported in hugepages-1048576kB
> 2020/01/31 16:53:33:457 notice     dpdk       EAL: Probing VFIO support...
> 2020/01/31 16:53:33:457 notice     dpdk       EAL: WARNING! Base virtual
> address hint (0xa80001000 != 0x7f1c00000000) not respected!
> 2020/01/31 16:53:33:457 notice     dpdk       EAL:    This may cause
> issues with mapping memory into secondary processes
> 2020/01/31 16:53:33:457 notice     dpdk       EAL: WARNING! Base virtual
> address hint (0xc00002000 != 0x7f13c0000000) not respected!
> 2020/01/31 16:53:33:457 notice     dpdk       EAL:    This may cause
> issues with mapping memory into secondary processes
> 2020/01/31 16:53:33:457 notice     dpdk       EAL: WARNING! Base virtual
> address hint (0xd80003000 != 0x7f0b80000000) not respected!
> 2020/01/31 16:53:33:457 notice     dpdk       EAL:    This may cause
> issues with mapping memory into secondary processes
> 2020/01/31 16:53:33:457 notice     dpdk       EAL: WARNING! Base virtual
> address hint (0xdc0a64000 != 0x7f077fe00000) not respected!
> 2020/01/31 16:53:33:457 notice     dpdk       EAL:    This may cause
> issues with mapping memory into secondary processes
> 2020/01/31 16:53:33:457 notice     dpdk       EAL: WARNING! Base virtual
> address hint (0xdc16c5000 != 0x7f037fc00000) not respected!
> 2020/01/31 16:53:33:457 notice     dpdk       EAL:    This may cause
> issues with mapping memory into secondary processes
> 2020/01/31 16:53:33:457 notice     dpdk       EAL: WARNING! Base virtual
> address hint (0xdc2326000 != 0x7eff7fa00000) not respected!
> 2020/01/31 16:53:33:457 notice     dpdk       EAL:    This may cause
> issues with mapping memory into secondary processes
> 2020/01/31 16:53:33:457 notice     dpdk       EAL: WARNING! Base virtual
> address hint (0xdc2f87000 != 0x7efb7f800000) not respected!
> 2020/01/31 16:53:33:457 notice     dpdk       EAL:    This may cause
> issues with mapping memory into secondary processes
> 2020/01/31 16:53:33:457 notice     dpdk       EAL: WARNING: cpu flags
> constant_tsc=yes nonstop_tsc=no -> using unreliable clock cycles !
> 2020/01/31 16:53:33:457 notice     dpdk       net_vdev_netvsc: probably
> using routed NetVSC interface "eth1" (index 3)
> 2020/01/31 16:53:33:457 notice     dpdk       EAL: Driver cannot attach
> the device (0002:00:02.0)
> 2020/01/31 16:53:33:457 notice     dpdk       EAL: Failed to attach device
> on primary process
> 2020/01/31 16:53:33:457 notice     dpdk       net_failsafe: sub_device 0
> probe failed (No such file or directory)
> 2020/01/31 16:53:33:457 notice     dpdk       tun_alloc(): Rx trigger
> disabled: Device or resource busy
> 2020/01/31 16:53:33:457 notice     dpdk       net_vdev_netvsc: probably
> using routed NetVSC interface "eth2" (index 4)
> 2020/01/31 16:53:33:457 notice     dpdk       EAL: Driver cannot attach
> the device (0003:00:02.0)
> 2020/01/31 16:53:33:457 notice     dpdk       EAL: Failed to attach device
> on primary process
> 2020/01/31 16:53:33:457 notice     dpdk       net_failsafe: sub_device 0
> probe failed (File exists)
> 2020/01/31 16:53:33:457 notice     dpdk       tun_alloc(): Rx trigger
> disabled: Device or resource busy
> 2020/01/31 16:53:33:457 notice     dpdk       EAL:   VFIO support not
> initialized
> 2020/01/31 16:53:33:457 notice     dpdk       EAL: Couldn't map new region
> for DMA
> 2020/01/31 16:53:33:457 notice     dpdk       tun_alloc(): Rx trigger
> disabled: Device or resource busy
> 2020/01/31 16:53:33:457 notice     dpdk       tun_alloc(): Rx trigger
> disabled: Device or resource busy
> 2020/01/31 16:53:35:404 notice     dpdk       EAL: Driver cannot attach
> the device (0002:00:02.0)
> 2020/01/31 16:53:35:404 notice     dpdk       EAL: Failed to attach device
> on primary process
> 2020/01/31 16:53:35:404 notice     dpdk       net_failsafe: sub_device 0
> probe failed (No such file or directory)
> 2020/01/31 16:53:35:448 notice     dpdk       EAL: Driver cannot attach
> the device (0003:00:02.0)
> 2020/01/31 16:53:35:448 notice     dpdk       EAL: Failed to attach device
> on primary process
> 2020/01/31 16:53:35:448 notice     dpdk       net_failsafe: sub_device 0
> probe failed (No such file or directory)
> 
> Did I do something wrong? Talking to Stephen Hemminger, he suggests I just
> used the netsvc PMD which I might also try:
> https://doc.dpdk.org/guides/nics/netvsc.html
> 
> Thanks,
> 
> Chris
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#15305): https://lists.fd.io/g/vpp-dev/message/15305
Mute This Topic: https://lists.fd.io/mt/69987045/21656
Mute #vpp: https://lists.fd.io/mk?hashtag=vpp&subid=1480452
Mute #dpdk: https://lists.fd.io/mk?hashtag=dpdk&subid=1480452
Mute #azure: https://lists.fd.io/mk?hashtag=azure&subid=1480452
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to