kata: build on arm

[Redent0r]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

What does the PR accomplish, why was it needed?

Change Log

• Change
• Change
• Change

Does this affect the toolchain?

YES/NO

Associated issues

• #xxxx

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-YYYY-XXXX

Test Methodology

• Pipeline build id: xxxx

[CBL-Mariner-Bot]

✅ PR Check Passed

No critical issues detected in spec file changes.

🤖 AI Analysis Summary:

Brief Analysis:
These changes primarily add support for an aarch64 build across several kernel and cloud‐hypervisor spec files and update related changelogs. No explicit CVE patch files (in the “Patch: CVE-YYYY-XXXXX.patch” format) are referenced or applied, so the CVE fix process remains unchanged.

Critical Issues Found:
• No CVE patch directives were found, yet previous changelog CVE references (if any) should be verified against available patch files.
• Some “todo:” comments (e.g., updating cargo feature flags for aarch64) indicate incomplete configuration.

Recommended Actions:
– Verify that any CVE fix mentioned in past changelogs is fully tracked in your package’s patch directory.
– Confirm that the “todo” for aarch64 cargo features is resolved before merging.
– Ensure that all new source files (e.g. config_aarch64) are maintained with proper upstream attribution and security review.

---

📋 For detailed analysis and recommendations, check the Azure DevOps pipeline logs.