Virtio-net Service Guide Release Notes

4720234

Description: Virtio-net-controller app crash occurs due to live update when an unplug operation is still in progress.

Keyword: Update; hotplug

Detected in version: 25.10

4735205

Description: The virtio-net-controller may fail to restart or terminate gracefully, logging an ipc_server.c:112:ipc_server_handler: Failed to epoll ctl del for fd 7 error.

Keyword: Virtio-net controller; dpa_partition

Detected in version: 25.10

4745706

Description: The virtnet query command incorrectly accepts and executes queries for non-existent or invalid queue IDs (e.g., -q 999) without returning an error.

Keyword: Virtio-net controller; input validation

Detected in version: 25.10

4779252

Description: A crash (program terminates with signal SIGABRT and Aborted) occurs when trying to enable packet count to device with no eth queues.

Keyword: Packet_count; counters; CLI

Detected in version: 25.10

4780761

Description: The virtio-net-controller incorrectly inherits VF MTU settings from the PF section of the virtnet.conf configuration file.

Keyword: VF; MTU

Detected in version: 25.10

4785728

Description: A hot-unplug operation for a virtio-net PF can block the controller for up to 10 minutes.

Keyword: Unplug; RPC; CLI

Detected in version: 25.10

4819572

Description: Device modify commands during driver unbind cause "device's health compromised" errors in dmesg due to firmware commands order violation.

Keyword: CLI; logging

Detected in version: 25.10

4794617

Description: Crash occurs during application load due to invalid number of EU's in SPRD config file.

Keyword: Execution units; SPRD

Detected in version: 25.10

4834032

Description: Virtio-net service may fail to terminate gracefully if a system reboot or shutdown is initiated during the service's early initialization phase, causing the system to hang for up to 30 minutes.

Keyword: Reboot hang; SIGTERM

Detected in version: 25.10

4407495

Description: The AARFS feature on BlueField-3 virtio-net devices is not persistent across controller restarts.

Keyword: Recovery; Accelerated Adaptive Receive Flow Steering

Detected in version: 25.10

4407517

Description: The DIM and AARFS features are not persistent across virtio-net controller restarts, potentially impacting network performance and CPU utilization.

Keyword: Recovery; Dynamic Interrupt Moderation; Accelerated Adaptive Receive Flow Steering

Detected in version: 25.10

4408123

Description: The pkt_cnt (packet counter) feature on virtio-net devices is not persistent across controller restarts, causing all hardware-level packet statistics to return to zero if the virtio-net-controller service is restarted.

Keyword: Recovery; pkt_cnt

Detected in version: 25.10

4731868

Description: Invalid recovery data may cause repeated startup failures.

Keyword: Recovery

Detected in version: 25.10

4739902

Description: Controller crash occurs during host shutdown when VF SF creation fails due to resource exhaustion.

Keyword: Recovery; VF; SF

Detected in version: 25.10

4781642

Description: If the virtnet.conf configuration file contains an empty JSON object ({}) at startup, the virtio-net controller incorrectly attempts to append default settings, resulting in a malformed JSON file.

Keyword: Recovery; mlnx_virtnet_check

Detected in version: 25.10

4782116

Description: Configuring an invalid value (other than 0 or 1) for the is_lag parameter in the virtnet.conf configuration file causes the virtio-net controller to fail during startup, triggering a cleanup routine that deletes all existing recovery files.

Keyword: Recovery

Detected in version: 25.10

4834822

Description: Corrupted recovery files (e.g., invalid sf_num) could leave the recovery directory in an inconsistent state with partial files remaining after restart.

Keyword: Recovery

Detected in version: 25.10

4840874

Description: Crash occurs during recovery flow when recovery files contain corrupted data.

Keyword: Recovery

Detected in version: 25.10

4844180

Description: Crash occurs during virtio-net-controller shutdown when VIRTIO_NET_EMULATION_NUM_PF

is configured to 0.

Keyword: Controller; VIRTIO_NET_EMULATION_NUM_PF

Detected in version: 25.10

4845177

Description: Multiple leaks in virtnet occur in CLI error paths.

Keyword: Stability; resource leak

Detected in version: 25.10

4847947

Description: Unplug failure occurs on BlueField-2 when the firmware lacks host awareness support.

Keyword: Unplug; firmware

Detected in version: 25.10

4797496

Description: Virtio-net does not support Packed Virtqueues ("packed_vq": 1) in the following scenarios:

• It is not supported on any VF configured for live migration.

• It is not supported on any PF that has the Admin Queue (AQ) enabled.

Workaround: Explicitly disable Packed VQs by setting "packed_vq": 0 in the virtnet.conf configuration file for any PFs using AQs or VFs intended for live migration. Use the default Split VQ (split_vq) mode instead.

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, virtnet -v or --version displays the version of the updated CLI, not the source or target upgrade versions.

Workaround: Run virtnet version to view both the original and destination versions.

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 ip command to rename the representor manually.

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 VIRTIO_NET_F_CTRL_VLAN is not supported. Enabling it from the hotplug device may results in anomalous behavior.

Workaround: Disable VIRTIO_NET_F_CTRL_VLAN.

Keyword: Feature bit

Reported in version: 24.07

4001261

Description: The virtnet.conf file does not check invalid values such as negative numbers or 0.

Workaround: N/A

Keyword: Virtnet; config; invalid value

Reported in version: 24.07

3965598

Description: Admin-VQ-based transitional VF show a vf_get error when the controller is restarted. However, VF functionality is not affected.

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 DPA_AUTHENTICATION is enabled.

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 uverbs_destroy_ufile_hw is observed if virtio-net-controller is still running.

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 vq is broken (e.g., device is removed) under heavy traffic.

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., virtnet query).

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 max_queues_size output from the virtnet list may be wrong. This does not affect the actual value.

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 (Unexpected TXQ (13) queue failure: -28) from dmesg in traffic stress test.

Workaround: N/A

Keywords: Virtio-net; error

Reported in version: DOCA 1.2.0

2870213

Description: Servers do not recover after configuring PCI_SWITCH_EMULATION_NUM_PORT to 32 followed by power cycle.

Workaround: Clear NVRAM and reset mlxconfig to default

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