** Summary changed:
- SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf)
+ iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Kinetic)
Importance: High
Assignee: Trent Lloyd (lathiat)
Status: Confirmed
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Kinetic)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => High
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Description changed:
+ BugLink: https://bugs.launchpad.net/bugs/1983656
+
+ [Impact]
+
Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b] get
no traffic flow and produce error messages in both the host and guest
during network configuration.
Environment: Ubuntu OpenStack Focal-Ussuri with OVN
Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE
Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy
Host Error Messages:
ice 0000:98:00.1: VF 7 failed opcode 6, retval: -5
Guest Error Messages:
iavf 0000:00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6
In the context of these errors "6" refers to the value of
VIRTCHNL_OP_CONFIG_VSI_QUEUES
It was found in these cases that the VM is able to successfully transmit
packets but never receives any and the RX packet drop counters for the
VF in "ip link" on the host increase equal to the RX packet count.
There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d
claiming to resolve this error in some cases. It is already included in
- the test kernel v5.15.0-41 and did not resolve the issue.
+ 5.15.0-41-generic and did not resolve the issue.
The following conditions are required to trigger the bug:
- A port VLAN must be assigned by the host
- The MTU must be set >1500 by the guest
- It appears that this ice/iavf driver is quite immature as many
- significant SR-IOV related fixes have landed in each of the recent
- kernel releases and we may need to consider pro-actively backporting
- more fixes.
+ There is no workaround, Intel E810 SR-IOV VFs with MTU >1500 cannot be
+ used without these patches.
- [ Impact ]
+ [Fix]
- Intel E810 (host: ice) SR-IOV VFs (guest: iavf) fail when a port VLAN is
- assigned by the host and the guest changes the MTU >1500. The guest iavf
- driver logs the following error and traffic flow stops:
- iavf 0000:00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6
+ iavf currently sets the maximum packet size to IAVF_MAX_RXBUFFER, but on
+ the previous ice driver, it was decremented by VLAN_HLEN to make some
+ space to fit the VLAN header. This doesn't happen on iavf, and we end up
+ trying to use a packet size larger than IAVF_MAX_RXBUFFER, causing the
+ IAVF_ERR_PARAM error.
- There is no workaround, Intel E810 SR-IOV VFs with MTU >1500 cannot be
- used without this patch.
+ The fix is to change the maximum packet size from IAVF_MAX_RXBUFFER to
+ max_mtu received from the PF via GET_VF_RESOURCES msg.
- [ Fix ]
+ Also pick up a necessary commit for i40e to announce the correct maximum
+ packet size by GET_VF_RESOURCES msg.
- During queue configuration, VF's max packet size was set to
- IAVF_MAX_RXBUFFER but on ice max frame size was smaller by VLAN_HLEN
- due to making some space for port VLAN as VF is not aware whether it's
- in a port VLAN. This mismatch in sizes caused ice to reject queue
- configuration with ERR_PARAM error. Proper max_mtu is sent from ice PF
- to VF with GET_VF_RESOURCES msg but VF does not look at this.
+ This has been fixed by the following commits:
- In iavf change max_frame from IAVF_MAX_RXBUFFER to max_mtu
- received from pf with GET_VF_RESOURCES msg to make vf's
- max_frame_size dependent from pf. Add check if received max_mtu is
- not in eligible range then set it to IAVF_MAX_RXBUFFER.
+ commit 399c98c4dc50b7eb7e9f24da7ffdda6f025676ef
+ Author: Michal Jaron <[email protected]>
+ Date: Tue Sep 13 15:38:35 2022 +0200
+ Subject: iavf: Fix set max MTU size with port VLAN and jumbo frames
+ Link:
https://github.com/torvalds/linux/commit/399c98c4dc50b7eb7e9f24da7ffdda6f025676ef
- [ Test Plan ]
+ commit 372539def2824c43b6afe2403045b140f65c5acc
+ Author: Michal Jaron <[email protected]>
+ Date: Tue Sep 13 15:38:36 2022 +0200
+ Subject: i40e: Fix VF set max MTU size
+ Link:
https://github.com/torvalds/linux/commit/372539def2824c43b6afe2403045b140f65c5acc
- 1. Create a focal VM and assign an Intel E810 (ice) SR-IOV VF with a port
- vlan
+ A test kernel is available in the following ppa:
+
+ https://launchpad.net/~arif-ali/+archive/ubuntu/sf00343742
+
+ If you install the test kernel to a compute host and VM, when you attach
+ a VF and set the MTU to 9000, it succeeds, and traffic can flow.
+
+ [Test Plan]
+
+ 1. Create a Focal VM and assign an Intel E810 (ice) SR-IOV VF with a
+ port vlan:
Openstack works, as does creating a VM directly with uvtool/libvirt.
- The syntax inside <interface> for the port VLAN is <vlan><tag
- id=‘998’/></vlan>
+ $ uvt-kvm create focal-test release=focal
- 2. Set an IP on the interface, set it’s link up and verify operation
+ Using the document to understand SRIOV basics in the link below
- sudo ip a a 192.168.1.7/24 dev enp7s0
- sudo ip link set up dev enp7s0
- ping 192.168.1.1
+
https://www.intel.com/content/www/us/en/developer/articles/technical/configure-
+ sr-iov-network-virtual-functions-in-linux-kvm.html
- 3. Set the MTU to 9000
+ The following command show all the bus info for all the network devices
- sudo ip link set mtu 9000 dev enp7s0
+ $ lshw -c network -businfo
- 4. Test if the interface still works and whether the error was observed:
- iavf 0000:07:00.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6
+ Choose one, as shown below
- [ Where problems could occur ]
+ pci@0000:17:01.4 ens2f0v4 network Ethernet Adaptive Virtual
+ Function
- The iavf driver is unified for multiple host drivers including ice and
- i40e.
+ We can then add the following into the XML definition via “virsh edit
+ focal-test”
- A companion patch for i40e was also submitted as it did not set the
- max_mtu although the ice driver already did. We should test the fixed iavf
- driver against both i40e (Intel E7xx) and ice (Intel E8xx) cards with and
- without that patch on the host kernel.
+ <interface type='hostdev' managed='yes'>
+ <source>
+ <address type='pci' domain='0x0000' bus='0x17' slot='0x01'
function='0x4'/>
+ </source>
+ <vlan>
+ <tag id='998'/>
+ </vlan>
+ </interface>
-
https://lore.kernel.org/netdev/[email protected]/
+ Then we stop and start the VM via "virsh shutdown focal-test" and then
+ "virsh start focal-test". We can then login to the VM using the command
+ below
- [ Other Info ]
+ $ uvt-kvm ssh focal-test
- Patch was developed by intel, has been accepted into v6.0-rc7 and already
- released into upstream stable v5.4.215, v5.15.71 and v5.19.12.
+ Once you have logged in, run the following ip parameters
- Early SRU is requested as the functionality is required now and there is
- no workaround.
+ $ sudo ip a a 192.168.1.7/24 dev enp7s0
+ $ sudo ip link set up dev enp7s0
+ $ sudo ip link set mtu 9000 dev enp7s0
+
+ Now check dmesg, and we will find the error
+
+ [ 61.529605] iavf 0000:07:00.0: PF returned error -5 (IAVF_ERR_PARAM)
+ to our request 6
+
+ Setting the IP and bringing the link up
+
+ [ 36.228877] iavf 0000:07:00.0 enp7s0: NIC Link is Up Speed is 25 Gbps Full
Duplex
+ [ 36.228887] IPv6: ADDRCONF(NETDEV_CHANGE): enp7s0: link becomes ready
+ [ 45.740100] crng init done
+ [ 45.740102] random: 7 urandom warning(s) missed due to ratelimiting
+
+ Then setting the MTU
+
+ [ 61.433706] iavf 0000:07:00.0: Received 16 queues, but can only have a max
of 4
+ [ 61.433707] iavf 0000:07:00.0: Fixing by reducing queues to 4
+ [ 61.529605] iavf 0000:07:00.0: PF returned error -5 (IAVF_ERR_PARAM) to
our request 6
+ [ 61.552890] iavf 0000:07:00.0 enp7s0: NIC Link is Up Speed is 25 Gbps Full
Duplex
+
+ There is a test kernel available in the following ppa:
+
+ https://launchpad.net/~arif-ali/+archive/ubuntu/sf00343742
+
+ If you install the test kernel, setting the MTU to 9000 works as
+ expected and traffic can flow.
+
+ [Where problems could occur]
+
+ We are changing how maximum MTU is calculated and applied to VFs in the
+ iavf and i40e drivers. Currently, any MTU over 1500 does not work at all
+ when a port VLAN is enabled, but if someone has somehow got their setup
+ to work, they may see a difference in MTU with these patches applied.
+
+ The iavf and i40e drivers are a popular driver, and if a regression were
+ to occur, initialisation and bringup of these network devices and VFs
+ might fail.
+
+ Most users currently using MTUs of 1500 are unlikely to see any
+ difference or be at risk of regression.
+
+ [Other Info]
+
+ Both patches were developed by intel, and have been accepted into
+ v6.0-rc7 and are already released into upstream stable v5.4.215,
+ v5.15.71 and v5.19.12. These patches are well tested by the community
+ and considered safe.
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1983656
[Impact]
Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b] get
no traffic flow and produce error messages in both the host and guest
during network configuration.
Environment: Ubuntu OpenStack Focal-Ussuri with OVN
Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE
Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy
Host Error Messages:
ice 0000:98:00.1: VF 7 failed opcode 6, retval: -5
Guest Error Messages:
iavf 0000:00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6
In the context of these errors "6" refers to the value of
VIRTCHNL_OP_CONFIG_VSI_QUEUES
It was found in these cases that the VM is able to successfully transmit
packets but never receives any and the RX packet drop counters for the
VF in "ip link" on the host increase equal to the RX packet count.
There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d
claiming to resolve this error in some cases. It is already included in
5.15.0-41-generic and did not resolve the issue.
The following conditions are required to trigger the bug:
- A port VLAN must be assigned by the host
- The MTU must be set >1500 by the guest
There is no workaround, Intel E810 SR-IOV VFs with MTU >1500 cannot be
used without these patches.
[Fix]
iavf currently sets the maximum packet size to IAVF_MAX_RXBUFFER, but on
the previous ice driver, it was decremented by VLAN_HLEN to make some
space to fit the VLAN header. This doesn't happen on iavf, and we end up
trying to use a packet size larger than IAVF_MAX_RXBUFFER, causing the
IAVF_ERR_PARAM error.
The fix is to change the maximum packet size from IAVF_MAX_RXBUFFER to
max_mtu received from the PF via GET_VF_RESOURCES msg.
Also pick up a necessary commit for i40e to announce the correct maximum
packet size by GET_VF_RESOURCES msg.
This has been fixed by the following commits:
commit 399c98c4dc50b7eb7e9f24da7ffdda6f025676ef
Author: Michal Jaron <[email protected]>
Date: Tue Sep 13 15:38:35 2022 +0200
Subject: iavf: Fix set max MTU size with port VLAN and jumbo frames
Link:
https://github.com/torvalds/linux/commit/399c98c4dc50b7eb7e9f24da7ffdda6f025676ef
commit 372539def2824c43b6afe2403045b140f65c5acc
Author: Michal Jaron <[email protected]>
Date: Tue Sep 13 15:38:36 2022 +0200
Subject: i40e: Fix VF set max MTU size
Link:
https://github.com/torvalds/linux/commit/372539def2824c43b6afe2403045b140f65c5acc
A test kernel is available in the following ppa:
https://launchpad.net/~arif-ali/+archive/ubuntu/sf00343742
If you install the test kernel to a compute host and VM, when you attach
a VF and set the MTU to 9000, it succeeds, and traffic can flow.
[Test Plan]
- 1. Create a Focal VM and assign an Intel E810 (ice) SR-IOV VF with a
- port vlan:
+ Create a Focal VM and assign an Intel E810 (ice) SR-IOV VF with a port
+ vlan:
Openstack works, as does creating a VM directly with uvtool/libvirt.
$ uvt-kvm create focal-test release=focal
Using the document to understand SRIOV basics in the link below
https://www.intel.com/content/www/us/en/developer/articles/technical/configure-
sr-iov-network-virtual-functions-in-linux-kvm.html
The following command show all the bus info for all the network devices
$ lshw -c network -businfo
Choose one, as shown below
pci@0000:17:01.4 ens2f0v4 network Ethernet Adaptive Virtual
Function
We can then add the following into the XML definition via “virsh edit
focal-test”
<interface type='hostdev' managed='yes'>
- <source>
- <address type='pci' domain='0x0000' bus='0x17' slot='0x01'
function='0x4'/>
- </source>
- <vlan>
- <tag id='998'/>
- </vlan>
+ <source>
+ <address type='pci' domain='0x0000' bus='0x17' slot='0x01'
function='0x4'/>
+ </source>
+ <vlan>
+ <tag id='998'/>
+ </vlan>
</interface>
Then we stop and start the VM via "virsh shutdown focal-test" and then
"virsh start focal-test". We can then login to the VM using the command
below
$ uvt-kvm ssh focal-test
Once you have logged in, run the following ip parameters
$ sudo ip a a 192.168.1.7/24 dev enp7s0
$ sudo ip link set up dev enp7s0
$ sudo ip link set mtu 9000 dev enp7s0
Now check dmesg, and we will find the error
[ 61.529605] iavf 0000:07:00.0: PF returned error -5 (IAVF_ERR_PARAM)
to our request 6
Setting the IP and bringing the link up
[ 36.228877] iavf 0000:07:00.0 enp7s0: NIC Link is Up Speed is 25 Gbps Full
Duplex
[ 36.228887] IPv6: ADDRCONF(NETDEV_CHANGE): enp7s0: link becomes ready
[ 45.740100] crng init done
[ 45.740102] random: 7 urandom warning(s) missed due to ratelimiting
Then setting the MTU
[ 61.433706] iavf 0000:07:00.0: Received 16 queues, but can only have a max
of 4
[ 61.433707] iavf 0000:07:00.0: Fixing by reducing queues to 4
[ 61.529605] iavf 0000:07:00.0: PF returned error -5 (IAVF_ERR_PARAM) to
our request 6
[ 61.552890] iavf 0000:07:00.0 enp7s0: NIC Link is Up Speed is 25 Gbps Full
Duplex
There is a test kernel available in the following ppa:
https://launchpad.net/~arif-ali/+archive/ubuntu/sf00343742
If you install the test kernel, setting the MTU to 9000 works as
expected and traffic can flow.
[Where problems could occur]
We are changing how maximum MTU is calculated and applied to VFs in the
iavf and i40e drivers. Currently, any MTU over 1500 does not work at all
when a port VLAN is enabled, but if someone has somehow got their setup
to work, they may see a difference in MTU with these patches applied.
The iavf and i40e drivers are a popular driver, and if a regression were
to occur, initialisation and bringup of these network devices and VFs
might fail.
Most users currently using MTUs of 1500 are unlikely to see any
difference or be at risk of regression.
[Other Info]
Both patches were developed by intel, and have been accepted into
v6.0-rc7 and are already released into upstream stable v5.4.215,
v5.15.71 and v5.19.12. These patches are well tested by the community
and considered safe.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1983656
Title:
iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux source package in Jammy:
In Progress
Status in linux source package in Kinetic:
In Progress
Bug description:
BugLink: https://bugs.launchpad.net/bugs/1983656
[Impact]
Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b]
get no traffic flow and produce error messages in both the host and
guest during network configuration.
Environment: Ubuntu OpenStack Focal-Ussuri with OVN
Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE
Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy
Host Error Messages:
ice 0000:98:00.1: VF 7 failed opcode 6, retval: -5
Guest Error Messages:
iavf 0000:00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6
In the context of these errors "6" refers to the value of
VIRTCHNL_OP_CONFIG_VSI_QUEUES
It was found in these cases that the VM is able to successfully
transmit packets but never receives any and the RX packet drop
counters for the VF in "ip link" on the host increase equal to the RX
packet count.
There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d
claiming to resolve this error in some cases. It is already included
in 5.15.0-41-generic and did not resolve the issue.
The following conditions are required to trigger the bug:
- A port VLAN must be assigned by the host
- The MTU must be set >1500 by the guest
There is no workaround, Intel E810 SR-IOV VFs with MTU >1500 cannot be
used without these patches.
[Fix]
iavf currently sets the maximum packet size to IAVF_MAX_RXBUFFER, but
on the previous ice driver, it was decremented by VLAN_HLEN to make
some space to fit the VLAN header. This doesn't happen on iavf, and we
end up trying to use a packet size larger than IAVF_MAX_RXBUFFER,
causing the IAVF_ERR_PARAM error.
The fix is to change the maximum packet size from IAVF_MAX_RXBUFFER to
max_mtu received from the PF via GET_VF_RESOURCES msg.
Also pick up a necessary commit for i40e to announce the correct
maximum packet size by GET_VF_RESOURCES msg.
This has been fixed by the following commits:
commit 399c98c4dc50b7eb7e9f24da7ffdda6f025676ef
Author: Michal Jaron <[email protected]>
Date: Tue Sep 13 15:38:35 2022 +0200
Subject: iavf: Fix set max MTU size with port VLAN and jumbo frames
Link:
https://github.com/torvalds/linux/commit/399c98c4dc50b7eb7e9f24da7ffdda6f025676ef
commit 372539def2824c43b6afe2403045b140f65c5acc
Author: Michal Jaron <[email protected]>
Date: Tue Sep 13 15:38:36 2022 +0200
Subject: i40e: Fix VF set max MTU size
Link:
https://github.com/torvalds/linux/commit/372539def2824c43b6afe2403045b140f65c5acc
A test kernel is available in the following ppa:
https://launchpad.net/~arif-ali/+archive/ubuntu/sf00343742
If you install the test kernel to a compute host and VM, when you
attach a VF and set the MTU to 9000, it succeeds, and traffic can
flow.
[Test Plan]
Create a Focal VM and assign an Intel E810 (ice) SR-IOV VF with a port
vlan:
Openstack works, as does creating a VM directly with uvtool/libvirt.
$ uvt-kvm create focal-test release=focal
Using the document to understand SRIOV basics in the link below
https://www.intel.com/content/www/us/en/developer/articles/technical/configure-
sr-iov-network-virtual-functions-in-linux-kvm.html
The following command show all the bus info for all the network
devices
$ lshw -c network -businfo
Choose one, as shown below
pci@0000:17:01.4 ens2f0v4 network Ethernet Adaptive
Virtual Function
We can then add the following into the XML definition via “virsh edit
focal-test”
<interface type='hostdev' managed='yes'>
<source>
<address type='pci' domain='0x0000' bus='0x17' slot='0x01'
function='0x4'/>
</source>
<vlan>
<tag id='998'/>
</vlan>
</interface>
Then we stop and start the VM via "virsh shutdown focal-test" and then
"virsh start focal-test". We can then login to the VM using the
command below
$ uvt-kvm ssh focal-test
Once you have logged in, run the following ip parameters
$ sudo ip a a 192.168.1.7/24 dev enp7s0
$ sudo ip link set up dev enp7s0
$ sudo ip link set mtu 9000 dev enp7s0
Now check dmesg, and we will find the error
[ 61.529605] iavf 0000:07:00.0: PF returned error -5
(IAVF_ERR_PARAM) to our request 6
Setting the IP and bringing the link up
[ 36.228877] iavf 0000:07:00.0 enp7s0: NIC Link is Up Speed is 25 Gbps Full
Duplex
[ 36.228887] IPv6: ADDRCONF(NETDEV_CHANGE): enp7s0: link becomes ready
[ 45.740100] crng init done
[ 45.740102] random: 7 urandom warning(s) missed due to ratelimiting
Then setting the MTU
[ 61.433706] iavf 0000:07:00.0: Received 16 queues, but can only have a max
of 4
[ 61.433707] iavf 0000:07:00.0: Fixing by reducing queues to 4
[ 61.529605] iavf 0000:07:00.0: PF returned error -5 (IAVF_ERR_PARAM) to
our request 6
[ 61.552890] iavf 0000:07:00.0 enp7s0: NIC Link is Up Speed is 25 Gbps Full
Duplex
There is a test kernel available in the following ppa:
https://launchpad.net/~arif-ali/+archive/ubuntu/sf00343742
If you install the test kernel, setting the MTU to 9000 works as
expected and traffic can flow.
[Where problems could occur]
We are changing how maximum MTU is calculated and applied to VFs in
the iavf and i40e drivers. Currently, any MTU over 1500 does not work
at all when a port VLAN is enabled, but if someone has somehow got
their setup to work, they may see a difference in MTU with these
patches applied.
The iavf and i40e drivers are a popular driver, and if a regression
were to occur, initialisation and bringup of these network devices and
VFs might fail.
Most users currently using MTUs of 1500 are unlikely to see any
difference or be at risk of regression.
[Other Info]
Both patches were developed by intel, and have been accepted into
v6.0-rc7 and are already released into upstream stable v5.4.215,
v5.15.71 and v5.19.12. These patches are well tested by the community
and considered safe.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983656/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
