cloud-hypervisor: upgrade to v51.1.56

[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?
Upgrade cloud-hypervisor to v51.1.56. This requires a corresponding upgrade to kata-containers and kata-containers-preview

Change Log

• cloud-hypervisor
• kata-containers
• kata-containers-preview

Does this affect the toolchain?

NO

Test Methodology

• kata-containers:

  • CI: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1093624&view=results
  • bb: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1093641&view=results
  • image build: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1093666&view=results
  • conformance: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1093770&view=results
  • performance: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1094971&view=results

• kata-containers-preview (tested through CI as kata-containers using this branch 3.0-dev...kata-ci/dom0/scheduled-upgrade-plus-kata-preview):

  • CI: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1093625&view=results
  • bb: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1093640&view=results
    • bb showing we can build kata-containers-preview: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1094980&view=results
  • image build: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1093667&view=results
  • conformance: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1093768&view=results [1 flake test failure due to networking, rerun passed https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1094949&view=results]
  • performance: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1093769&view=results

[Redent0r]

todo: upload sources to mariner cache

[romoh]

LGTM

[sprt]

LGTM, just one nit about the version scheme.

[sprt]

nit: IMO we should use the same version format as kata-containers since there's no reason to use a tilde (pre-release) for this package but not for the other one. The preview semantic is already captured in the package name.

[Redent0r]

Are you saying to use 3.27.0.preview2 instead ? if so, I agree. It would also align with the GH tag https://github.com/microsoft/kata-containers/releases/tag/3.27.0.preview2 (GH doesn't support ~ in the tag) If @romoh agrees, I can follow up with a PR that switches to 3.27.0.preview2 (We'll have to be careful to make sure that 3.27.0~preview2 does not supersedes 3.27.0.preview2 )