The following subsections provide information on virtio-net service new features, interoperability, known issues, and bug fixes.
Changes and New Features
|
Title |
Description |
|---|---|
|
Faster Controller Service Restart |
The virtio-net-controller service restart flow is optimized, so the service takes less time to come back up after a restart. |
|
Live Update During Device Operations |
Live updates ( |
Bug Fixes
|
Ref # |
Issue Details |
|---|---|
|
5354389 |
Description: Live updates now release the admin virtqueue of devices that have no data virtqueues, such as a PF used only by a live migration agent. Previously, after about 27 live updates, every further live update failed. |
|
Detected in Version: v26.10.8-dirty |
|
|
5334956 |
Description: The CLI and libvirtnet now reject hotplug and modify MTU values below 68 with an error. Previously, these values reached the device, which rejected them. |
|
Detected in Version: v26.10.6 |
|
|
5324160 |
Description: RX performance is improved when running with more than 48 total queues. Previously, RX could be more than 50% slower than TX. |
|
Detected in Version: v26.01.1011 |
|
|
5308622 |
Description: The |
|
Detected in Version: 26.07 |
|
|
5302012 |
Description: With a jumbo MTU and |
|
Detected in Version: 26.07 |
|
|
5275589 |
Description: Enabling |
|
Detected in Version: v26.10.4 |
|
|
5273959 |
Description: Changing a virtio-net device's ring size with |
|
Detected in Version: 26.10 |
|
|
5237152 |
Description: A virtqueue no longer stops processing transmit descriptors while sending traffic. Previously, the host kernel reported |
|
Detected in Version: 25.10.13.1 |
|
|
5234957 |
Description: The controller now checks the length of transmit descriptor chains. Previously, invalid transmit descriptors from the guest could crash the DPA application and hang the host. |
|
Detected in Version: 26.07.9-1 |
|
|
5221544 |
Description: The virtio-net-controller no longer restarts endlessly when a hotplug PF has a pending hot-unplug and its host driver has failed. |
|
Detected in Version: 26.07 |
|
|
5221315 |
Description: |
|
Detected in Version: 26.07 |
|
|
5151022 |
Description: The virtio-net-controller no longer hangs on shutdown or restarts in a loop when the SPRD partition configuration provides invalid or insufficient DPA EU IDs. |
|
Detected in Version: v26.07.6 |
|
|
4535271 |
Description: Live migration of a VM whose virtio-net driver uses VLAN filtering, such as a Windows guest, no longer fails on the destination with |
|
Detected in Version: v25.07.3 |
Known Issues
The following are known limitations of this NVIDIA® BlueField® virtio-net software version.
|
Ref # |
Issue Details |
|---|---|
|
4540857 |
Description: When more than 64 unique unicast MAC addresses (for example, macvlan sub-interfaces) are configured on a single virtio-net interface, traffic to the addresses beyond the first 64 is dropped. |
|
Workaround: Configure no more than 64 unique unicast MAC addresses on a single virtio-net interface, or enable promiscuous mode on the affected guest interface: |
|
|
Keyword: MAC filter table; macvlan; promiscuous mode |
|
|
Reported in Version: 26.10 |
|
|
4849313 |
Description: Creating a hotplug device can show an outdated |
|
Workaround: Run |
|
|
Keyword: Hotplug; |
|
|
Reported in Version: 26.07 |
|
|
5013051 |
Description: Following a NATS broker restart, the virtio-net-controller relies on lazy reconnection. Consequently, the first event generated while disconnected is lost. However, this dropped event triggers a successful reconnection, allowing all subsequent events to be delivered normally. |
|
Workaround: N/A |
|
|
Keyword: LM; vnet_event |
|
|
Reported in version: 26.04 |
|
|
4898379 |
Description: Manually issuing inactive and active state commands (e.g., via devlink) on a SF is not supported while the virtio-net controller is active. Executing these state changes abruptly tears down the underlying firmware and hardware resources without properly notifying the controller. This causes an immediate loss of traffic for all connections associated with the SF, and the system cannot automatically recover from this state. |
|
Workaround: Avoid manually toggling SF states while the virtio-net controller is running. If an SF is inadvertently toggled and traffic drops, you must perform a full manual reinitialization of both the affected SF and the controller to restore network connectivity. |
|
|
Keyword: Scalable function; recovery |
|
|
Reported in version: 26.04 |
|
|
4961952 |
Description: If the virtio-net controller is restarted during an active vDPA live migration, transient RQT modify errors (e.g., "Remote I/O error") may appear in the system logs on the migration source VF. These error messages are strictly cosmetic and have no functional impact. |
|
Workaround: N/A |
|
|
Keyword: Live migration; vDPA |
|
|
Reported in version: 26.04 |
|
|
4914672 |
Description: During rapid, repeated virtual machine stress testing (e.g., executing |
|
Workaround: Increase the boot wait time in your automation scripts to a minimum of 200 seconds to provide the Windows VM sufficient time to fully complete its crash recovery, finish the boot process, and initialize its virtio-net interfaces before network connectivity is verified. |
|
|
Keyword: Windows VM; reboot |
|
|
Reported in version: 26.04 |
|
|
4914672 |
Description: CentOS 7 virtual machines running older kernels (specifically kernel 3.10) may experience a transient soft lockup in |
|
Workaround: N/A |
|
|
Keyword: Kernel 3.10.0; CentOS 7; lockup |
|
|
Reported in version: 26.04 |
|
|
4797496 |
Description: Virtio-net does not support Packed Virtqueues (
|
|
Workaround: Explicitly disable Packed VQs by setting |
|
|
Keyword: VQ; live migration |
|
|
Reported in version: 25.10 |
|
|
4498529 |
Description: Windows VM may take a lot of time to load when VLAN tagging is enabled. |
|
Workaround: Disable VLAN tagging. |
|
|
Keyword: Windows; VLAN |
|
|
Reported in version: 25.10 |
|
|
4534273 |
Description: After installing a new version, |
|
Workaround: Run |
|
|
Keyword: CLI; version; update |
|
|
Reported in version: 25.07 |
|
|
3879093 |
Description: When creating a large number of virtio-net VFs, the representor name of the SF may not be renamed. |
|
Workaround: Use the |
|
|
Keyword: Representor |
|
|
Reported in version: 24.10 |
|
|
3943905 |
Description: Host OS kernel <3.19 does not support 31 hotplug devices. |
|
Workaround: Avoid hotplugging more than 20 devices if host OS kernel is <3.19, or upgrade the kernel to ≥3.19. |
|
|
Keyword: Host OS; kernel; hotplug |
|
|
Reported in version: 24.07 |
|
|
4022160 |
Description: Feature bit |
|
Workaround: Disable |
|
|
Keyword: Feature bit |
|
|
Reported in version: 24.07 |
|
|
4001261 |
Description: The |
|
Workaround: N/A |
|
|
Keyword: Virtnet; config; invalid value |
|
|
Reported in version: 24.07 |
|
|
3965598 |
Description: Admin-VQ-based transitional VF show a |
|
Workaround: N/A |
|
|
Keyword: Admin VQ; transitional device |
|
|
Reported in version: 24.07 |
|
|
3961951 |
Description: Out-of-memory call trace occurs when creating many (>300) VFs on a BlueField running OpenEuler or CentOS 7.6. |
|
Workaround: Update the kernel to support shared RQ. |
|
|
Keyword: OOM; OpenEuler; CentOS 7.6; virtual function |
|
|
Reported in version: 24.07 |
|
|
3862683 |
Description: Creating VFs and hotplug PFs in parallel can lead to controller crash. |
|
Workaround: Create VFs followed by hotplug PF or vice versa. |
|
|
Keyword: Virtio-net emulation |
|
|
Reported in version: 1.9.0 |
|
|
3665070 |
Description: Virtio-net controller fails to load if |
|
Workaround: N/A |
|
|
Keywords: Virtio-net; DPA |
|
|
Reported in version: DOCA 2.5.0 |
|
|
3538486 |
Description: When removing LAG configuration from BlueField, a kernel warning for |
|
Workaround: Stop virtio-net-controller service before cleaning up bond configuration. |
|
|
Keywords: Virtio-net; LAG |
|
|
Reported in version: DOCA 2.2.0 |
|
|
3683801 |
Description: Starting from kernel 5.14, the virtio-net TX path has a logic which may trigger infinite loop when |
|
Workaround: N/A |
|
|
Keyword: Virtio-net |
|
|
Reported in version: DOCA 1.8.0 |
|
|
3714522 |
Description: When creating/destroying VFs back to back, make sure the virtio-net controller side does not see any alive VF before recreating them from the guest OS (i.e., |
|
Workaround: N/A |
|
|
Keyword: Virtio-net; VFs |
|
|
Reported in version: DOCA 1.8.0 |
|
|
3694402 |
Description: When restarting the virtio-net-controller from the DPU while the guest OS is booting, the guest OS may see kernel call trace while the controller is preparing the device. It recovers once the controller starts. |
|
Workaround: N/A |
|
|
Keyword: Virtio-net; hotplug; restart |
|
|
Reported in version: DOCA 1.8.0 |
|
|
3633453 |
Description: Jumbo MTU is only supported on a guest OS with kernel 4.11 and above. |
|
Workaround: N/A |
|
|
Keyword: Virtio-net; jumbo MTU |
|
|
Reported in version: DOCA 1.7.0 |
|
|
3021967 |
Description: When rebooting a DPU with a large number of VFs created on host, VF recovery may fail due to timeout. |
|
Workaround: Restart the driver on the host after the DPU is up. |
|
|
Keyword: Reboot; VFs |
|
|
Reported in version: DOCA 1.7.0 |
|
|
3232444 |
Description: After live migration of virtio-net devices using the VFE driver, the |
|
Workaround: N/A |
|
|
Keywords: Virtio-net; live migration |
|
|
Reported in version: DOCA 1.4.0 |
|
|
2801780 |
Description: When running virtio-net-controller with host kernel older than 3.10.0-1160.el7, host virtio driver may get error ( |
|
Workaround: N/A |
|
|
Keywords: Virtio-net; error |
|
|
Reported in version: DOCA 1.2.0 |
|
|
2870213 |
Description: Servers do not recover after configuring |
|
Workaround: Clear NVRAM and reset |
|
|
Keywords: Virtio-net; power cycle |
|
|
Reported in version: DOCA 1.2.0 |
|
|
2685191 |
Description: Once virtio-net is enabled, the mlx5 Windows VF becomes unavailable. |
|
Workaround: N/A |
|
|
Keywords: Virtio-net; virtual function; WinOF-2 |
|
|
Reported in version: DOCA 1.2.0 |
|
|
2702395 |
Description: When a device is hot-plugged from the virtio-net controller, the host OS may hang when warm reboot is performed on the host and Arm at the same time. |
|
Workaround: Reboot the host OS first and only then reboot DPU. |
|
|
Keywords: Virtio-net controller; hot-plug; reboot |
|
|
Reported in version: DOCA 1.2.0 |
Last updated: