[vs] Enable SAI_VS_USE_CONFIGURED_SPEED_AS_OPER_SPEED in VS platform sai.profile by rustiqly · Pull Request #25428 · sonic-net/sonic-buildimage

rustiqly · 2026-02-11T00:41:37Z

What I did

Enable SAI_VS_USE_CONFIGURED_SPEED_AS_OPER_SPEED=true in all VS platform sai.profile files.

Why I did it

Virtual NICs (virtio) do not report valid link speed via sysfs — /sys/class/net/ethN/speed returns -1. The VS SAI reads this value and interprets it as 4294967295 (0xFFFFFFFF unsigned), which causes show interfaces status to display 4294967.3G as the port speed for operationally up ports.

The SAI_VS_USE_CONFIGURED_SPEED_AS_OPER_SPEED flag (added in sonic-sairedis) makes VS SAI return the configured speed from SAI_PORT_ATTR_SPEED (CONFIG_DB) as the operational speed, bypassing the broken sysfs query entirely.

This is the right default for all VS platforms since virtual switches never have real physical link speeds to report.

How I did it

Added SAI_VS_USE_CONFIGURED_SPEED_AS_OPER_SPEED=true to all VS sai.profile files:

x86_64-kvm_x86_64-r0/SONiC-VM/sai.profile
x86_64-kvm_x86_64-r0/brcm_gearbox_vs/sai.profile
x86_64-kvm_x86_64_4_asic-r0/msft_four_asic_vs/0/sai.profile (1/2/3 are symlinks)
x86_64-kvm_x86_64_6_asic-r0/msft_multi_asic_vs/0/sai.profile (1-5 are symlinks)

How to verify it

Build SONiC VS image with this change
Boot on KVM with virtio NICs
show interfaces status shows correct configured speed (e.g. 40G) instead of 4294967.3G

Companion PR: sonic-net/sonic-sairedis#1763 (fixes the code to also handle -1 gracefully as fallback)

Signed-off-by: Rustiqly rustiqly@users.noreply.github.com

rustiqly · 2026-02-11T00:41:44Z

cc @liushilongbuaa

mssonicbld · 2026-02-11T00:41:47Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-02-11T00:41:59Z

Azure Pipelines successfully started running 1 pipeline(s).

mssonicbld · 2026-02-11T04:09:09Z

/azp run Azure.sonic-buildimage

rustiqly · 2026-02-11T04:09:12Z

Updated to also add SAI_VS_USE_CONFIGURED_SPEED_AS_OPER_SPEED=true to src/sonic-device-data/src/sai.vs_profile, which is the template used to generate sai.profile for all VS HwSKUs at build time (including the default Force10-S6000 HwSKU).

Previously the PR only patched device/virtual/ profiles (used by docker-sonic-vs), but missed the sonic-device-data template that generates profiles for the full KVM image. The Makefile in src/sonic-device-data copies sai.vs_profile as sai.profile into every VS HwSKU directory during package build.

Verified on a live VS VM: after adding this flag to the Force10-S6000 sai.profile and restarting syncd, all ports correctly report 40G instead of 4294967295 (0xFFFFFFFF).

azure-pipelines · 2026-02-11T04:09:23Z

Azure Pipelines successfully started running 1 pipeline(s).

lihuay · 2026-02-12T04:38:35Z

/azp run

azure-pipelines · 2026-02-12T04:38:50Z

Azure Pipelines successfully started running 1 pipeline(s).

Copilot

Pull request overview

Enables the VS SAI profile flag SAI_VS_USE_CONFIGURED_SPEED_AS_OPER_SPEED=true so VS reports operational port speed based on the configured speed (from SAI_PORT_ATTR_SPEED) instead of relying on broken sysfs link speed in virtio environments.

Changes:

Add SAI_VS_USE_CONFIGURED_SPEED_AS_OPER_SPEED=true to the common VS SAI profile template.
Add the same flag to VS platform sai.profile files for SONiC-VM, brcm_gearbox_vs, and MSFT multi-ASIC VS HWSKUs.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
src/sonic-device-data/src/sai.vs_profile	Adds configured-speed-as-oper-speed behavior to the common VS SAI profile.
device/virtual/x86_64-kvm_x86_64-r0/SONiC-VM/sai.profile	Enables configured speed as oper speed for the default SONiC-VM VS HWSKU profile.
device/virtual/x86_64-kvm_x86_64-r0/brcm_gearbox_vs/sai.profile	Enables configured speed as oper speed for the gearbox VS HWSKU profile.
device/virtual/x86_64-kvm_x86_64_4_asic-r0/msft_four_asic_vs/0/sai.profile	Enables configured speed as oper speed for 4-ASIC VS (ASIC 0 profile).
device/virtual/x86_64-kvm_x86_64_6_asic-r0/msft_multi_asic_vs/0/sai.profile	Enables configured speed as oper speed for 6-ASIC VS (ASIC 0 profile).

device/virtual/x86_64-kvm_x86_64-r0/SONiC-VM/sai.profile

mssonicbld · 2026-02-13T05:50:13Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-02-13T05:50:24Z

Azure Pipelines successfully started running 1 pipeline(s).

mssonicbld · 2026-02-14T20:26:49Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-02-14T20:27:00Z

Azure Pipelines successfully started running 1 pipeline(s).

sonicly1g · 2026-02-14T21:07:35Z

Updated to also add SAI_VS_USE_CONFIGURED_SPEED_AS_OPER_SPEED=true to sai_mlnx.profile and sai_dpu_2p.profile under device/virtual/ — these are used by docker-sonic-vs/start.sh which copies them over sai.profile for Mellanox-SN2700 and DPU-2P HwSKUs.

Good catch from the Copilot review — without this, the speed flag would be overwritten when start.sh runs on those platforms.

mssonicbld · 2026-02-14T21:07:35Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-02-14T21:07:46Z

Azure Pipelines successfully started running 1 pipeline(s).

mssonicbld · 2026-02-23T16:59:51Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-02-23T17:00:04Z

Azure Pipelines successfully started running 1 pipeline(s).

mssonicbld · 2026-02-24T15:02:58Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-02-24T15:03:21Z

Azure Pipelines successfully started running 1 pipeline(s).

azure-pipelines · 2026-02-24T17:05:09Z

Azure Pipelines successfully started running 1 pipeline(s).

mssonicbld · 2026-02-25T15:01:47Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-02-25T15:02:02Z

Azure Pipelines successfully started running 1 pipeline(s).

yxieca

LGTM. AI agent on behalf of Ying.

yxieca

LGTM. AI agent on behalf of Ying.

yxieca

AI agent on behalf of Ying.

yxieca

AI agent on behalf of Ying. Quick review: [vs]. No issues found.

yxieca

AI agent on behalf of Ying. Quick review: [vs] Enable SAI_VS_USE_CONFIGURED_SPEED_AS_OPER_SPEED in VS platform sai.profile. No issues found.

mssonicbld · 2026-03-02T15:03:04Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-03-02T15:03:16Z

Azure Pipelines successfully started running 1 pipeline(s).

mssonicbld · 2026-03-03T15:04:42Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-03-03T15:04:56Z

Azure Pipelines successfully started running 1 pipeline(s).

mssonicbld · 2026-03-04T15:07:23Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-03-04T15:07:36Z

Azure Pipelines successfully started running 1 pipeline(s).

mssonicbld · 2026-03-05T15:03:45Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-03-05T15:03:58Z

Azure Pipelines successfully started running 1 pipeline(s).

Virtual NICs (virtio) do not report valid link speed via sysfs (/sys/class/net/ethN/speed returns -1). This causes VS SAI to report 0xFFFFFFFF as the oper speed, displayed as '4294967.3G' in CLI. Enable SAI_VS_USE_CONFIGURED_SPEED_AS_OPER_SPEED=true in all VS platform sai.profile files so that VS SAI returns the configured speed (from CONFIG_DB) as the oper speed instead of querying sysfs. Updated profiles: - x86_64-kvm_x86_64-r0/SONiC-VM/sai.profile - x86_64-kvm_x86_64-r0/brcm_gearbox_vs/sai.profile - x86_64-kvm_x86_64_4_asic-r0/msft_four_asic_vs/0/sai.profile (+ symlinked 1-3) - x86_64-kvm_x86_64_6_asic-r0/msft_multi_asic_vs/0/sai.profile (+ symlinked 1-5) Signed-off-by: Rustiqly <rustiqly@users.noreply.github.com>

mssonicbld · 2026-03-06T15:02:15Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-03-06T15:02:28Z

Azure Pipelines successfully started running 1 pipeline(s).

rustiqly mentioned this pull request Feb 11, 2026

[vslib] Fix VS SAI reporting 0xFFFFFFFF oper speed for virtio NICs sonic-net/sonic-sairedis#1763

Open

rustiqly force-pushed the fix/vs-sai-profile-oper-speed branch from fcf18f7 to e105505 Compare February 11, 2026 04:09

rustiqly requested a review from lguohan as a code owner February 11, 2026 04:09

lihuay requested a review from Copilot February 12, 2026 04:38

Copilot started reviewing on behalf of lihuay February 12, 2026 04:38 View session

Copilot AI reviewed Feb 12, 2026

View reviewed changes

device/virtual/x86_64-kvm_x86_64-r0/SONiC-VM/sai.profile Show resolved Hide resolved

rustiqly force-pushed the fix/vs-sai-profile-oper-speed branch from e105505 to 093273a Compare February 13, 2026 05:49

rustiqly force-pushed the fix/vs-sai-profile-oper-speed branch from 8bfd07d to e053921 Compare February 14, 2026 21:07

rustiqly force-pushed the fix/vs-sai-profile-oper-speed branch from e053921 to 62be1e4 Compare February 23, 2026 16:58

rustiqly force-pushed the fix/vs-sai-profile-oper-speed branch from 62be1e4 to 04c02f6 Compare February 24, 2026 15:01

rustiqly force-pushed the fix/vs-sai-profile-oper-speed branch from 04c02f6 to 0e5f794 Compare February 24, 2026 17:01

rustiqly force-pushed the fix/vs-sai-profile-oper-speed branch from 0e5f794 to a236ae6 Compare February 25, 2026 15:01

This was referenced Feb 26, 2026

[CI] Flaky kvmtest-dpu failures on unrelated PRs #25692

Open

[CI] Flaky kvmtest-t1-lag-vpp failures on unrelated PRs #25695

Open

rustiqly force-pushed the fix/vs-sai-profile-oper-speed branch from a236ae6 to 634a8d7 Compare February 26, 2026 15:01

yxieca approved these changes Feb 28, 2026

View reviewed changes

yxieca approved these changes Mar 1, 2026

View reviewed changes

rustiqly force-pushed the fix/vs-sai-profile-oper-speed branch from 634a8d7 to cb2f960 Compare March 2, 2026 15:01

rustiqly force-pushed the fix/vs-sai-profile-oper-speed branch from cb2f960 to 41ef7aa Compare March 3, 2026 15:02

rustiqly force-pushed the fix/vs-sai-profile-oper-speed branch from 41ef7aa to 8287c6a Compare March 4, 2026 15:04

rustiqly force-pushed the fix/vs-sai-profile-oper-speed branch 2 times, most recently from c910e6c to fcb7214 Compare March 5, 2026 15:01

rustiqly force-pushed the fix/vs-sai-profile-oper-speed branch from fcb7214 to 5d17d97 Compare March 6, 2026 15:01

lihuay merged commit 4c398f0 into sonic-net:master Mar 7, 2026
25 of 26 checks passed

Conversation

rustiqly commented Feb 11, 2026

What I did

Why I did it

How I did it

How to verify it

Uh oh!

rustiqly commented Feb 11, 2026

Uh oh!

mssonicbld commented Feb 11, 2026

Uh oh!

azure-pipelines bot commented Feb 11, 2026

Uh oh!

mssonicbld commented Feb 11, 2026

Uh oh!

rustiqly commented Feb 11, 2026

Uh oh!

azure-pipelines bot commented Feb 11, 2026

Uh oh!

lihuay commented Feb 12, 2026

Uh oh!

azure-pipelines bot commented Feb 12, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

mssonicbld commented Feb 13, 2026

Uh oh!

azure-pipelines bot commented Feb 13, 2026

Uh oh!

mssonicbld commented Feb 14, 2026

Uh oh!

azure-pipelines bot commented Feb 14, 2026

Uh oh!

sonicly1g commented Feb 14, 2026

Uh oh!

mssonicbld commented Feb 14, 2026

Uh oh!

azure-pipelines bot commented Feb 14, 2026

Uh oh!

mssonicbld commented Feb 23, 2026

Uh oh!

azure-pipelines bot commented Feb 23, 2026

Uh oh!

mssonicbld commented Feb 24, 2026

Uh oh!

azure-pipelines bot commented Feb 24, 2026

Uh oh!

azure-pipelines bot commented Feb 24, 2026

Uh oh!

mssonicbld commented Feb 25, 2026

Uh oh!

azure-pipelines bot commented Feb 25, 2026

Uh oh!

yxieca left a comment

Choose a reason for hiding this comment

Uh oh!

yxieca left a comment

Choose a reason for hiding this comment

Uh oh!

yxieca left a comment

Choose a reason for hiding this comment

Uh oh!

yxieca left a comment

Choose a reason for hiding this comment

Uh oh!

yxieca left a comment

Choose a reason for hiding this comment

Uh oh!

mssonicbld commented Mar 2, 2026

Uh oh!

azure-pipelines bot commented Mar 2, 2026

Uh oh!

mssonicbld commented Mar 3, 2026

Uh oh!

azure-pipelines bot commented Mar 3, 2026

Uh oh!