From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1845] DPDK 20 guest with X710 SR-IOV: VF MAC changes randomly on reboot (host i40e 2.22.18)
Date: Mon, 01 Dec 2025 05:59:46 +0000 [thread overview]
Message-ID: <bug-1845-3@http.bugs.dpdk.org/> (raw)
http://bugs.dpdk.org/show_bug.cgi?id=1845
Bug ID: 1845
Summary: DPDK 20 guest with X710 SR-IOV: VF MAC changes
randomly on reboot (host i40e 2.22.18)
Product: DPDK
Version: 20.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: gownivalla.susmitha@wipro.com
Target Milestone: ---
Hello DPDK Community,
We are seeing an intermittent issue where the VF MAC address on the host (PF
side) changes unexpectedly after VM reboot when using Intel X710 NICs.
Environment
NIC: Intel X710 (SR-IOV)
Host driver (problematic): i40e 2.22.18
Host firmware/NVM tested: 6.00 and 9.10
Host driver (working): i40e 2.14.x
Working firmware/NVM: 7.10
Hypervisor: OpenStack (Neutron sets MAC during orchestration)
MAC is explicitly assigned in orchestration YAML
Issue
The assigned VF MAC is correctly programmed at initial VM creation.
However, on some VM reboots (not every time), the MAC on the host VF changes to
a random, different MAC.
Expected
VF MAC programmed by orchestration should remain persistent across reboots.
Observed Only With
i40e 2.22.18
Firmware 6.00 and 9.10
Not Observed With
i40e 2.14.13
Firmware 7.10
Request/Clarification required:
Is this a known issue in i40e 2.22.18 or DPDK 20.11?
Any recommended fix, patch, or firmware/driver combination?
Any debug flags or traces we can enable to capture VF MAC programming failures?
Please let me know if additional logs are needed.
Thanks,
Susmitha
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2025-12-01 5:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-1845-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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).