From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id E85D1A052F for ; Sun, 26 Jan 2020 21:53:40 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 3C5AD49E0; Sun, 26 Jan 2020 21:53:40 +0100 (CET) Received: from mail-qv1-f41.google.com (mail-qv1-f41.google.com [209.85.219.41]) by dpdk.org (Postfix) with ESMTP id 8F35F2A62 for ; Thu, 23 Jan 2020 20:25:18 +0100 (CET) Received: by mail-qv1-f41.google.com with SMTP id x1so2032897qvr.8 for ; Thu, 23 Jan 2020 11:25:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=EqcdbxmjUuobFnnlH0SGFlbzO7UD18/PcbeeNHBql2I=; b=VpWDq42OCMTzLaz7EeHKl39m0jyp8hlS3ggxWPGqEDGJpvtZyEP++PQK3uV6a78rcI u7+PT/VToLs2bzWe2ce4+xvTaCFmmed632a56eqCiUzaVlpq1LuhVl07LuxmehfrqQBo Z1HvPjAuqTRsICMoYfcvp89XdlkXQBCPpjbEEPXWWjqVoem7+D3rgOu/DUMioXLpqH3G f3SGwzVSCSswiLnamxHXvhZFaHJ+UL+UDy+uBtLi52qcIF1vY1Ifh+JQbPmG8F1NAyxE TOfXxpBadKIzFzZ2iONALPgjkIOgrMcBHp+ThLHWw2hC7soKUaNFhu721eSx0LCIbpw3 MWqQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=EqcdbxmjUuobFnnlH0SGFlbzO7UD18/PcbeeNHBql2I=; b=KJ9NWk+KUdLSaX+44zddUI6itbWVPXkLIwpnJzVS8jwwkWJ0vGrynEZMz6TeBiml7u mlgc/jaxkblVCtXWtB8t5/hifomWBinQy8ejqB6dthGANhfnYqCASlOv00kfm73e+2+8 juSgvgLCEJ7qrT5mPe496JHbOg5Hgo3ziQKujukdzKVvtVDMm97L66AHUvBjGypj7RBz t7OO9vLexSpwvUGd9z49l+XZ5nLM5jfifY4DqTpFYtNEKCotTbhG3GFeaKDNPpMVCB6w oEoDXNklyMvyl2coOYlW84OLfkAoAO6X3xEUvbe+ntFwso6pf9VqcVU1Mq2+UsB6FiKT 9PeQ== X-Gm-Message-State: APjAAAVb6qkOnI7vhg79WOU+/KTgLJcZrS6M2v6cecXj2bDtk1dq0Dz1 cwt/xBBtWeXbJFwL4POd4vx2wjPcC8OI0/z3UTSilsUG X-Google-Smtp-Source: APXvYqwCvum4rLrL52/e499a4IjvMuP4Zr2cXhtE9AkLHVsKhvhsUy/Q2a2fed2vY44uQchkifRuO9yKfiLoHE7WR9o= X-Received: by 2002:a0c:eac7:: with SMTP id y7mr18081447qvp.86.1579807517480; Thu, 23 Jan 2020 11:25:17 -0800 (PST) MIME-Version: 1.0 From: Chris King Date: Thu, 23 Jan 2020 14:25:06 -0500 Message-ID: To: users@dpdk.org X-Mailman-Approved-At: Sun, 26 Jan 2020 21:53:39 +0100 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-users] VPP / DPDK issue with failsafe adapters 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" Hello, I have been reaching out for support for a VPP / DPDK issue on the fd.io forums here: https://lists.fd.io/g/vpp-dev/topic/interface_activation_problem/69987045 Since my problem may be DPDK related (unsure) or at the boundary between VPP and DPDK, I thought I would reach out here as well. Here is the latest context and any insights would be appreciated: Scenario: I am having difficulty getting my VPP interfaces activating properly. I am trying to use DPDK-enabled netvsc devices with VPP in Ubuntu 18.04 in Azure. Results: I have had a fair bit of success initializing DPDK directly on this same box on the same adapters. Both of the following testpmd commands work for me and the interfaces are attached to properly: sudo ./testpmd -l 0-3 -n 4 --vdev='net_failsafe0,dev(0002:00:02.0)' --vdev='net_failsafe1,dev(0003:00:02.0)' -b 0001:00:02.0 -- -i sudo ./testpmd -l 0-3 -n 4 --vdev='net_vdev_netvsc0,iface=eth1' --vdev='net_vdev_netvsc1,iface=eth2' -b 0001:00:02.0 -- -i Now, my DPDK devices are configured like this in the VPP config: dev 0002:00:02.0 vdev net_vdev_netvsc0,iface=eth1 dev 0003:00:02.0 vdev net_vdev_netvsc1,iface=eth2 And when I try to start VPP I see the following EAL parameters and failure to attach to the devices: 2020/01/23 19:02:45:346 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/23 19:02:45:570 warn dpdk unsupported rx offloads requested on port 0: jumbo-frame 2020/01/23 19:02:45:572 warn dpdk unsupported rx offloads requested on port 2: jumbo-frame 2020/01/23 19:02:45:574 notice dpdk EAL: Detected 4 lcore(s) 2020/01/23 19:02:45:574 notice dpdk EAL: Detected 1 NUMA nodes 2020/01/23 19:02:45:574 notice dpdk EAL: No available hugepages reported in hugepages-1048576kB 2020/01/23 19:02:45:574 notice dpdk EAL: No free hugepages reported in hugepages-1048576kB 2020/01/23 19:02:45:574 notice dpdk EAL: No available hugepages reported in hugepages-1048576kB 2020/01/23 19:02:45:574 notice dpdk EAL: Probing VFIO support... 2020/01/23 19:02:45:574 notice dpdk EAL: WARNING! Base virtual address hint (0xa80001000 != 0x7f0ac0000000) not respected! 2020/01/23 19:02:45:574 notice dpdk EAL: This may cause issues with mapping memory into secondary processes 2020/01/23 19:02:45:574 notice dpdk EAL: WARNING! Base virtual address hint (0xc00002000 != 0x7f0280000000) not respected! 2020/01/23 19:02:45:574 notice dpdk EAL: This may cause issues with mapping memory into secondary processes 2020/01/23 19:02:45:574 notice dpdk EAL: WARNING! Base virtual address hint (0xd80003000 != 0x7efa40000000) not respected! 2020/01/23 19:02:45:574 notice dpdk EAL: This may cause issues with mapping memory into secondary processes 2020/01/23 19:02:45:574 notice dpdk EAL: WARNING! Base virtual address hint (0xdc0a64000 != 0x7ef63fe00000) not respected! 2020/01/23 19:02:45:574 notice dpdk EAL: This may cause issues with mapping memory into secondary processes 2020/01/23 19:02:45:574 notice dpdk EAL: WARNING! Base virtual address hint (0xdc16c5000 != 0x7ef23fc00000) not respected! 2020/01/23 19:02:45:574 notice dpdk EAL: This may cause issues with mapping memory into secondary processes 2020/01/23 19:02:45:574 notice dpdk EAL: WARNING! Base virtual address hint (0xdc2326000 != 0x7eee3fa00000) not respected! 2020/01/23 19:02:45:574 notice dpdk EAL: This may cause issues with mapping memory into secondary processes 2020/01/23 19:02:45:574 notice dpdk EAL: WARNING! Base virtual address hint (0xdc2f87000 != 0x7eea3f800000) not respected! 2020/01/23 19:02:45:574 notice dpdk EAL: This may cause issues with mapping memory into secondary processes 2020/01/23 19:02:45:574 notice dpdk EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable clock cycles ! 2020/01/23 19:02:45:574 notice dpdk net_vdev_netvsc: probably using routed NetVSC interface "eth1" (index 3) 2020/01/23 19:02:45:574 notice dpdk EAL: Driver cannot attach the device (0002:00:02.0) 2020/01/23 19:02:45:574 notice dpdk EAL: Failed to attach device on primary process 2020/01/23 19:02:45:574 notice dpdk net_failsafe: sub_device 0 probe failed (No such file or directory) 2020/01/23 19:02:45:574 notice dpdk tun_alloc(): Rx trigger disabled: Device or resource busy 2020/01/23 19:02:45:574 notice dpdk net_vdev_netvsc: probably using routed NetVSC interface "eth2" (index 4) 2020/01/23 19:02:45:574 notice dpdk EAL: Driver cannot attach the device (0003:00:02.0) 2020/01/23 19:02:45:574 notice dpdk EAL: Failed to attach device on primary process 2020/01/23 19:02:45:574 notice dpdk net_failsafe: sub_device 0 probe failed (File exists) 2020/01/23 19:02:45:574 notice dpdk tun_alloc(): Rx trigger disabled: Device or resource busy 2020/01/23 19:02:45:574 notice dpdk EAL: VFIO support not initialized 2020/01/23 19:02:45:574 notice dpdk EAL: Couldn't map new region for DMA 2020/01/23 19:02:45:574 notice dpdk tun_alloc(): Rx trigger disabled: Device or resource busy 2020/01/23 19:02:45:574 notice dpdk tun_alloc(): Rx trigger disabled: Device or resource busy 2020/01/23 19:02:47:533 notice dpdk EAL: Driver cannot attach the device (0002:00:02.0) 2020/01/23 19:02:47:533 notice dpdk EAL: Failed to attach device on primary process 2020/01/23 19:02:47:533 notice dpdk net_failsafe: sub_device 0 probe failed (No such file or directory) Does anyone know if there something I can do in the VPP startup.conf to get DPDK devices to initialize correctly? Thanks, Chris