From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 6DB96A046B for ; Tue, 28 May 2019 20:09:26 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id ADDEE2E8F; Tue, 28 May 2019 20:09:25 +0200 (CEST) Received: from mail-pf1-f195.google.com (mail-pf1-f195.google.com [209.85.210.195]) by dpdk.org (Postfix) with ESMTP id 8EB99A49 for ; Tue, 28 May 2019 20:09:24 +0200 (CEST) Received: by mail-pf1-f195.google.com with SMTP id u22so4662510pfm.3 for ; Tue, 28 May 2019 11:09:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dUaGXiWiCfSl9MA5Zm8MghmeBpMGnsHh6MpXZrBS8IY=; b=tLR/vjf6oszUmUeXg2SavY/1oiw0IGfmSOb/6vHR/3M7bsDgKOGvH+iut85R2aT5gi aXmbDlTeXadokVtnFfQgIrbAEzPIT1shnCvjBCuDUdBtbPuwkzOBhXewtoH4SZQ7KNqU qONsU/68oKKt6unAkGdYh0LjkRuYM9PnzGPHj0ZA1Lo83jP7m2CKxrjq9uTBrphVu1Fu IoB/sQph9hbSNmcM90rXzV+IKFASZH46OTCBuP4xKGLZA0u6HVRv5YJKxMaG+TZcZrvH MduTTusfsi+80TsMsAmPUXu0tq320y3q/h/fojKJzb9JzRMI1fIFAlzllGwrfcJhPEh0 3OIg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=dUaGXiWiCfSl9MA5Zm8MghmeBpMGnsHh6MpXZrBS8IY=; b=uNUFnHzDjkMreBFqkkRLK944sE6ZxIyYQ+l4uq7EHUcyuCUY5ZXVCJZk0WtRouGN6Z 1/5WSzAvtwKj0QVBMaWm7u8LIudMBVE0Bs4ZSwEDAGwUrZRD1MRIFlQN/6FlYxo8c063 pZWNRe+MDKp1HYF9PDoObYkrQCFyN43KZf49U4QGAtEQvktzdtWnW0d6z0PmWNffwNK0 ZWvWx1JH2r6ZlFEy2R1/9xTU/VFgoimuRTuM1z0GrAgKpQsbNf0Pvjr7MZgQxNsZIn1e bX6m7F8UhNiqGFYogTMGpHomHSv3ZF4w7pwAQ29Q5aZXDMJWNPheGz7vVpdjdqjFbdrw KKIQ== X-Gm-Message-State: APjAAAUyV5DVuqAkitdl+ItY1L9OBvmxTH2Xlahvf10KKTwL8uKv4j5/ JQCr5NrRI2poqtfIdJt9YLlBXNKUhw2PzMC66vClzkGX X-Google-Smtp-Source: APXvYqy2ZlTmBhlcWjl36bzz+3EQX4RluX+WEDYpgC70mwP7Du08PwRc2QfRfLnia1oephKAL7HDHi9DIQtympv21iQ= X-Received: by 2002:a63:c02:: with SMTP id b2mr118033385pgl.5.1559066963778; Tue, 28 May 2019 11:09:23 -0700 (PDT) MIME-Version: 1.0 References: <20190527075203.5a08c48d@hermes.lan> <20190528070214.0920c905@hermes.lan> In-Reply-To: <20190528070214.0920c905@hermes.lan> From: Sara Gittlin Date: Tue, 28 May 2019 21:09:12 +0300 Message-ID: To: Stephen Hemminger Cc: users@dpdk.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] pktgen - !PANIC!: *** Did not find any ports to use *** X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Sender: "users" Thank you Stephen and Keith trying your suggestions .. Stephen - regarding your PS - I'm really sorry - I did not mean to prioritise myself - just pasted the error msg. I'll remember your recommendation .. Regards -Sara On Tue, May 28, 2019 at 5:02 PM Stephen Hemminger < stephen@networkplumber.org> wrote: > On Tue, 28 May 2019 08:33:35 +0300 > Sara Gittlin wrote: > > > Hello > > According the dpdk release notes - my NIC - Onboard NIC: *Intel(R) > > X552*/X557-AT > > (2x10G) was tested > > > > Tested Platforms > > > > ---------------- > > > > > > #. SuperMicro 1U > > > > > > - BIOS: 1.0c > > > > - Processor: Intel(R) Atom(TM) CPU C2758 @ 2.40GHz > > > > > > #. SuperMicro 1U > > > > > > - BIOS: 1.0a > > > > - Processor: Intel(R) Xeon(R) CPU D-1540 @ 2.00GHz > > > > *- Onboard NIC: Intel(R) X552/X557-AT (2x10G)* > > > > Thank you > > > > -Sara > > > > On Mon, May 27, 2019 at 5:56 PM Sara Gittlin > wrote: > > > > > Thank you Stephen > > > i can run pktgen on the host with same 2 VF's > > > Regards > > > -Sara > > > > > > > > > On Mon, May 27, 2019 at 5:52 PM Stephen Hemminger < > > > stephen@networkplumber.org> wrote: > > > > > >> On Mon, 27 May 2019 17:44:17 +0300 > > >> Sara Gittlin wrote: > > >> > > >> > Hello , > > >> > I'm running pktgen on a ubuntu-16.0p4 VM w 3 CPU's, > > >> > I added 2 SRIOV VFs devices to the VM - and i can see them w > lspci or > > >> > dpdk-devbind --status > > >> > 00:08.0 Ethernet controller: Intel Corporation Ethernet Connection > X552 > > >> > Virtual Function > > >> > 00:09.0 Ethernet controller: Intel Corporation Ethernet Connection > X552 > > >> > Virtual Function > > >> > > >> Most likely these devices are missing/not supported by DPDK driver. > > >> Look at the numeric id's (lspci -n) and compare them with the list > > >> of pci ids in the driver source. > > >> > > >> In the past with Intel devices it also helped to look at the Linux > > >> kernel driver. Sometimes the missing id's were there and some small > > >> changes to the MAC code was necessary to get them to work. > > Walking backwards from PCI to device. > > 1. The PCI id table for lspci is in /usr/share/misc/pci.ids > The entry for X552 is: > 15a9 X552 Virtual Function > Therefore the PCI vendor:device is 8086:15a9 > > 4. On Linux this device is under ixgbevf as > > #define IXGBE_DEV_ID_X550EM_X_VF_HV 0x15A9 > > static const struct pci_device_id ixgbevf_pci_tbl[] = { > {PCI_VDEVICE(INTEL, IXGBE_DEV_ID_82599_VF), board_82599_vf }, > {PCI_VDEVICE(INTEL, IXGBE_DEV_ID_82599_VF_HV), board_82599_vf_hv }, > {PCI_VDEVICE(INTEL, IXGBE_DEV_ID_X540_VF), board_X540_vf }, > {PCI_VDEVICE(INTEL, IXGBE_DEV_ID_X540_VF_HV), board_X540_vf_hv }, > {PCI_VDEVICE(INTEL, IXGBE_DEV_ID_X550_VF), board_X550_vf }, > {PCI_VDEVICE(INTEL, IXGBE_DEV_ID_X550_VF_HV), board_X550_vf_hv }, > {PCI_VDEVICE(INTEL, IXGBE_DEV_ID_X550EM_X_VF), board_X550EM_x_vf } > {PCI_VDEVICE(INTEL, IXGBE_DEV_ID_X550EM_A_VF), board_x550em_a_vf }, > /* required last entry */ > {0, } > }; > > Conclusion: you are using X552 on Hyper-V. > > 5. In DPDK, similar table is ixgbe_ethdev. > > /* > * The set of PCI devices this driver supports (for 82599 VF) > */ > static const struct rte_pci_id pci_id_ixgbevf_map[] = { > { RTE_PCI_DEVICE(IXGBE_INTEL_VENDOR_ID, IXGBE_DEV_ID_82599_VF) }, > { RTE_PCI_DEVICE(IXGBE_INTEL_VENDOR_ID, IXGBE_DEV_ID_82599_VF_HV) > }, > { RTE_PCI_DEVICE(IXGBE_INTEL_VENDOR_ID, IXGBE_DEV_ID_X540_VF) }, > { RTE_PCI_DEVICE(IXGBE_INTEL_VENDOR_ID, IXGBE_DEV_ID_X540_VF_HV) }, > { RTE_PCI_DEVICE(IXGBE_INTEL_VENDOR_ID, IXGBE_DEV_ID_X550_VF_HV) }, > { RTE_PCI_DEVICE(IXGBE_INTEL_VENDOR_ID, IXGBE_DEV_ID_X550_VF) }, > { RTE_PCI_DEVICE(IXGBE_INTEL_VENDOR_ID, IXGBE_DEV_ID_X550EM_A_VF) > }, > { RTE_PCI_DEVICE(IXGBE_INTEL_VENDOR_ID, > IXGBE_DEV_ID_X550EM_A_VF_HV) }, > { RTE_PCI_DEVICE(IXGBE_INTEL_VENDOR_ID, IXGBE_DEV_ID_X550EM_X_VF) > }, > { RTE_PCI_DEVICE(IXGBE_INTEL_VENDOR_ID, > IXGBE_DEV_ID_X550EM_X_VF_HV) }, > { .vendor_id = 0, /* sentinel */ }, > }; > > So the device is supported... > > > A different possibility is that since you are running on Hyper-V (at least > according to the device ids) is that vdev_netvsc device is trying to setup > tap > failsafe and messing the port numbers around. > Try disabling it by setting this in the config. > > CONFIG_RTE_LIBRTE_VDEV_NETVSC_PMD=n > > > > > PS: Top posting is not preferred on open source mailing lists. >