Hi Ori, I managed to get the traffic flowing after setting the MAC address of the destination port on source machine and vice-versa. Command used in packetgen prompt is: set mac 0 <mac-address> Thanks, Sandeep
On Thu, Sep 8, 2016 at 2:57 AM, Ori Zakin <ori at drivenets.com> wrote: > Make sure the VF Mac/Vlan filters correspond to the packetgen config. > > Ori > > > On 8 Sep 2016, at 12:51 AM, Sandeep Rayapudi <rayapudisandeep at gmail.com> > wrote: > > Thanks Ori. > When I did the ip link up, packetgen comes up. > > Now the nics on these two hosts connected by cable. When I played traffic > on one container using packetgen, the traffic doesn't reach the other > container. > Any clues why? > > On Wed, Sep 7, 2016 at 7:38 AM, Ori Zakin <ori at drivenets.com> wrote: > >> Can you run ?ip link? on host? >> Check if the physical device is up. >> >> Ori >> > >> > Message: 1 >> > Date: Tue, 6 Sep 2016 14:09:04 -0400 >> > From: Sandeep Rayapudi <rayapudisandeep at gmail.com> >> > To: users at dpdk.org >> > Subject: [dpdk-users] PMD: eth_ixgbevf_dev_init(): VF Initialization >> > Failure: -15 >> > Message-ID: >> > <CAJU=zSW2A3u36H2O2Nhizc2ME1E-EHE9KvBPDHzqT3kXSY5TxQ at mail.g >> mail.com> >> > Content-Type: text/plain; charset=UTF-8 >> > >> > Hi all, when i tried to run pktgen/testpmd on the container with SR-IOV >> VF, >> > VF Init fails with error code -15. Any inputs please? >> > >> > Steps I followed are: >> > >> > 1. Create a Virtual Function on NIC >> > >> > a. Add boot option for the host: *iommu=pt intel_iommu=on* >> > >> > b. Without this option, we're unable to edit the file: >> > /sys/bus/pci/devices/0000:05:00.0/sriov_numvfs >> > >> > c. After reboot, echo *1* > sriov_numvfs >> > >> > d. Now, we're able to see *1 *Virtual Function in *lspci | grep -i >> > ethernet* output >> > >> > e. Now dpdk-devbind tool displays that the virtual function bound >> to >> > *ixgbevf* >> > >> > 2. Bind the VF NIC to vfio-pci >> > >> > 3. Create the mountpoint >> > >> > 4. Start the container with: >> > >> > a. docker run --privileged -itd -v */dev/vfio/vfio0:/dev/vfio/vfi >> o0* >> > -v /mnt/huge_c0/:/dev/hugepages/ -v >> > /sys/bus/pci/drivers:/sys/bus/pci/drivers -v >> > /sys/kernel/mm/hugepages:/sys/kernel/mm/hugepages -v >> > /sys/devices/system/node:/sys/devices/system/node -v /dev:/dev -v >> /usr:/usr >> > -v /lib:/lib >> > >> > 5. Start DPDK application >> > >> > ./app/app/x86_64-native-linuxapp-gcc/pktgen -c 0x1f -n 3 -- -P -m "2.0" >> > >> > >> > Copyright (c) <2010-2016>, Intel Corporation. All rights reserved. >> Powered >> > by Intel? DPDK >> > >> > EAL: Detected 28 lcore(s) >> > >> > EAL: No free hugepages reported in hugepages-1048576kB >> > >> > EAL: Probing VFIO support... >> > >> > EAL: VFIO support initialized >> > >> > PMD: bnxt_rte_pmd_init() called for (null) >> > >> > EAL: PCI device 0000:04:00.0 on NUMA socket 0 >> > >> > EAL: probe driver: 8086:10fb rte_ixgbe_pmd >> > >> > EAL: PCI device 0000:04:00.1 on NUMA socket 0 >> > >> > EAL: probe driver: 8086:10fb rte_ixgbe_pmd >> > >> > EAL: PCI device 0000:05:00.0 on NUMA socket 0 >> > >> > EAL: probe driver: 8086:10fb rte_ixgbe_pmd >> > >> > EAL: PCI device 0000:05:00.1 on NUMA socket 0 >> > >> > EAL: probe driver: 8086:10fb rte_ixgbe_pmd >> > >> > EAL: PCI device 0000:05:10.0 on NUMA socket 0 >> > >> > EAL: probe driver: 8086:10ed rte_ixgbevf_pmd >> > >> > EAL: using IOMMU type 1 (Type 1) >> > >> > PMD: eth_ixgbevf_dev_init(): VF Initialization Failure: -15 >> > >> > EAL: Error - exiting with code: 1 >> > >> > Cause: Requested device 0000:05:10.0 cannot be used >> > >> > Thanks, >> > Sandeep >> > > >
