some additional information: 1.$DPDK_DIR/tools/dpdk-devbind.py --status
Network devices using DPDK-compatible driver ============================================ 0000:01:00.0 '82599EB 10-Gigabit SFI/SFP+ Network Connection' drv=vfio-pci unused= Network devices using kernel driver =================================== 0000:01:00.1 '82599EB 10-Gigabit SFI/SFP+ Network Connection' if=eth1 drv=ixgbe unused=vfio-pci 0000:06:00.0 'I350 Gigabit Network Connection' if=eth2 drv=igb unused=vfio-pci 0000:06:00.1 'I350 Gigabit Network Connection' if=eth3 drv=igb unused=vfio-pci Other network devices ===================== <none> 2.cat /etc/issue Debian GNU/Linux 7 \n \l 3. I did some debug on ovs-switchd, and it seemed that when do dpdk_init(), the function rte_eal_pci_map_device() return -1, so the whole vswtiched process exited. some deep debug shows that VFIO_PRESENT is not defined, but now my kernel version is: Linux 10-180-0-39 3.10.45-openstack-amd64, which is greater than 3.6.0 At 2016-09-27 21:36:27, "Aaron Conole" <acon...@redhat.com> wrote: >ychen <ychen103...@163.com> writes: > >> hi, >> I follow the doc "INSTALLDPDK.md" to build ovs dpdk envrioment, but failed >> to start ovs-vswitchd >> here is my configurations: >> 1. kernel: 3.10.45-openstack-amd64 #1 SMP Tue Jul 1 01:52:20 UTC 2014 x86_64 >> GNU/Linux >> 2. NIC: >> 01:00.0 Ethernet controller [0200]: Intel Corporation 82599EB 10-Gigabit >> SFI/SFP+ Network Connection [8086:10fb] (rev 01) >> 01:00.1 Ethernet controller [0200]: Intel Corporation 82599EB 10-Gigabit >> SFI/SFP+ Network Connection [8086:10fb] (rev 01) >> 06:00.0 Ethernet controller [0200]: Intel Corporation I350 Gigabit Network >> Connection [8086:1521] (rev 01) >> 06:00.1 Ethernet controller [0200]: Intel Corporation I350 Gigabit Network >> Connection [8086:1521] (rev 01) > >Can you also include the output of dpdk_nic_bind? It is helpful to see >which driver you are using. What linux distribution is this on? > >> 3. IOMMU support >> /sys/kernel/iommu_groups/12/devices/0000:01:00.0 >> /sys/kernel/iommu_groups/12/devices/0000:01:00.1 >> /sys/kernel/iommu_groups/9/devices/0000:06:00.0 >> /sys/kernel/iommu_groups/9/devices/0000:06:00.1 >> BOOT_IMAGE=/boot/vmlinuz-3.10.45-openstack-amd64 >> root=UUID=5cc1592c-91b4-485c-96cc-4528837dbeef ro default_hugepagesz=1G >> hugepagesz=1G hugepages=4 iommu=pt intel_iommu=on isolcpus=0-12 >> intel_idle.max_cstate=0 idle=poll quiet cgroup_enable=memory crashkernel=512M >> 4. hugepage support >> AnonHugePages: 229376 kB >> HugePages_Total: 4 >> HugePages_Free: 2 >> HugePages_Rsvd: 0 >> HugePages_Surp: 0 >> Hugepagesize: 1048576 kB >> 5.cpu information >> Architecture: x86_64 >> CPU op-mode(s): 32-bit, 64-bit >> Byte Order: Little Endian >> CPU(s): 48 >> On-line CPU(s) list: 0-47 >> Thread(s) per core: 2 >> Core(s) per socket: 12 >> Socket(s): 2 >> NUMA node(s): 2 >> Vendor ID: GenuineIntel >> CPU family: 6 >> Model: 63 >> Stepping: 2 >> CPU MHz: 2599.988 >> BogoMIPS: 4601.07 >> Virtualization: VT-x >> L1d cache: 32K >> L1i cache: 32K >> L2 cache: 256K >> L3 cache: 30720K >> NUMA node0 CPU(s): >> 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38,40,42,44,46 >> NUMA node1 CPU(s): >> 1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39,41,43,45,47 >> >> >> 6.dpdk parameters in ovs >> datapath_types : [netdev, system] >> db_version : [] >> external_ids : {} >> iface_types : [dpdk, dpdkr, dpdkvhostuser, dpdkvhostuserclient, >> geneve, gre, internal, ipsec_gre, lisp, patch, stt, system, tap, vxlan] >> manager_options : [] >> next_cfg : 2 >> other_config : {dpdk-init="true", dpdk-lcore-mask="0xf", >> dpdk-socket-mem="1024,1024", pmd-cpu-mask="0x3"} >> 7. error logs when start ovs-vswtichd >> 2016-09-27T07:15:27Z|00001|vlog|INFO|opened log file >> /var/log/openvswitch/ovs-vswitchd.log >> 2016-09-27T07:15:27Z|00002|ovs_numa|INFO|Discovered 24 CPU cores on NUMA >> node 0 >> 2016-09-27T07:15:27Z|00003|ovs_numa|INFO|Discovered 24 CPU cores on NUMA >> node 1 >> 2016-09-27T07:15:27Z|00004|ovs_numa|INFO|Discovered 2 NUMA nodes and 48 CPU >> cores >> 2016-09-27T07:15:27Z|00005|reconnect|INFO|unix:/var/run/openvswitch/db.sock: >> connecting... >> 2016-09-27T07:15:27Z|00006|reconnect|INFO|unix:/var/run/openvswitch/db.sock: >> connected >> 2016-09-27T07:15:27Z|00007|dpdk|INFO|DPDK Enabled, initializing >> 2016-09-27T07:15:27Z|00008|dpdk|INFO|No vhost-sock-dir provided - defaulting >> to /var/run/openvswitch >> 2016-09-27T07:15:27Z|00009|dpdk|INFO|EAL ARGS: ovs-vswitchd -c 0xf >> --socket-mem 1024,1024 >> EAL: Detected 48 lcore(s) >> PMD: bnxt_rte_pmd_init() called for (null) >> EAL: PCI device 0000:01:00.0 on NUMA socket 0 >> EAL: probe driver: 8086:10fb rte_ixgbe_pmd >> EAL: Error - exiting with code: 1 >> Cause: Requested device 0000:01:00.0 cannot be used > >This can mean that the device is not properly bound, bound to an >unsupported driver, or even a possible SELinux issue. > >> 8. version information >> Open vSwitch 2.6.0 >> dpdk: 16.07 _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev