- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Follow up of this thread, was advised to submit a new question.
While upgrading a number of VMs using Linux kernel 6.12+, we've noticed that an old iavf bug has regressed. When attempting to bring the interface up with any MTU (even if not set; defaulting to 1500) the following error is seen: "PF returned error -5 (IAVF_ERR_PARAM)".
The E810-C is running on a Supermicro X12-SPi board with NVM 4.91. Earlier NVM versions also produce the same issue (i.e. 4.80 or 4.90). ESXi icen driver version is 2.3.3.0, latest at time of post.
The below error can be seen when attempting to activate the NIC:
Please see the attached for the SSU taken from the VM. Apologies for the delay, needed the ability to assign the SR-IOV and access the console since remote SSH is not possible while the issue is ongoing.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Shane5,
Greetings from Intel!
We appreciate you reaching out to us regarding the reported issue. As per the supported VF driver for guest operating system are given in the below article:
Guest Operating System Support for SR-IOV in VMware vSphere* 6.5,...
To assist you more effectively and provide an accurate solution, we kindly request the following details:
1- Current running ESXi build number?
2- Any configured module parameters specifics?
Looking forward to your update on this.
Best Regards,
Azhari_Intel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
1 - Currently running ESXi 8.0 Update 3h (installed NIC under 3e, nothing tested prior to this update).
2 - Only parameter set is trust_all_vfs=1,1,1,1,1,1,1,1 as the NIC is running in 2x4x10Gbe mode (cannot check other modes at this time).
Matrix seen on 630155_Intel Ethernet Controller E810 Feature Support Matrix_rev4_8.pdf shows compatibility. While reviewing commits by Intel to the Linux kernel, the issue may have surfaced as part of the migration to the "Intel Ethernet common library" (libie).
When attempting SR-IOV on Linux VMs using kernels before libie migration but after the 2022 commits that addressed the "PF returned error -5 (IAVF_ERR_PARAM)", the functionality works fine.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Shane5,
Greetings for the day!
Thank you for sharing the details. We kindly request you to allow us some time to review the information and provide you with an update.
We appreciate your understanding!
Best regards,
Poojitha N
Intel Customer Support Technician
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page