Thanks for the response.
Just sending the mail again, hopefully in the right format
For the 2 NIC part, i avoided that by doing the unbind/bind from the console.
Still saw the same issue.
RegardsSachin
===========START===================================================
EAL: Detected 2 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket/var/run/dpdk/rte/mp_socket
EAL: No free hugepages reported inhugepages-1048576kBEAL: Probing VFIO
support...Oct 8 07:35:17 master-nodekni[19444]:
EAL: Probing VFIO support...
EAL: PCI device 0000:00:04.0 on NUMAsocket -1
EAL: Invalid NUMA socket, default to0
EAL: probe driver: 1af4:1000net_virtioOct 8 07:35:17 master-node kni[19444]:
EAL: PCI device 0000:00:04.0 on NUMAsocket -1Oct 8 07:35:17 master-node
kni[19444]:
EAL: Invalid NUMA socket, default to0Oct 8 07:35:17 master-node kni[19444]:
EAL: probe driver: 1af4:1000 net_virtio
EAL: Error - exiting with code: 1Cause: No supported Ethernet device foundOct 8
07:35:17 master-nodekni[19444]:
EAL: Error - exiting with code: 1#012Cause:Oct 8 07:35:17 master-node
kni[19444]: No supported Ethernet device found
I have set 128 hugepages each of size128KB
AnonHugePages: 0 kB
ShmemHugePages: 0 kB
HugePages_Total: 128
HugePages_Free: 114
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
ens4:flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1460
inet10.128.0.17 netmask 255.255.255.255 broadcast 0.0.0.0
inet6fe80::4001:aff:fe80:11 prefixlen 64 scopeid 0x20<link>
ether42:01:0a:80:00:11 txqueuelen 1000 (Ethernet)
RXpackets 2064 bytes 5260296 (5.2 MB)
RX errors0 dropped 0 overruns 0 frame 0
TXpackets 2001 bytes 183154 (183.1 KB)
TX errors0 dropped 0 overruns 0 carrier 0 collisions 0
soot@master-node:~/dpdk/dpdk-stable-18.11.2#./usertools/dpdk-devbind.py --statu
Network devices using kernel driver
===================================
0000:00:04.0 'Virtio network device1000' if=ens4 drv=virtio-pci unused= *Active*
No 'Crypto' devices detected
============================
No 'Eventdev' devices detected
==============================
No 'Mempool' devices detected
=============================
No 'Compress' devices detected
==============================
===================================END
==================================================
On Thursday, October 10, 2019, 06:47:01 AM GMT+5:30, Stephen Hemminger
<[email protected]> wrote:
On Tue, 8 Oct 2019 07:59:12 +0000 (UTC)
sachin gupta <[email protected]> wrote:
> Hi All,When i run the KNI sample application on Google Cloud, i get the
> following error
>
>
>
> EAL: Detected 2 lcore(s)EAL: Detected 1 NUMA nodesEAL: Multi-process socket
> /var/run/dpdk/rte/mp_socketEAL: No free hugepages reported in
> hugepages-1048576kBEAL: Probing VFIO support...Oct 8 07:35:17 master-node
> kni[19444]: EAL: Probing VFIO support...EAL: PCI device 0000:00:04.0 on NUMA
> socket -1EAL: Invalid NUMA socket, default to 0EAL: probe driver: 1af4:1000
> net_virtioOct 8 07:35:17 master-node kni[19444]: EAL: PCI device 0000:00:04.0
> on NUMA socket -1Oct 8 07:35:17 master-node kni[19444]: EAL: Invalid NUMA
> socket, default to 0Oct 8 07:35:17 master-node kni[19444]: EAL: probe driver:
> 1af4:1000 net_virtioEAL: Error - exiting with code: 1 Cause: No supported
> Ethernet device foundOct 8 07:35:17 master-node kni[19444]: EAL: Error -
> exiting with code: 1#012 Cause:Oct 8 07:35:17 master-node kni[19444]: No
> supported Ethernet device found
>
> I have set 128 hugepages each of size 128KB
> AnonHugePages: 0 kBShmemHugePages: 0 kBHugePages_Total:
> 128HugePages_Free: 114HugePages_Rsvd: 0HugePages_Surp:
> 0Hugepagesize: 2048 kB
>
>
>
> ens4: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1460 inet
> 10.128.0.17 netmask 255.255.255.255 broadcast 0.0.0.0 inet6
> fe80::4001:aff:fe80:11 prefixlen 64 scopeid 0x20<link> ether
> 42:01:0a:80:00:11 txqueuelen 1000 (Ethernet) RX packets 2064 bytes
> 5260296 (5.2 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX
> packets 2001 bytes 183154 (183.1 KB) TX errors 0 dropped 0 overruns
> 0 carrier 0 collisions 0
>
>
> soot@master-node:~/dpdk/dpdk-stable-18.11.2# ./usertools/dpdk-devbind.py
> --statu
> Network devices using kernel
> driver===================================0000:00:04.0 'Virtio network device
> 1000' if=ens4 drv=virtio-pci unused= *Active*
> No 'Crypto' devices detected============================
> No 'Eventdev' devices detected==============================
> No 'Mempool' devices detected=============================
> No 'Compress' devices detected==============================
>
> ThanksSachin
Hard to tell on this email, bad line wrapping (and which ended up in spam
folder).
But the startup output indicates you did not configure huge pages.
Did you use dpdk-setup.sh ?
With virtio you need to unbind the device from the kernel and bind it to dpdk
with dpdk-devbind or manually. In a cloud that means you need to have two
Ethernet devices, one for DPDK and one for logging in SSH etc.
Also last time I checked Google Cloud had a custom version of virtio and don't
think virtio developers test wit that.
