From: Stephen Hemminger <stephen@networkplumber.org>
To: Dattu Gundu <dattu.gundu@oracle.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: qdisc errors on Azure VM (TAP Config)
Date: Thu, 6 Oct 2022 09:31:30 -0700 [thread overview]
Message-ID: <20221006093130.544efb26@hermes.local> (raw)
In-Reply-To: <PH0PR10MB443736423182D0C8576F337B905C9@PH0PR10MB4437.namprd10.prod.outlook.com>
On Thu, 6 Oct 2022 06:08:59 +0000
Dattu Gundu <dattu.gundu@oracle.com> wrote:
> Hi,
>
> I am observing the below errors during the bootup of Azure VM.
>
> I understand these errors started popping from DPDK 20.11.1 due to extended ack support was added in Linux version 4.17
> And used for diagnosing the TAP config in kernel.
>
> Is it because we are trying to delete the qdisc before they are created ?
> And looks like the failure is per queue.
>
> Am I missing any packages ?
>
> How to avoid these errors ?
> If they are not serious, is there a way to suppress them ?
>
> net_vdev_netvsc: probably using routed NetVSC interface "s0p0" (index 7)
> tap_nl_dump_ext_ack(): Cannot delete qdisc with handle of zero
> tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
> tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
> tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
> tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
> tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
> tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
> tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
> tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
> net_vdev_netvsc: probably using routed NetVSC interface "s1p0" (index 8)
> tap_nl_dump_ext_ack(): Cannot delete qdisc with handle of zero
> tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
> tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
> tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
> tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
> tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
> tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
> tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
> tap_nl_dump_ext_ack(): Failed to find qdisc with specified classid
>
> Currently using below kernel:
> 5.4.17
> x86_64
> GNU/Linux
> #3 SMP PREEMPT Thu Aug 18 05:23:39 UTC 2022
>
> Thanks,
> Raghava Dattu.
If possible use netvsc PMD and not the older vdev_netvsc/failsafe/tap stuff.
Are you sure your kernel has all the necessary qdisc to run the failsafe/tap
device. It needs to have flower, mirred, mqprio, etc.
next prev parent reply other threads:[~2022-10-06 16:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 6:08 Dattu Gundu
2022-10-06 16:31 ` Stephen Hemminger [this message]
2022-10-10 8:05 ` [External] : " Dattu Gundu
2022-10-10 14:56 ` Stephen Hemminger
2022-10-12 11:14 ` Dattu Gundu
2022-10-12 17:11 ` Stephen Hemminger
2022-10-17 9:13 ` Dattu Gundu
2022-10-17 15:01 ` Stephen Hemminger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221006093130.544efb26@hermes.local \
--to=stephen@networkplumber.org \
--cc=dattu.gundu@oracle.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).