From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 33242439A9 for ; Tue, 23 Jan 2024 17:32:12 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E57A8402B0; Tue, 23 Jan 2024 17:32:11 +0100 (CET) Received: from mail-pl1-f177.google.com (mail-pl1-f177.google.com [209.85.214.177]) by mails.dpdk.org (Postfix) with ESMTP id EE54D402A8 for ; Tue, 23 Jan 2024 17:32:10 +0100 (CET) Received: by mail-pl1-f177.google.com with SMTP id d9443c01a7336-1d51ba18e1bso40281505ad.0 for ; Tue, 23 Jan 2024 08:32:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1706027530; x=1706632330; darn=dpdk.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=z645QqtxL73m6LCtJYK0wR/Hk5zwOc3iFPALHijA7Eg=; b=Cgp9cN/jIIZFrQls3SA+nJzzImk+R/DD6ZcCxA8CL7w6Rvy/fK0F02NoEacRInCjcQ HaWs29OxjO6BVCaojtWjzsaMVf7UzMRsKUK5cfKH0u+JOkV8z0GMzIBcx7W4pEAoqSXG +X20VZzbz9x+fJD/3wmoG0BaUOCZrvMfrLsig7zMoby9zqI683I5zvoKi2f9E2l4LJ46 piyE900XbvC3EK9yPsRWVlRBDQdcedNpbTYihiHwtahy+Bp7JynpG5WtKnR8aptxMdI6 CVXmoOY67hSb0LEkBS7SrSdsuFRW/8dkUusUnbgLUIrewPTQ8LrCKtkHNuMmx/l7RmgR i+YA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706027530; x=1706632330; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=z645QqtxL73m6LCtJYK0wR/Hk5zwOc3iFPALHijA7Eg=; b=gAfRdQDX5OI4M3gtv6NTXPBGbcty4LFrwCnoaBZSyHYcVZ388tk27jr4SbKYYMEjbB wacCfE5kDn0TQ9dd1r+CcV80MHZKG2/E3ugxMz8gb+t1030+A7SwrbpWfRe6AcT12I4a BsT6rr/uP9yhj6eUTBfD4g+8qXMyNmP8kHwLyIu/4Yj6nqm2K0ijfrJLz5ShsyzxIwgM yhSTJ0IVas/XiWDpS1BV7Xmlesn/GDHHs6qw268zENWo+t4HVuB003+c9nxygun6be+w sZw4WZkrPp7VDLLYxzvjCKRkBCaNmH3WtWzp+qxmWqRuPkSKTATTIqUyMXsg7PxEtDEW O8Pg== X-Gm-Message-State: AOJu0YyMJSP8L6v/yzemZOtkxoEj0HYjJCiMulD28/TEKkUk22gOYTjp 2atUf6sQPLIgAwoNJn6Jdx95d/eA+8Ti2IRgHZ8e69wre5yCvqxTAz/hFlnkSX0= X-Google-Smtp-Source: AGHT+IEnPYgd5B7ot2zxQ8vWiSnEDga7ZiLdLL1CpRuPfy0fwKviaLJfm6Gz9+CdWMIvXQ9goWeWNg== X-Received: by 2002:a17:902:fc4f:b0:1d7:57bf:259 with SMTP id me15-20020a170902fc4f00b001d757bf0259mr3817631plb.121.1706027530045; Tue, 23 Jan 2024 08:32:10 -0800 (PST) Received: from hermes.local (204-195-123-141.wavecable.com. [204.195.123.141]) by smtp.gmail.com with ESMTPSA id m20-20020a170902f21400b001d74ca3a89asm3934221plc.293.2024.01.23.08.32.09 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 23 Jan 2024 08:32:09 -0800 (PST) Date: Tue, 23 Jan 2024 08:32:08 -0800 From: Stephen Hemminger To: Oleksandr Nahnybida Cc: users@dpdk.org Subject: Re: DPDK Netvsc - RNDIS reports VF but device not found, retrying Message-ID: <20240123083208.32900f39@hermes.local> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org On Tue, 23 Jan 2024 14:34:12 +0200 Oleksandr Nahnybida wrote: > Hello, > > I am trying to set up dpdk with netvsc as master pmd on Azure following > https://learn.microsoft.com/en-us/azure/virtual-network/setup-dpdk?tabs=ubuntu > and > https://doc.dpdk.org/guides-22.11/nics/netvsc.html > > but I have the following error messages > > EAL: VFIO support initialized > EAL: Probe PCI driver: mlx5_pci (15b3:1018) device: 8565:00:02.0 (socket 0) > mlx5_net: DV flow is not supported. > mlx5_common: Failed to allocate DevX UAR (BF/NC) > mlx5_common: Failed to allocate UAR. > mlx5_net: Failed to prepare Tx DevX UAR. > mlx5_net: probe of PCI device 8565:00:02.0 aborted after encountering an > error: Operation not permitted > mlx5_common: Failed to load driver mlx5_eth > EAL: Requested device 8565:00:02.0 cannot be used > EAL: Probe PCI driver: mlx5_pci (15b3:1018) device: d377:00:02.0 (socket 0) > mlx5_net: DV flow is not supported. > mlx5_common: Failed to allocate DevX UAR (BF/NC) > mlx5_common: Failed to allocate UAR. > mlx5_net: Failed to prepare Tx DevX UAR. > mlx5_net: probe of PCI device d377:00:02.0 aborted after encountering an > error: Operation not permitted > mlx5_common: Failed to load driver mlx5_eth > EAL: Requested device d377:00:02.0 cannot be used > EAL: Probe PCI driver: mlx5_pci (15b3:1018) device: f97e:00:02.0 (socket 0) > mlx5_net: DV flow is not supported. > mlx5_common: Failed to allocate DevX UAR (BF/NC) > mlx5_common: Failed to allocate UAR. > mlx5_net: Failed to prepare Tx DevX UAR. > mlx5_net: probe of PCI device f97e:00:02.0 aborted after encountering an > error: Operation not permitted > mlx5_common: Failed to load driver mlx5_eth > EAL: Requested device f97e:00:02.0 cannot be used > EAL: Bus (pci) probe failed. > hn_vf_attach(): Couldn't find port for VF > hn_vf_add(): RNDIS reports VF but device not found, retrying > hn_vf_attach(): Couldn't find port for VF > hn_vf_add(): RNDIS reports VF but device not found, retrying > and so on in a loop > > Also, with debug logs I see > > mlx5_common: DevX read access NIC register=0X9055 failed errno=22 status=0 > syndrome=0 > mlx5_common: DevX read access NIC register=0X9055 failed errno=22 status=0 > syndrome=0 > mlx5_common: DevX read access NIC register=0X9055 failed errno=22 status=0 > syndrome=0 > > > The DPDK version is 22.11, running on > Linux dpdk0 5.15.0-1053-azure #61~20.04.1-Ubuntu > VM type D8ls v5, accelerated networking is on for two ports > > driverctl -b vmbus list-devices > > 000d3a1c-e0df-000d-3a1c-e0df000d3a1c hv_netvsc > 000d3a1e-4573-000d-3a1e-4573000d3a1e uio_hv_generic [*] > 000d3a1e-47da-000d-3a1e-47da000d3a1e uio_hv_generic [*] > > > Any, ideas what I might be doing wrong? I see the same behavior with > testpmd and my app. Looks like a mlx5 driver issue, which kernel driver are you using? The netvsc code sees a VF but can't use it because of the mlx5 errors.