Switch to KVM hypervisor on Rb3Gen2-Core-Kit and QCM6490-IDP by vkraleti · Pull Request #2879 · qualcomm-linux/meta-qcom

Viswanath Kraleti (vkraleti) · 2026-08-05T11:02:23Z

All PILs are functioning correctly with KVM on Rb3Gen2-Core-Kit and QCM6490-IDP. Update
FIT_DTB_COMPATIBLE entries and machine configurations to switch to KVM on these boards.

qcomlnxci · 2026-08-05T20:12:18Z

Test Coral run workflow

Test jobs for commit `c4dcacb`

qcomdistro: multimedia image-prop
Pass: 38 | Fail: 3 | Others: 12 | Total: 53
qcomdistro: multimedia image
Pass: 8 | Fail: 1 | Total: 9

github-actions · 2026-08-19T09:19:49Z

Test run workflow

Test jobs for commit `62eb8a7`

qcom-distro
Pass: 296 | Fail: 37 | Total: 357

qcom-distro_linux-qcom-6.18
Pass: 233 | Fail: 0 | Total: 259

nodistro
Pass: 10 | Fail: 0 | Total: 10

test-reporting-app · 2026-08-19T09:20:10Z

Test Results

119 files + 38 715 suites +289 10h 17m 50s ⏱️ + 2h 51m 31s
175 tests + 2 132 ✅ - 23 1 💤 + 1 42 ❌ +24
4 579 runs +1 816 4 471 ✅ +1 775 50 💤 +12 58 ❌ +29

For more details on these failures, see this check.

Results for commit 62eb8a7. ± Comparison against base commit 1efd355.

♻️ This comment has been updated with latest results.

qcomlnxci · 2026-08-19T16:51:15Z

Test Coral run workflow

Test jobs for commit `a0d5c14`

qcomdistro: multimedia image-prop
Pass: 26 | Fail: 0 | Total: 26
qcomdistro: multimedia image
Pass: 9 | Fail: 0 | Total: 9

Dmitry Baryshkov (lumag) · 2026-08-19T23:40:10Z

+
+local_conf_header:
+  gunyah: |
+        MACHINE_FEATURES:remove = "kvm"


It's no a distro configuration. Changing it in the distro-like Kas fragment is invalid.

Renamed the config as ci/gunyah.yml and removed distro include so that, any machine+distro combination can be build with Gunyah.

Dmitry Baryshkov (lumag) · 2026-08-19T23:40:45Z

+          - machine: iq-615-evk
+            distro:
+                name: qcom-distro-gunyah
+                yamlfile: ':ci/qcom-distro-gunyah.yml'


We are not changing the distro here, so this is incorrect.

qcom-distro in the name is to indicate the build is with gunyah and qcom-distro. It can't be called as qcom-distro+gunyah, as having any other separator apart from hypen(-) / underscore(_) caused issues while copying to S3 in the past.

Dmitry Baryshkov (lumag) · 2026-08-19T23:42:47Z

+FIT_DTB_COMPATIBLE[qcom_qcm6490-idp-staging] = "qcm6490-idp kodiak-el2 kodiak-staging"

-FIT_DTB_COMPATIBLE[qcom_qcs5430-iot-el2kvm] = \
+FIT_DTB_COMPATIBLE[qcom_qcs5430-iot] = \


This will break users switching from QLI 2.0 to QLI 2.1 or master without erasing UEFI variables. This doesn't sound good.

But is there any option to clear efivars? Even for L,M, and T this was an agreed short coming and users need to perform one time efivars cleanup.

The switch itself is already something that is not really ideal to push as part of 2.x, as this is a major change in the end.

The user will have to remove efivars, update both the OS and the firmware via capsule-updates, and hopefully it will work :-)

qcomlnxci · 2026-08-21T04:24:32Z

Test Coral run workflow

Test jobs for commit `d3973df`

qcomdistro: multimedia image-prop
Pass: 44 | Fail: 0 | Total: 44
qcomdistro: multimedia image
Pass: 9 | Fail: 0 | Total: 9

Viswanath Kraleti (vkraleti) · 2026-08-24T05:38:48Z

Dmitry Baryshkov (@lumag) Ricardo Salveti (@ricardosalveti) KVM enablement for QCS6490 is planned for the upcoming release, and we are running short on time to complete the full L4 test cycle. Could you please review this PR and let me know if you see any issues or required modifications?

As you are already aware, supporting both hypervisors is being tracked in another PR, on which we can continue discussions for a clean switching solution.

Dmitry Baryshkov (lumag) · 2026-08-24T13:09:07Z

KVM enablement for QCS6490 is planned for the upcoming release,

We have two different items here. KVM enablement and KVM being a default. Could we separate them? I don't think we require KVM being a default for completing L4 testing?

Viswanath Kraleti (vkraleti) · 2026-08-25T08:44:22Z

KVM enablement for QCS6490 is planned for the upcoming release,

We have two different items here. KVM enablement and KVM being a default. Could we separate them? I don't think we require KVM being a default for completing L4 testing?

Commitment for Sep release is to switch to default KVM and perform complete L4 testing on KVM.

Dmitry Baryshkov (lumag) · 2026-08-25T12:55:05Z

KVM enablement for QCS6490 is planned for the upcoming release,

We have two different items here. KVM enablement and KVM being a default. Could we separate them? I don't think we require KVM being a default for completing L4 testing?

Commitment for Sep release is to switch to default KVM and perform complete L4 testing on KVM.

This means it must be implemented correctly. No shortcuts,

Viswanath Kraleti (vkraleti) · 2026-09-01T17:35:23Z

Dmitry Baryshkov (@lumag) Ricardo Salveti (@ricardosalveti) as discussed over the call with sahitya-tummala, I updated the commit messages in the current PR and also created #3052 to add Gunyah support in CI. Can you please review?

Ricardo Salveti (ricardosalveti) · 2026-09-01T20:15:04Z

+    "qcs6490-rb3gen2 qcs6490-rb3gen2-industrial-mezzanine kodiak-el2 qcs6490-rb3gen2-industrial-mezzanine-staging"
 FIT_DTB_COMPATIBLE[qcom_qcs6490-iot-subtype9-staging] = \
-    "qcs6490-rb3gen2 qcs6490-rb3gen2-industrial-mezzanine kodiak-staging qcs6490-rb3gen2-industrial-mezzanine-staging"
+    "qcs6490-rb3gen2 qcs6490-rb3gen2-industrial-mezzanine kodiak-el2 qcs6490-rb3gen2-industrial-mezzanine-staging"


kodiak-staging removed on both lines here.

Ricardo Salveti (ricardosalveti) · 2026-09-01T20:17:58Z

linux-yocto builds will boot without the el2 overlay and with the kvm firmware, that will be broken (lemans is also broken similarly today).

Ricardo Salveti (ricardosalveti) · 2026-09-01T21:32:48Z

It seems it is not really working correctly on rb3gen2, ADSP seems to be failing, and iris seems to be giving errors as well.

Dmitry Baryshkov (lumag) · 2026-09-02T01:03:18Z

-FIT_DTB_COMPATIBLE[qcom_qcm6490-idp-staging] = "qcm6490-idp kodiak-staging"
-FIT_DTB_COMPATIBLE[qcom_qcm6490-idp-el2kvm] = "qcm6490-idp kodiak-el2"
+FIT_DTB_COMPATIBLE[qcom_qcm6490-idp] = "qcm6490-idp kodiak-el2"
+FIT_DTB_COMPATIBLE[qcom_qcm6490-idp-staging] = "qcm6490-idp kodiak-el2 kodiak-staging"


Don't reorder the lines. It's impossible to review your changes. If you want to retain a certain order, split the reordering into a separate commit.

Broke this commit into two, for easy review.

qcomlnxci · 2026-09-02T04:59:25Z

Test Coral run workflow

Test jobs for commit `373420d`

qcomdistro: multimedia image-prop
Pass: 21 | Fail: 0 | Total: 21
qcomdistro: multimedia image
Pass: 9 | Fail: 0 | Total: 9

qcomlnxci · 2026-09-02T09:55:42Z

Test Coral run workflow

Test jobs for commit `24d0264`

qcomdistro: multimedia image
Pass: 1 | Fail: 0 | Total: 1

Dmitry Baryshkov (lumag) · 2026-09-02T13:57:59Z


+# ---------- glymur ----------
+FIT_DTB_COMPATIBLE[qcom_glymur-crd-staging] = "glymur-crd glymur-staging"
+FIT_DTB_COMPATIBLE[qcom_glymur-crd-camx] = "glymur-crd glymur-crd-camx"


What kind of sorting order do you have in mind? In my opinion, camx comes before staging.

Dmitry Baryshkov (lumag) · 2026-09-02T13:59:52Z

+FIT_DTB_COMPATIBLE[qcom_qcs6490-iot-subtype9] = \
+    "qcs6490-rb3gen2 qcs6490-rb3gen2-industrial-mezzanine"
+
+FIT_DTB_COMPATIBLE[qcom_qcs5430-iot-subtype2] = \


Again, subtype2 < subtype9.

Dmitry Baryshkov (lumag) · 2026-09-02T14:01:15Z

    "qcs6490-rb3gen2 qcs6490-rb3gen2-vision-mezzanine kodiak-staging"

 FIT_DTB_COMPATIBLE[qcom_qcs5430-iot-camx] = \
-    "qcs6490-rb3gen2 qcs5430-fps-camx"


These entries got moved. You wrote that you are changing compats. No mention of moving anything

Dmitry Baryshkov (lumag) · 2026-09-02T14:03:16Z


 # ---------- kodiak ----------
-FIT_DTB_COMPATIBLE[qcom_qcm6490-idp-staging] = "qcm6490-idp kodiak-staging"
+FIT_DTB_COMPATIBLE[qcom_qcm6490-idp-staging] = "qcm6490-idp kodiak-el2 kodiak-staging"


Why is this a separate commit? Why are you adding overlays? Just add -el2gh where applicable. Can you glance at the commit and see what was changed? No. If you just changed the compatible strings, it would have been much easier.

Dmitry Baryshkov (lumag) · 2026-09-02T14:04:08Z

 #
 # Syntax:
 # FIT_DTB_COMPATIBLE[<compatible-encoded>] = "<dtb-stem> [<overlay-stem> [<overlay-stem>...]]"
 #


"Foo, in addition bar" means two different actions. Two separate commits.

qcomlnxci · 2026-09-02T18:59:02Z

Test Coral run workflow

Test jobs for commit `37cc3bb`

qcomdistro: multimedia image
Pass: 9 | Fail: 0 | Total: 9
qcomdistro: multimedia image-prop
Pass: 30 | Fail: 0 | Total: 30

Viswanath Kraleti (vkraleti) · 2026-09-06T02:57:22Z

It seems it is not really working correctly on rb3gen2, ADSP seems to be failing, and iris seems to be giving errors as well.

The issue narrowed down to the devconfig.mbn currently being used. This version doesn't support KVM, preventing the PILs from initializing correctly.

Dmitry Baryshkov (lumag) · 2026-09-07T09:50:30Z

It seems it is not really working correctly on rb3gen2, ADSP seems to be failing, and iris seems to be giving errors as well.

The issue narrowed down to the devconfig.mbn currently being used. This version doesn't support KVM, preventing the PILs from initializing correctly.

And how was KVM tested then?

sahitya-tummala · 2026-09-08T10:50:03Z

It seems it is not really working correctly on rb3gen2, ADSP seems to be failing, and iris seems to be giving errors as well.

The issue narrowed down to the devconfig.mbn currently being used. This version doesn't support KVM, preventing the PILs from initializing correctly.

And how was KVM tested then?

The issue is with devcfg.mbn, but other devcfg variants its fine and those other devcfg variants are for internal consumption only, not to be released externally. Hence, a new FW bin is being released with the fix to devcfg.mbn, which is the right one to use on Kodiak. The fix is part of #3069.

Viswanath Kraleti (@vkraleti) pls rebase your change on that and trigger the CI tests again, these should pass now. Note that the above PR also has boot changes to update efivar with el2gh/el2kvm based on the XBL image flashed.

Dmitry Baryshkov (lumag) · 2026-09-08T15:19:14Z

And how was KVM tested then?

The issue is with devcfg.mbn, but other devcfg variants its fine and those other devcfg variants are for internal consumption only, not to be released externally. Hence, a new FW bin is being released with the fix to devcfg.mbn, which is the right one to use on Kodiak. The fix is part of #3069.

This is all fine, but how was this PR tested? Why was it not tested with the devcfg.mbn that we have in meta-qcom?

Viswanath Kraleti (@vkraleti) should we treat your PRs as completely untested and thus requiring more scrunity?

Viswanath Kraleti (vkraleti) · 2026-09-10T00:50:57Z

And how was KVM tested then?

The issue is with devcfg.mbn, but other devcfg variants its fine and those other devcfg variants are for internal consumption only, not to be released externally. Hence, a new FW bin is being released with the fix to devcfg.mbn, which is the right one to use on Kodiak. The fix is part of #3069.

This is all fine, but how was this PR tested? Why was it not tested with the devcfg.mbn that we have in meta-qcom?

Viswanath Kraleti (Viswanath Kraleti (@vkraleti)) should we treat your PRs as completely untested and thus requiring more scrunity?

Due to HLOS and nHLOS interdependencies (both are developed in different environments) this couldn't be tested with the devcfg.mbn present in meta-qcom. Instead it was validated with the internal builds with an expectation that meta-qcom CI can validate with published bins. #2939 is supposed to bring in nHLOS changes how ever it was an integration miss.

Dmitry Baryshkov (lumag) · 2026-09-10T04:46:42Z

Due to HLOS and nHLOS interdependencies (both are developed in different environments) this couldn't be tested with the devcfg.mbn present in meta-qcom.

Was this ever mentioned in the PR description or in the commit message? How was this supposed to be merged at all if this PR was opened before the NHLOS update?

The el2gh suffix selects the Gunyah hypervisor variant of a board's compatible string, the same way el2kvm selects the KVM variant. Like camx and staging, it is a feature/hypervisor selector rather than board metadata, so it has no corresponding node in qcom-metadata.dtb. test_fitimage_compatible_metadata_validation validates every dash-separated suffix of the generated ITS compatible strings against the metadata node names, and so already fails today on the pre-existing el2gh entries in fit-dtb-compatible-linux-qcom.inc. Add el2gh to the skip set to match the metadata-check script's blacklist, and to COMPAT_EXTENSIONS so the unit-level fixtures stay in sync. Signed-off-by: Viswanath Kraleti <viswanath.kraleti@oss.qualcomm.com>

KVM is the preffered hypervisor for Qualcomm Linux SoCs. Gunyah was used as an interim solution till KVM is fully functional. Now that KVM support on Rb3Gen2 Core Kit has been validated, it no longer requires Gunyah as an interim solution. Add 'kvm' to MACHINE_FEATURES so that the KVM-specific XBL configuration is selected during boot. This switches the default hypervisor to KVM and aligns Rb3Gen2 Core Kit with IQ-615-EVK, IQ-8275-EVK, and IQ-9075-EVK. Signed-off-by: Viswanath Kraleti <viswanath.kraleti@oss.qualcomm.com>

KVM is the preffered hypervisor for Qualcomm Linux SoCs. Gunyah was used as an interim solution till KVM is fully functional. Now that KVM support on QCM6490-IDP has been validated, it no longer requires Gunyah as an interim solution. Add 'kvm' to MACHINE_FEATURES so that the KVM-specific XBL configuration is selected during boot. This switches the default hypervisor to KVM and aligns QCM6490-IDP with IQ-615-EVK, IQ-8275-EVK, and IQ-9075-EVK. Signed-off-by: Viswanath Kraleti <viswanath.kraleti@oss.qualcomm.com>

Currently FIT_DTB_COMPATIBLE entries in fit-dtb-compatible-linux-qcom.inc and fit-dtb-compatible.inc are not sorted and it is hard to identify missing and duplicate entires. Group them per SoC for easier navigation. Within each SoC section, compatible string entries containing el2gh string (indicating Gunyah hypervisor usage) are further grouped together and labeled for easier identification. No entries were added, removed, or changed, so there is no functional impact. Signed-off-by: Viswanath Kraleti <viswanath.kraleti@oss.qualcomm.com>

Kodiak FIT_DTB_COMPATIBLE entries currently use el2kvm-specific compatible strings to load el2.dtbo. As KVM is the default hypervisor now, update the compatible entries to load kodiak-el2.dtbo without requiring an el2kvm suffix. Introduce dedicated el2gh variants for Gunyah configurations and group them under the corresponding Gunyah compatible strings. After dropping el2kvm suffix from Kodiak FIT_DTB_COMPATIBLE keys, four keys, qcom_qcs5430-iot-camx, qcom_qcs5430-iot-subtype2-camx, qcom_qcs6490-iot-camx and qcom_qcs6490-iot-subtype2-camx each defined twice with different values. Drop the stale first occurrence of each of the four keys, keeping the kodiak-el2-inclusive value that these are supposed to be resolving to. Signed-off-by: Viswanath Kraleti <viswanath.kraleti@oss.qualcomm.com>

Viswanath Kraleti (vkraleti) · 2026-09-11T10:23:53Z

Dmitry Baryshkov (@lumag) Ricardo Salveti (@ricardosalveti) updated nHLOS is consumed by meta-qcom and boot tests on Rb3Gen2 are successful. Can you please review one moretime?

Dmitry Baryshkov (lumag) · 2026-09-11T14:11:24Z

Let's wait for the tests to conclude

Dmitry Baryshkov (lumag) · 2026-09-11T14:15:31Z

-FIT_DTB_COMPATIBLE[qcom_qcm6490-idp-el2kvm] = "qcm6490-idp kodiak-el2"
-FIT_DTB_COMPATIBLE[qcom_qcm6490-idp-staging] = "qcm6490-idp kodiak-staging"
+FIT_DTB_COMPATIBLE[qcom_qcm6490-idp] = "qcm6490-idp kodiak-el2"
+FIT_DTB_COMPATIBLE[qcom_qcm6490-idp-staging] = "qcm6490-idp kodiak-el2 kodiak-staging"


I think it was written several times. Don't mix functional changes and refactoring / reordering. This commit really should have only one kind of changes: drop -el2kvm if it's a part of the compat string, otherwise add -el2gh. No reordering, no moving, etc.

qcomlnxci · 2026-09-11T18:59:12Z

Test Coral run workflow

Test jobs for commit `62eb8a7`

qcomdistro: multimedia image-prop
Pass: 41 | Fail: 0 | Total: 41
qcomdistro: multimedia image
Pass: 9 | Fail: 0 | Total: 9

Viswanath Kraleti (vkraleti) requested review from Anuj Mittal (anujm1), Koen Kooi (koenkooi), Dmitry Baryshkov (lumag), Milosz Wasilewski (mwasilew), Nicolas Dechesne (ndechesne), Jose Quaresma (quaresmajose) and Ricardo Salveti (ricardosalveti) as code owners August 5, 2026 11:02

Jose Quaresma (quaresmajose) previously approved these changes Aug 5, 2026

View reviewed changes

Dmitry Baryshkov (lumag) requested changes Aug 5, 2026

View reviewed changes

Comment thread .github/workflows/build-yocto.yml

Comment thread .github/workflows/build-yocto.yml Outdated

Viswanath Kraleti (vkraleti) dismissed Jose Quaresma (quaresmajose)’s stale review via 7d56df9 August 19, 2026 05:20

Viswanath Kraleti (vkraleti) force-pushed the kodiak-kvm branch 2 times, most recently from 7d56df9 to a0d5c14 Compare August 19, 2026 05:27

Dmitry Baryshkov (lumag) requested changes Aug 19, 2026

View reviewed changes

Viswanath Kraleti (vkraleti) force-pushed the kodiak-kvm branch 2 times, most recently from c9890b0 to d3973df Compare August 20, 2026 10:55

Viswanath Kraleti (vkraleti) force-pushed the kodiak-kvm branch from d3973df to b6c9efc Compare September 1, 2026 16:18

Viswanath Kraleti (vkraleti) changed the title ~~Enable KVM by default on Rb3Gen2-Core-Kit and QCM6490-IDP~~ Switch to KVM hypervisor on Rb3Gen2-Core-Kit and QCM6490-IDP Sep 1, 2026

Viswanath Kraleti (vkraleti) force-pushed the kodiak-kvm branch from b6c9efc to 373420d Compare September 1, 2026 16:48

Viswanath Kraleti (vkraleti) added the backport wrynose label Sep 1, 2026

Ricardo Salveti (ricardosalveti) reviewed Sep 1, 2026

View reviewed changes

Comment thread conf/machine/include/fit-dtb-compatible-linux-qcom.inc

Dmitry Baryshkov (lumag) requested changes Sep 2, 2026

View reviewed changes

Viswanath Kraleti (vkraleti) force-pushed the kodiak-kvm branch 2 times, most recently from 24d0264 to 37cc3bb Compare September 2, 2026 09:53

Dmitry Baryshkov (lumag) requested changes Sep 2, 2026

View reviewed changes

Viswanath Kraleti (vkraleti) force-pushed the kodiak-kvm branch from 37cc3bb to 457c794 Compare September 11, 2026 06:42

Viswanath Kraleti (vkraleti) added 5 commits September 11, 2026 12:13

Viswanath Kraleti (vkraleti) force-pushed the kodiak-kvm branch from 457c794 to 62eb8a7 Compare September 11, 2026 06:43

Viswanath Kraleti (vkraleti) added this to the qli-2.1 pull-request freeze milestone Sep 11, 2026

Dmitry Baryshkov (lumag) approved these changes Sep 11, 2026

View reviewed changes

Dmitry Baryshkov (lumag) requested changes Sep 11, 2026

View reviewed changes

Uh oh!

Conversation

Viswanath Kraleti (vkraleti) commented Aug 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Uh oh!

qcomlnxci commented Aug 5, 2026

Test Coral run workflow

Test jobs for commit c4dcacb

Uh oh!

github-actions Bot commented Aug 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Test run workflow

Test jobs for commit 62eb8a7

Uh oh!

test-reporting-app Bot commented Aug 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Test Results

Uh oh!

qcomlnxci commented Aug 19, 2026

Test Coral run workflow

Test jobs for commit a0d5c14

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Viswanath Kraleti (vkraleti) Aug 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

qcomlnxci commented Aug 21, 2026

Test Coral run workflow

Test jobs for commit d3973df

Uh oh!

Viswanath Kraleti (vkraleti) commented Aug 24, 2026

Uh oh!

Dmitry Baryshkov (lumag) commented Aug 24, 2026

Uh oh!

Viswanath Kraleti (vkraleti) commented Aug 25, 2026

Uh oh!

Dmitry Baryshkov (lumag) commented Aug 25, 2026

Uh oh!

Viswanath Kraleti (vkraleti) commented Sep 1, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Ricardo Salveti (ricardosalveti) commented Sep 1, 2026

Uh oh!

Ricardo Salveti (ricardosalveti) commented Sep 1, 2026

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

qcomlnxci commented Sep 2, 2026

Test Coral run workflow

Test jobs for commit 373420d

Uh oh!

qcomlnxci commented Sep 2, 2026

Test Coral run workflow

Test jobs for commit 24d0264

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Viswanath Kraleti (vkraleti) commented Aug 5, 2026 •

edited

Loading

Test jobs for commit `c4dcacb`

github-actions Bot commented Aug 19, 2026 •

edited

Loading

Test jobs for commit `62eb8a7`

test-reporting-app Bot commented Aug 19, 2026 •

edited

Loading

Test jobs for commit `a0d5c14`

Viswanath Kraleti (vkraleti) Aug 20, 2026 •

edited

Loading

Test jobs for commit `d3973df`

Test jobs for commit `373420d`

Test jobs for commit `24d0264`

Test jobs for commit `37cc3bb`

sahitya-tummala commented Sep 8, 2026 •

edited

Loading

Viswanath Kraleti (vkraleti) commented Sep 11, 2026 •

edited

Loading

Test jobs for commit `62eb8a7`