build(deps): bump github.com/go-openapi/runtime in /src/runtime

Bumps [github.com/go-openapi/runtime](https://github.com/go-openapi/runtime) from 0.28.0 to 0.29.3.
- [Release notes](https://github.com/go-openapi/runtime/releases)
- [Commits](https://github.com/go-openapi/runtime/compare/v0.28.0...v0.29.3)

---
updated-dependencies:
- dependency-name: github.com/go-openapi/runtime
  dependency-version: 0.29.3
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

.github/workflows/actionlint.yaml

@@ -23,5 +23,3 @@ jobs:
 
       - name: Run actionlint
         uses: raven-actions/actionlint@e01d1ea33dd6a5ed517d95b4c0c357560ac6f518  # v2.1.1
-        with:
-          version: '1.7.12'

.github/workflows/basic-ci-amd64.yaml

@@ -35,7 +35,7 @@ jobs:
       KATA_HYPERVISOR: ${{ matrix.vmm }}
       SANDBOXER: "shim"
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0
@@ -96,7 +96,7 @@ jobs:
       KATA_HYPERVISOR: ${{ matrix.vmm }}
       SANDBOXER: "podsandbox"
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0
@@ -141,7 +141,7 @@ jobs:
       GOPATH: ${{ github.workspace }}
       KATA_HYPERVISOR: ${{ matrix.vmm }}
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0
@@ -195,7 +195,7 @@ jobs:
     env:
       KATA_HYPERVISOR: ${{ matrix.vmm }}
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0
@@ -242,7 +242,7 @@ jobs:
       GOPATH: ${{ github.workspace }}
       KATA_HYPERVISOR: ${{ matrix.vmm }}
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0
@@ -269,51 +269,6 @@ jobs:
         timeout-minutes: 15
         run: bash tests/functional/vfio/gha-run.sh run
 
-  run-docker-tests:
-    name: run-docker-tests
-    strategy:
-      # We can set this to true whenever we're 100% sure that
-      # all the tests are not flaky, otherwise we'll fail them
-      # all due to a single flaky instance.
-      fail-fast: false
-      matrix:
-        vmm:
-          - qemu
-          - qemu-runtime-rs
-    runs-on: ubuntu-22.04
-    env:
-      KATA_HYPERVISOR: ${{ matrix.vmm }}
-    steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
-        with:
-          ref: ${{ inputs.commit-hash }}
-          fetch-depth: 0
-          persist-credentials: false
-
-      - name: Rebase atop of the latest target branch
-        run: |
-          ./tests/git-helper.sh "rebase-atop-of-the-latest-target-branch"
-        env:
-          TARGET_BRANCH: ${{ inputs.target-branch }}
-
-      - name: Install dependencies
-        run: bash tests/integration/docker/gha-run.sh install-dependencies
-        env:
-          GH_TOKEN: ${{ github.token }}
-
-      - name: get-kata-tarball
-        uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4.3.0
-        with:
-          name: kata-static-tarball-amd64${{ inputs.tarball-suffix }}
-          path: kata-artifacts
-
-      - name: Install kata
-        run: bash tests/integration/docker/gha-run.sh install-kata kata-artifacts
-
-      - name: Run docker smoke test
-        timeout-minutes: 5
-        run: bash tests/integration/docker/gha-run.sh run
-
   run-nerdctl-tests:
     name: run-nerdctl-tests
     strategy:
@@ -332,7 +287,7 @@ jobs:
     env:
       KATA_HYPERVISOR: ${{ matrix.vmm }}
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0
@@ -379,7 +334,7 @@ jobs:
     name: run-kata-agent-apis
     runs-on: ubuntu-22.04
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0

.github/workflows/basic-ci-s390x.yaml

@@ -35,7 +35,7 @@ jobs:
       KATA_HYPERVISOR: ${{ matrix.vmm }}
       SANDBOXER: "shim"
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0
@@ -96,7 +96,7 @@ jobs:
       KATA_HYPERVISOR: ${{ matrix.vmm }}
       SANDBOXER: "podsandbox"
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0
@@ -123,46 +123,3 @@ jobs:
       - name: Run containerd-stability tests
         timeout-minutes: 15
         run: bash tests/stability/gha-run.sh run
-
-  run-docker-tests:
-    name: run-docker-tests
-    strategy:
-      # We can set this to true whenever we're 100% sure that
-      # all the tests are not flaky, otherwise we'll fail them
-      # all due to a single flaky instance.
-      fail-fast: false
-      matrix:
-        vmm:
-          - qemu
-          - qemu-runtime-rs
-    runs-on: s390x-large
-    env:
-      KATA_HYPERVISOR: ${{ matrix.vmm }}
-    steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
-        with:
-          ref: ${{ inputs.commit-hash }}
-          fetch-depth: 0
-          persist-credentials: false
-
-      - name: Rebase atop of the latest target branch
-        run: |
-          ./tests/git-helper.sh "rebase-atop-of-the-latest-target-branch"
-        env:
-          TARGET_BRANCH: ${{ inputs.target-branch }}
-
-      - name: Install dependencies
-        run: bash tests/integration/docker/gha-run.sh install-dependencies
-
-      - name: get-kata-tarball
-        uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4.3.0
-        with:
-          name: kata-static-tarball-s390x${{ inputs.tarball-suffix }}
-          path: kata-artifacts
-
-      - name: Install kata
-        run: bash tests/integration/docker/gha-run.sh install-kata kata-artifacts
-
-      - name: Run docker smoke test
-        timeout-minutes: 5
-        run: bash tests/integration/docker/gha-run.sh run

.github/workflows/build-checks-preview-riscv64.yaml

@@ -72,7 +72,7 @@ jobs:
           sudo rm -f /tmp/kata_hybrid*  # Sometime we got leftover from test_setup_hvsock_failed()
 
       - name: Checkout the code
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           fetch-depth: 0
           persist-credentials: false

.github/workflows/build-checks.yaml

@@ -84,7 +84,7 @@ jobs:
           sudo rm -f /tmp/kata_hybrid*  # Sometime we got leftover from test_setup_hvsock_failed()
 
       - name: Checkout the code
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           fetch-depth: 0
           persist-credentials: false

.github/workflows/build-kata-static-tarball-amd64.yaml

@@ -75,7 +75,7 @@ jobs:
           username: ${{ vars.QUAY_DEPLOYER_USERNAME }}
           password: ${{ secrets.QUAY_DEPLOYER_PASSWORD }}
 
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0 # This is needed in order to keep the commit ids history
@@ -178,7 +178,7 @@ jobs:
           username: ${{ vars.QUAY_DEPLOYER_USERNAME }}
           password: ${{ secrets.QUAY_DEPLOYER_PASSWORD }}
 
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0 # This is needed in order to keep the commit ids history
@@ -272,7 +272,7 @@ jobs:
           username: ${{ vars.QUAY_DEPLOYER_USERNAME }}
           password: ${{ secrets.QUAY_DEPLOYER_PASSWORD }}
 
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0 # This is needed in order to keep the commit ids history
@@ -326,7 +326,7 @@ jobs:
       contents: read
       packages: write
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0
@@ -391,7 +391,7 @@ jobs:
           username: ${{ vars.QUAY_DEPLOYER_USERNAME }}
           password: ${{ secrets.QUAY_DEPLOYER_PASSWORD }}
 
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0 # This is needed in order to keep the commit ids history
@@ -436,7 +436,7 @@ jobs:
       contents: read
       packages: write
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0

.github/workflows/build-kata-static-tarball-arm64.yaml

@@ -64,7 +64,7 @@ jobs:
           username: ${{ vars.QUAY_DEPLOYER_USERNAME }}
           password: ${{ secrets.QUAY_DEPLOYER_PASSWORD }}
 
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0 # This is needed in order to keep the commit ids history
@@ -162,7 +162,7 @@ jobs:
           username: ${{ vars.QUAY_DEPLOYER_USERNAME }}
           password: ${{ secrets.QUAY_DEPLOYER_PASSWORD }}
 
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0 # This is needed in order to keep the commit ids history
@@ -253,7 +253,7 @@ jobs:
           username: ${{ vars.QUAY_DEPLOYER_USERNAME }}
           password: ${{ secrets.QUAY_DEPLOYER_PASSWORD }}
 
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0 # This is needed in order to keep the commit ids history
@@ -305,7 +305,7 @@ jobs:
       contents: read
       packages: write
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0

.github/workflows/build-kata-static-tarball-ppc64le.yaml

@@ -51,7 +51,7 @@ jobs:
           username: ${{ vars.QUAY_DEPLOYER_USERNAME }}
           password: ${{ secrets.QUAY_DEPLOYER_PASSWORD }}
 
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0 # This is needed in order to keep the commit ids history
@@ -109,7 +109,7 @@ jobs:
           username: ${{ vars.QUAY_DEPLOYER_USERNAME }}
           password: ${{ secrets.QUAY_DEPLOYER_PASSWORD }}
 
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0 # This is needed in order to keep the commit ids history
@@ -184,7 +184,7 @@ jobs:
           username: ${{ vars.QUAY_DEPLOYER_USERNAME }}
           password: ${{ secrets.QUAY_DEPLOYER_PASSWORD }}
 
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0 # This is needed in order to keep the commit ids history
@@ -240,7 +240,7 @@ jobs:
         run: |
           sudo chown -R "$USER":"$USER" "$GITHUB_WORKSPACE"
 
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0

.github/workflows/build-kata-static-tarball-riscv64.yaml

@@ -38,7 +38,7 @@ jobs:
           - kernel
           - virtiofsd
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0 # This is needed in order to keep the commit ids history

.github/workflows/build-kata-static-tarball-s390x.yaml

@@ -58,7 +58,7 @@ jobs:
           username: ${{ vars.QUAY_DEPLOYER_USERNAME }}
           password: ${{ secrets.QUAY_DEPLOYER_PASSWORD }}
 
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0 # This is needed in order to keep the commit ids history
@@ -143,7 +143,7 @@ jobs:
           username: ${{ vars.QUAY_DEPLOYER_USERNAME }}
           password: ${{ secrets.QUAY_DEPLOYER_PASSWORD }}
 
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0 # This is needed in order to keep the commit ids history
@@ -196,7 +196,7 @@ jobs:
       contents: read
       packages: write
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           persist-credentials: false
       - name: Rebase atop of the latest target branch
@@ -270,7 +270,7 @@ jobs:
           username: ${{ vars.QUAY_DEPLOYER_USERNAME }}
           password: ${{ secrets.QUAY_DEPLOYER_PASSWORD }}
 
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0 # This is needed in order to keep the commit ids history
@@ -328,7 +328,7 @@ jobs:
       contents: read
       packages: write
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0

.github/workflows/build-kubectl-image.yaml

@@ -28,7 +28,7 @@ jobs:
       packages: write
     steps:
       - name: Checkout repository
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           persist-credentials: false
 

.github/workflows/cargo-deny-runner.yaml

@@ -20,7 +20,7 @@ jobs:
 
     steps:
       - name: Checkout Code
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           persist-credentials: false
       - name: Generate Action

.github/workflows/ci-weekly.yaml

@@ -73,7 +73,7 @@ jobs:
     runs-on: ubuntu-22.04
     steps:
       - name: Checkout code
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0

.github/workflows/ci.yaml

@@ -182,7 +182,7 @@ jobs:
     runs-on: ubuntu-22.04
     steps:
       - name: Checkout code
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0

.github/workflows/cleanup-resources.yaml

@@ -12,11 +12,9 @@ jobs:
     runs-on: ubuntu-22.04
     permissions:
       id-token: write # Used for OIDC access to log into Azure
-    environment:
-      name: ci
-      deployment: false
+    environment: ci
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           persist-credentials: false
 

.github/workflows/codeql.yml

@@ -60,7 +60,7 @@ jobs:
         # your codebase is analyzed, see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages
     steps:
     - name: Checkout repository
-      uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
       with:
         persist-credentials: false
 

.github/workflows/darwin-tests.yaml

@@ -27,7 +27,7 @@ jobs:
         echo "$HOME/.local/bin" >> "${GITHUB_PATH}"
 
     - name: Checkout code
-      uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
       with:
         persist-credentials: false
 

.github/workflows/docs-url-alive-check.yaml

@@ -19,7 +19,7 @@ jobs:
       run: |
         echo "GOPATH=${GITHUB_WORKSPACE}" >> "$GITHUB_ENV"
     - name: Checkout code
-      uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
       with:
         fetch-depth: 0
         persist-credentials: false

.github/workflows/editorconfig-checker.yaml

@@ -15,7 +15,7 @@ jobs:
     runs-on: ubuntu-24.04
     steps:
       - name: Checkout the code
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           fetch-depth: 0
           persist-credentials: false

.github/workflows/gatekeeper-skipper.yaml

@@ -42,7 +42,7 @@ jobs:
       skip_test: ${{ steps.skipper.outputs.skip_test }}
       skip_static: ${{ steps.skipper.outputs.skip_static }}
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0

.github/workflows/gatekeeper.yaml

@@ -30,7 +30,7 @@ jobs:
       issues: read
       pull-requests: read
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ github.event.pull_request.head.sha }}
           fetch-depth: 0

.github/workflows/nydus-snapshotter-version-in-sync.yaml

@@ -20,7 +20,7 @@ jobs:
     runs-on: ubuntu-22.04
     steps:
     - name: Checkout code
-      uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
       with:
         persist-credentials: false
     - name: Ensure nydus-snapshotter-version is in sync inside our repo

.github/workflows/payload-after-push.yaml

@@ -145,7 +145,7 @@ jobs:
     needs: [publish-kata-deploy-payload-amd64, publish-kata-deploy-payload-arm64, publish-kata-deploy-payload-s390x, publish-kata-deploy-payload-ppc64le]
     steps:
       - name: Checkout repository
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           persist-credentials: false
 
@@ -171,7 +171,7 @@ jobs:
       packages: write # needed to push the helm chart to ghcr.io
     steps:
       - name: Checkout repository
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           persist-credentials: false
 

.github/workflows/publish-kata-deploy-payload.yaml

@@ -44,7 +44,7 @@ jobs:
       packages: write
     runs-on: ${{ inputs.runner }}
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0

.github/workflows/push-oras-tarball-cache.yaml

@@ -21,7 +21,7 @@ jobs:
       packages: write
     steps:
       - name: Checkout repository
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           fetch-depth: 0
           persist-credentials: false

.github/workflows/release-amd64.yaml

@@ -50,7 +50,7 @@ jobs:
           username: ${{ vars.QUAY_DEPLOYER_USERNAME }}
           password: ${{ secrets.QUAY_DEPLOYER_PASSWORD }}
 
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           persist-credentials: false
       - name: get-kata-tarball

.github/workflows/release-arm64.yaml

@@ -50,7 +50,7 @@ jobs:
           username: ${{ vars.QUAY_DEPLOYER_USERNAME }}
           password: ${{ secrets.QUAY_DEPLOYER_PASSWORD }}
 
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           persist-credentials: false
       - name: get-kata-tarball

.github/workflows/release-ppc64le.yaml

@@ -47,7 +47,7 @@ jobs:
           username: ${{ vars.QUAY_DEPLOYER_USERNAME }}
           password: ${{ secrets.QUAY_DEPLOYER_PASSWORD }}
 
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           persist-credentials: false
       - name: get-kata-tarball

.github/workflows/release-s390x.yaml

@@ -51,7 +51,7 @@ jobs:
           username: ${{ vars.QUAY_DEPLOYER_USERNAME }}
           password: ${{ secrets.QUAY_DEPLOYER_PASSWORD }}
 
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           persist-credentials: false
       - name: get-kata-tarball

.github/workflows/release.yaml

@@ -12,7 +12,7 @@ jobs:
       contents: write # needed for the `gh release create` command
     steps:
       - name: Checkout repository
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           fetch-depth: 0
           persist-credentials: false
@@ -87,7 +87,7 @@ jobs:
       packages: write # needed to push the multi-arch manifest to ghcr.io
     steps:
       - name: Checkout repository
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           persist-credentials: false
 
@@ -124,7 +124,7 @@ jobs:
     runs-on: ubuntu-22.04
     steps:
       - name: Checkout repository
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           persist-credentials: false
 
@@ -206,7 +206,7 @@ jobs:
       contents: write # needed for the `gh release` commands
     steps:
       - name: Checkout repository
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           persist-credentials: false
 
@@ -224,7 +224,7 @@ jobs:
       contents: write # needed for the `gh release` commands
     steps:
       - name: Checkout repository
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           persist-credentials: false
 
@@ -242,7 +242,7 @@ jobs:
       contents: write # needed for the `gh release` commands
     steps:
       - name: Checkout repository
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           persist-credentials: false
 
@@ -261,7 +261,7 @@ jobs:
       packages: write # needed to push the helm chart to ghcr.io
     steps:
       - name: Checkout repository
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           persist-credentials: false
 
@@ -298,7 +298,7 @@ jobs:
       contents: write # needed for the `gh release` commands
     steps:
       - name: Checkout repository
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           persist-credentials: false
 

.github/workflows/run-cri-containerd-tests.yaml

@@ -41,7 +41,7 @@ jobs:
       GOPATH: ${{ github.workspace }}
       KATA_HYPERVISOR: ${{ inputs.vmm }}
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0

.github/workflows/run-k8s-tests-on-aks.yaml

@@ -58,9 +58,7 @@ jobs:
     permissions:
       contents: read
       id-token: write # Used for OIDC access to log into Azure
-    environment:
-      name: ci
-      deployment: false
+    environment: ci
     env:
       DOCKER_REGISTRY: ${{ inputs.registry }}
       DOCKER_REPO: ${{ inputs.repo }}
@@ -73,7 +71,7 @@ jobs:
       GENPOLICY_PULL_METHOD: ${{ matrix.genpolicy-pull-method }}
       RUNS_ON_AKS: "true"
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0

.github/workflows/run-k8s-tests-on-arm64.yaml

@@ -46,7 +46,7 @@ jobs:
       K8S_TEST_HOST_TYPE: all
       TARGET_ARCH: "aarch64"
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0

.github/workflows/run-k8s-tests-on-free-runner.yaml

@@ -63,7 +63,7 @@ jobs:
       CONTAINER_ENGINE_VERSION: ${{ matrix.environment.containerd_version }}
       GH_TOKEN: ${{ github.token }}
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0
@@ -124,3 +124,4 @@ jobs:
         if: always()
         timeout-minutes: 15
         run: bash tests/integration/kubernetes/gha-run.sh cleanup
+

.github/workflows/run-k8s-tests-on-nvidia-gpu.yaml

@@ -53,7 +53,7 @@ jobs:
       USE_EXPERIMENTAL_SNAPSHOTTER_SETUP: ${{ matrix.environment.name == 'nvidia-gpu-snp' && 'true' || 'false' }}
       K8S_TEST_HOST_TYPE: baremetal
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0

.github/workflows/run-k8s-tests-on-ppc64le.yaml

@@ -45,7 +45,7 @@ jobs:
       KUBERNETES: ${{ matrix.k8s }}
       TARGET_ARCH: "ppc64le"
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0

.github/workflows/run-k8s-tests-on-zvsi.yaml

@@ -78,7 +78,7 @@ jobs:
       AUTHENTICATED_IMAGE_USER: ${{ vars.AUTHENTICATED_IMAGE_USER }}
       AUTHENTICATED_IMAGE_PASSWORD: ${{ secrets.AUTHENTICATED_IMAGE_PASSWORD }}
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0

.github/workflows/run-kata-coco-stability-tests.yaml

@@ -55,9 +55,7 @@ jobs:
     permissions:
 
       id-token: write # Used for OIDC access to log into Azure
-    environment:
-      name: ci
-      deployment: false
+    environment: ci
     env:
       DOCKER_REGISTRY: ${{ inputs.registry }}
       DOCKER_REPO: ${{ inputs.repo }}
@@ -74,7 +72,7 @@ jobs:
       AUTHENTICATED_IMAGE_PASSWORD: ${{ secrets.AUTHENTICATED_IMAGE_PASSWORD }}
       SNAPSHOTTER: ${{ matrix.snapshotter }}
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0

.github/workflows/run-kata-coco-tests.yaml

@@ -71,7 +71,7 @@ jobs:
       GH_ITA_KEY: ${{ secrets.ITA_KEY }}
       AUTO_GENERATE_POLICY: "yes"
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0
@@ -144,9 +144,7 @@ jobs:
     runs-on: ubuntu-24.04
     permissions:
       contents: read
-    environment:
-      name: ci
-      deployment: false
+    environment: ci
     env:
       DOCKER_REGISTRY: ${{ inputs.registry }}
       DOCKER_REPO: ${{ inputs.repo }}
@@ -169,7 +167,7 @@ jobs:
       CONTAINER_ENGINE_VERSION: "active"
       GH_TOKEN: ${{ github.token }}
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0
@@ -271,9 +269,7 @@ jobs:
     runs-on: ubuntu-24.04
     permissions:
       contents: read
-    environment:
-      name: ci
-      deployment: false
+    environment: ci
     env:
       DOCKER_REGISTRY: ${{ inputs.registry }}
       DOCKER_REPO: ${{ inputs.repo }}
@@ -292,7 +288,7 @@ jobs:
       K8S_TEST_HOST_TYPE: "all"
       GH_TOKEN: ${{ github.token }}
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0
@@ -383,9 +379,7 @@ jobs:
         pull-type:
           - default
     runs-on: ubuntu-24.04
-    environment:
-      name: ci
-      deployment: false
+    environment: ci
     env:
       DOCKER_REGISTRY: ${{ inputs.registry }}
       DOCKER_REPO: ${{ inputs.repo }}
@@ -408,7 +402,7 @@ jobs:
       AUTO_GENERATE_POLICY: "no"
       GH_TOKEN: ${{ github.token }}
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0

.github/workflows/run-kata-deploy-tests-on-aks.yaml

@@ -48,9 +48,7 @@ jobs:
           - host_os: cbl-mariner
             vmm: clh
     runs-on: ubuntu-22.04
-    environment:
-      name: ci
-      deployment: false
+    environment: ci
     permissions:
       id-token: write # Used for OIDC access to log into Azure
     env:
@@ -62,7 +60,7 @@ jobs:
       KATA_HYPERVISOR: ${{ matrix.vmm }}
       KUBERNETES: "vanilla"
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0

.github/workflows/run-kata-deploy-tests.yaml

@@ -46,7 +46,7 @@ jobs:
       KATA_HYPERVISOR: ${{ matrix.vmm }}
       KUBERNETES: ${{ matrix.k8s }}
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0

.github/workflows/run-kata-monitor-tests.yaml

@@ -40,7 +40,7 @@ jobs:
       #CONTAINERD_VERSION: ${{ matrix.containerd_version }}
       KATA_HYPERVISOR: ${{ matrix.vmm }}
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0

.github/workflows/run-metrics.yaml

@@ -46,7 +46,7 @@ jobs:
       K8S_TEST_HOST_TYPE: "baremetal"
       KUBERNETES: kubeadm
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           ref: ${{ inputs.commit-hash }}
           fetch-depth: 0

.github/workflows/scorecard.yaml

@@ -27,7 +27,7 @@ jobs:
 
     steps:
       - name: "Checkout code"
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           persist-credentials: false
 

.github/workflows/shellcheck.yaml

@@ -22,7 +22,7 @@ jobs:
     runs-on: ubuntu-24.04
     steps:
       - name: Checkout the code
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           fetch-depth: 0
           persist-credentials: false

.github/workflows/shellcheck_required.yaml

@@ -23,7 +23,7 @@ jobs:
     runs-on: ubuntu-24.04
     steps:
       - name: Checkout the code
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           fetch-depth: 0
           persist-credentials: false

.github/workflows/stale_issues.yaml

@@ -1,42 +0,0 @@
-name: 'Stale issues with activity before a fixed date'
-on:
-  schedule:
-    - cron: '0 0 * * *'
-  workflow_dispatch:
-    inputs:
-      date:
-        description: "Date of stale cut-off. All issues not updated since this date will be marked as stale. Format: YYYY-MM-DD e.g. 2022-10-09"
-        default: "2022-10-09"
-        required: false
-        type: string
-
-permissions: {}
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
-  cancel-in-progress: true
-
-jobs:
-  stale:
-    name: stale
-    runs-on: ubuntu-24.04
-    permissions:
-      actions: write # Needed to manage caches for state persistence across runs
-      issues: write # Needed to add/remove labels, post comments, or close issues
-    steps:
-      - name: Calculate the age to stale
-        run: |
-          echo AGE=$(( ( $(date +%s) - $(date -d "${DATE:-2022-10-09}" +%s) ) / 86400 )) >> "$GITHUB_ENV"
-        env:
-          DATE: ${{ inputs.date }}
-
-      - name: Run the stale action
-        uses: actions/stale@5bef64f19d7facfb25b37b414482c7164d639639 # v9.1.0
-        with:
-          stale-pr-message: 'This issue has had no activity since before ${DATE}. Please comment on the issue, or it will be closed in 30 days'
-          days-before-pr-stale: -1
-          days-before-pr-close: -1
-          days-before-issue-stale: ${AGE}
-          days-before-issue-close: 30
-        env:
-          DATE: ${{ inputs.date }}

.github/workflows/static-checks.yaml

@@ -28,7 +28,7 @@ jobs:
     runs-on: ubuntu-22.04
     steps:
       - name: Checkout the code
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           fetch-depth: 0
           persist-credentials: false
@@ -71,7 +71,7 @@ jobs:
             component-path: src/dragonball
     steps:
       - name: Checkout the code
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           fetch-depth: 0
           persist-credentials: false
@@ -115,7 +115,7 @@ jobs:
       packages: write # for push to ghcr.io
     steps:
       - name: Checkout code
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           fetch-depth: 0
           persist-credentials: false
@@ -171,7 +171,7 @@ jobs:
       contents: read  # for checkout
     steps:
       - name: Checkout code
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           fetch-depth: 0
           persist-credentials: false

.github/workflows/zizmor.yaml

@@ -15,7 +15,7 @@ jobs:
     runs-on: ubuntu-22.04
     steps:
       - name: Checkout repository
-        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
         with:
           fetch-depth: 0
           persist-credentials: false

Cargo.toml

@@ -6,12 +6,6 @@ rust-version = "1.88"
 
 [workspace]
 members = [
-  # kata-agent
-  "src/agent",
-  "src/agent/rustjail",
-  "src/agent/policy",
-  "src/agent/vsock-exporter",
-
   # Dragonball
   "src/dragonball",
   "src/dragonball/dbs_acpi",
@@ -47,6 +41,7 @@ resolver = "2"
 
 # TODO: Add all excluded crates to root workspace
 exclude = [
+  "src/agent",
   "src/tools",
   "src/libs",
 
@@ -109,7 +104,6 @@ wasm_container = { path = "src/runtime-rs/crates/runtimes/wasm_container" }
 kata-sys-util = { path = "src/libs/kata-sys-util" }
 kata-types = { path = "src/libs/kata-types", features = ["safe-path"] }
 logging = { path = "src/libs/logging" }
-mem-agent = { path = "src/libs/mem-agent" }
 protocols = { path = "src/libs/protocols", features = ["async"] }
 runtime-spec = { path = "src/libs/runtime-spec" }
 safe-path = { path = "src/libs/safe-path" }
@@ -118,65 +112,35 @@ test-utils = { path = "src/libs/test-utils" }
 
 # Local dependencies from `src/agent`
 kata-agent-policy = { path = "src/agent/policy" }
-rustjail = { path = "src/agent/rustjail" }
-vsock-exporter = { path = "src/agent/vsock-exporter" }
 
 # Outside dependencies
 actix-rt = "2.7.0"
 anyhow = "1.0"
-async-recursion = "0.3.2"
 async-trait = "0.1.48"
-capctl = "0.2.0"
-cfg-if = "1.0.0"
-cgroups = { package = "cgroups-rs", git = "https://github.com/kata-containers/cgroups-rs", rev = "v0.3.5" }
-clap = { version = "4.5.40", features = ["derive"] }
-const_format = "0.2.30"
 containerd-shim = { version = "0.10.0", features = ["async"] }
 containerd-shim-protos = { version = "0.10.0", features = ["async"] }
-derivative = "2.2.0"
-futures = "0.3.30"
 go-flag = "0.1.0"
 hyper = "0.14.20"
 hyperlocal = "0.8.0"
-ipnetwork = "0.17.0"
 lazy_static = "1.4"
-libc = "0.2.94"
+libc = "0.2"
 log = "0.4.14"
-netlink-packet-core = "0.7.0"
-netlink-packet-route = "0.19.0"
-netlink-sys = { version = "0.7.0", features = ["tokio_socket"] }
 netns-rs = "0.1.0"
 # Note: nix needs to stay sync'd with libs versions
 nix = "0.26.4"
 oci-spec = { version = "0.8.1", features = ["runtime"] }
-opentelemetry = { version = "0.17.0", features = ["rt-tokio"] }
-procfs = "0.12.0"
-prometheus = { version = "0.14.0", features = ["process"] }
 protobuf = "3.7.2"
 rand = "0.8.4"
-regex = "1.10.5"
-rstest = "0.18.0"
-rtnetlink = "0.14.0"
-scan_fmt = "0.2.6"
-scopeguard = "1.0.0"
 serde = { version = "1.0.145", features = ["derive"] }
 serde_json = "1.0.91"
-serial_test = "0.10.0"
 sha2 = "0.10.9"
 slog = "2.5.2"
 slog-scope = "4.4.0"
-slog-stdlog = "4.0.0"
-slog-term = "2.9.0"
 strum = { version = "0.24.0", features = ["derive"] }
-strum_macros = "0.26.2"
 tempfile = "3.19.1"
-thiserror = "1.0.26"
+thiserror = "1.0"
 tokio = "1.46.1"
-tokio-vsock = "0.3.4"
-toml = "0.5.8"
 tracing = "0.1.41"
 tracing-opentelemetry = "0.18.0"
-tracing-subscriber = "0.3.20"
 ttrpc = "0.8.4"
 url = "2.5.4"
-which = "4.3.0"

README.md

@@ -74,7 +74,7 @@ See the [official documentation](docs) including:
 - [Developer guide](docs/Developer-Guide.md)
 - [Design documents](docs/design)
   - [Architecture overview](docs/design/architecture)
-  - [Architecture 4.0 overview](docs/design/architecture_4.0/)
+  - [Architecture 3.0 overview](docs/design/architecture_3.0/)
 
 ## Configuration
 

ci/openshift-ci/README.md

@@ -37,23 +37,6 @@ oc adm policy add-scc-to-group anyuid system:authenticated system:serviceaccount
 oc label --overwrite ns default pod-security.kubernetes.io/enforce=privileged pod-security.kubernetes.io/warn=baseline pod-security.kubernetes.io/audit=baseline
 ```
 
-The e2e suite uses a combination of built-in (origin) and external tests. External
-tests include Kubernetes upstream conformance tests from the `hyperkube` image.
-
-To enable external tests, export a variable matching your cluster version:
-
-```bash
-export EXTENSIONS_PAYLOAD_OVERRIDE=$(oc get clusterversion version -o jsonpath='{.status.desired.image}')
-# Optional: limit to hyperkube only (k8s conformance tests, avoids downloading all operator extensions)
-export EXTENSION_BINARY_OVERRIDE_INCLUDE_TAGS="hyperkube"
-```
-
-Alternatively, skip external tests entirely (only OpenShift-specific tests from origin):
-
-```bash
-export OPENSHIFT_SKIP_EXTERNAL_TESTS=1
-```
-
 Now you should be ready to run the openshift-tests. Our CI only uses a subset
 of tests, to get the current ``TEST_SKIPS`` see
 [the pipeline config](https://github.com/openshift/release/tree/master/ci-operator/config/kata-containers/kata-containers).

ci/openshift-ci/peer-pods-azure.sh

@@ -39,21 +39,6 @@ git_sparse_clone() {
   git checkout FETCH_HEAD
 }
 
-#######################
-# Install prerequisites
-#######################
-if ! command -v helm &>/dev/null; then
-	echo "Helm not installed, installing in current location..."
-	PATH="${PWD}:${PATH}"
-	curl -fsSL https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | HELM_INSTALL_DIR='.' bash -s -- --no-sudo
-fi
-if ! command -v yq &>/dev/null; then
-	echo "yq not installed, installing in current location..."
-	PATH="${PWD}:${PATH}"
-	curl -fsSL https://github.com/mikefarah/yq/releases/latest/download/yq_linux_amd64 -o ./yq
-	chmod +x yq
-fi
-
 ###############################
 # Disable security to allow e2e
 ###############################
@@ -98,6 +83,7 @@ AZURE_REGION=$(az group show --resource-group "${AZURE_RESOURCE_GROUP}" --query
 # Create workload identity
 AZURE_WORKLOAD_IDENTITY_NAME="caa-${AZURE_CLIENT_ID}"
 az identity create   --name "${AZURE_WORKLOAD_IDENTITY_NAME}"   --resource-group "${AZURE_RESOURCE_GROUP}"   --location "${AZURE_REGION}"
+USER_ASSIGNED_CLIENT_ID="$(az identity show --resource-group "${AZURE_RESOURCE_GROUP}" --name "${AZURE_WORKLOAD_IDENTITY_NAME}" --query 'clientId' -otsv)"
 
 
 #############################
@@ -198,36 +184,84 @@ echo "CAA_IMAGE=\"${CAA_IMAGE}\""
 echo "CAA_TAG=\"${CAA_TAG}\""
 echo "PP_IMAGE_ID=\"${PP_IMAGE_ID}\""
 
-# Install cert-manager (prerequisit)
-helm install cert-manager oci://quay.io/jetstack/charts/cert-manager --namespace cert-manager --create-namespace --set crds.enabled=true
-
 # Clone and configure caa
-git_sparse_clone "https://github.com/confidential-containers/cloud-api-adaptor.git" "${CAA_GIT_SHA:-main}" "src/cloud-api-adaptor/install/charts/" "src/peerpod-ctrl/chart" "src/webhook/chart"
+git_sparse_clone "https://github.com/confidential-containers/cloud-api-adaptor.git" "${CAA_GIT_SHA:-main}" "src/cloud-api-adaptor/install/"
 echo "CAA_GIT_SHA=\"$(git rev-parse HEAD)\""
-pushd src/cloud-api-adaptor/install/charts/peerpods
-# Use the latest kata-deploy
-yq -i '( .dependencies[] | select(.name == "kata-deploy") ) .version = "0.0.0-dev"' Chart.yaml
-helm dependency update .
-# Create secrets
-kubectl apply -f - << EOF
-apiVersion: v1
-kind: Namespace
+pushd src/cloud-api-adaptor
+cat <<EOF > install/overlays/azure/workload-identity.yaml
+apiVersion: apps/v1
+kind: DaemonSet
 metadata:
-    name: confidential-containers-system
-    labels:
-        app.kubernetes.io/managed-by: Helm
-    annotations:
-        meta.helm.sh/release-name: peerpods
-        meta.helm.sh/release-namespace: confidential-containers-system
+  name: cloud-api-adaptor-daemonset
+  namespace: confidential-containers-system
+spec:
+  template:
+    metadata:
+      labels:
+        azure.workload.identity/use: "true"
+---
+apiVersion: v1
+kind: ServiceAccount
+metadata:
+  name: cloud-api-adaptor
+  namespace: confidential-containers-system
+  annotations:
+    azure.workload.identity/client-id: "${USER_ASSIGNED_CLIENT_ID}"
 EOF
-kubectl create secret generic my-provider-creds \
-       -n confidential-containers-system \
-       --from-literal=AZURE_CLIENT_ID="$AZURE_CLIENT_ID" \
-       --from-literal=AZURE_CLIENT_SECRET="$AZURE_CLIENT_SECRET" \
-       --from-literal=AZURE_TENANT_ID="$AZURE_TENANT_ID"
-helm install peerpods . -f providers/azure.yaml --set secrets.mode=reference --set secrets.existingSecretName=my-provider-creds --set providerConfigs.azure.AZURE_SUBSCRIPTION_ID="${AZURE_SUBSCRIPTION_ID}" --set providerConfigs.azure.AZURE_REGION="${PP_REGION}" --set providerConfigs.azure.AZURE_INSTANCE_SIZE="Standard_D2as_v5" --set providerConfigs.azure.AZURE_RESOURCE_GROUP="${PP_RESOURCE_GROUP}" --set providerConfigs.azure.AZURE_SUBNET_ID="${PP_SUBNET_ID}" --set providerConfigs.azure.AZURE_IMAGE_ID="${PP_IMAGE_ID}" --set providerConfigs.azure.DISABLECVM="true" --set providerConfigs.azure.PEERPODS_LIMIT_PER_NODE="50" --set kata-deploy.snapshotter.setup= --dependency-update -n confidential-containers-system --create-namespace --wait
-popd	# charts
-popd	# git_sparse_clone CAA
+PP_INSTANCE_SIZE="Standard_D2as_v5"
+DISABLECVM="true"
+cat <<EOF > install/overlays/azure/kustomization.yaml
+apiVersion: kustomize.config.k8s.io/v1beta1
+kind: Kustomization
+bases:
+- ../../yamls
+images:
+- name: cloud-api-adaptor
+  newName: "${CAA_IMAGE}"
+  newTag: "${CAA_TAG}"
+generatorOptions:
+  disableNameSuffixHash: true
+configMapGenerator:
+- name: peer-pods-cm
+  namespace: confidential-containers-system
+  literals:
+  - CLOUD_PROVIDER="azure"
+  - AZURE_SUBSCRIPTION_ID="${AZURE_SUBSCRIPTION_ID}"
+  - AZURE_REGION="${PP_REGION}"
+  - AZURE_INSTANCE_SIZE="${PP_INSTANCE_SIZE}"
+  - AZURE_RESOURCE_GROUP="${PP_RESOURCE_GROUP}"
+  - AZURE_SUBNET_ID="${PP_SUBNET_ID}"
+  - AZURE_IMAGE_ID="${PP_IMAGE_ID}"
+  - DISABLECVM="${DISABLECVM}"
+  - PEERPODS_LIMIT_PER_NODE="50"
+secretGenerator:
+- name: peer-pods-secret
+  namespace: confidential-containers-system
+  envs:
+  - service-principal.env
+- name: ssh-key-secret
+  namespace: confidential-containers-system
+  files:
+  - id_rsa.pub
+patchesStrategicMerge:
+- workload-identity.yaml
+EOF
+ssh-keygen -t rsa -f install/overlays/azure/id_rsa -N ''
+echo "AZURE_CLIENT_ID=${AZURE_CLIENT_ID}" > install/overlays/azure/service-principal.env
+echo "AZURE_CLIENT_SECRET=${AZURE_CLIENT_SECRET}" >> install/overlays/azure/service-principal.env
+echo "AZURE_TENANT_ID=${AZURE_TENANT_ID}" >> install/overlays/azure/service-principal.env
+
+# Deploy Operator
+git_sparse_clone "https://github.com/confidential-containers/operator" "${OPERATOR_SHA:-main}" "config/"
+echo "OPERATOR_SHA=\"$(git rev-parse HEAD)\""
+oc apply -k "config/release"
+oc apply -k "config/samples/ccruntime/peer-pods"
+popd
+
+# Deploy CAA
+kubectl apply -k "install/overlays/azure"
+popd
+popd
 
 # Wait for runtimeclass
 SECONDS=0

docs/Developer-Guide.md

@@ -522,18 +522,10 @@ $ sudo kata-runtime check
 If your system is *not* able to run Kata Containers, the previous command will error out and explain why.
 
 # Run Kata Containers with Containerd
-
 Refer to the [How to use Kata Containers and Containerd](how-to/containerd-kata.md) how-to guide.
 
 # Run Kata Containers with Kubernetes
-
-- Containerd
-
-Refer to the [How to use Kata Containers and Containerd with Kubernetes](how-to/how-to-use-k8s-with-containerd-and-kata.md) how-to guide.
-
-- CRI-O
-
-Refer to the [How to use Kata Containers and CRI-O with Kubernetes](how-to/how-to-use-k8s-with-crio-and-kata.md) how-to guide.
+Refer to the [Run Kata Containers with Kubernetes](how-to/run-kata-with-k8s.md) how-to guide.
 
 # Troubleshoot Kata Containers
 

docs/design/architecture/kubernetes.md

@@ -32,4 +32,4 @@ runtime. Refer to the following guides on how to set up Kata
 Containers with Kubernetes:
 
 - [How to use Kata Containers and containerd](../../how-to/containerd-kata.md)
-- [Run Kata Containers with Kubernetes](../../how-to/how-to-use-k8s-with-crio-and-kata.md)
+- [Run Kata Containers with Kubernetes](../../how-to/run-kata-with-k8s.md)

docs/design/architecture_3.0/README.md

@@ -0,0 +1,168 @@
+# Kata 3.0 Architecture
+## Overview
+In cloud-native scenarios, there is an increased demand for container startup speed, resource consumption, stability, and security, areas where the present Kata Containers runtime is challenged relative to other runtimes. To achieve this, we propose a solid, field-tested and secure Rust version of the kata-runtime.
+
+Also, we provide the following designs:
+
+- Turn key solution with builtin `Dragonball` Sandbox
+- Async I/O to reduce resource consumption
+- Extensible framework for multiple services, runtimes and hypervisors
+- Lifecycle management for sandbox and container associated resources
+
+### Rationale for choosing Rust
+
+We chose Rust because it is designed as a system language with a focus on efficiency.
+In contrast to Go, Rust makes a variety of design trade-offs in order to obtain
+good execution performance, with innovative techniques that, in contrast to C or
+C++, provide reasonable protection against common memory errors (buffer
+overflow, invalid pointers, range errors), error checking (ensuring errors are
+dealt with), thread safety, ownership of resources, and more.
+
+These benefits were verified in our project when the Kata Containers guest agent
+was rewritten in Rust. We notably saw a significant reduction in memory usage
+with the Rust-based implementation.
+
+
+## Design
+### Architecture
+![architecture](./images/architecture.png)
+### Built-in VMM
+#### Current Kata 2.x architecture
+![not_builtin_vmm](./images/not_built_in_vmm.png)
+As shown in the figure, runtime and VMM are separate processes. The runtime process forks the VMM process and interacts through the inter-process RPC. Typically, process interaction consumes more resources than peers within the process, and it will result in relatively low efficiency. At the same time, the cost of resource operation and maintenance should be considered. For example, when performing resource recovery under abnormal conditions, the exception of any process must be detected by others and activate the appropriate resource recovery process. If there are additional processes, the recovery becomes even more difficult.
+#### How To Support Built-in VMM
+We provide `Dragonball` Sandbox to enable built-in VMM by integrating VMM's function into the Rust library. We could perform VMM-related functionalities by using the library. Because runtime and VMM  are in the same process, there is a benefit in terms of message processing speed and API synchronization. It can also guarantee the consistency of the runtime and the VMM life cycle, reducing resource recovery and exception handling maintenance, as shown in the figure:
+![builtin_vmm](./images/built_in_vmm.png)
+### Async Support
+#### Why Need Async
+**Async is already in stable Rust and allows us to write async code**
+
+- Async provides significantly reduced CPU and memory overhead, especially for workloads with a large amount of IO-bound tasks
+- Async is zero-cost in Rust, which means that you only pay for what you use. Specifically, you can use async without heap allocations and dynamic dispatch, which greatly improves efficiency
+- For more (see [Why Async?](https://rust-lang.github.io/async-book/01_getting_started/02_why_async.html) and [The State of Asynchronous Rust](https://rust-lang.github.io/async-book/01_getting_started/03_state_of_async_rust.html)).
+
+**There may be several problems if implementing kata-runtime with Sync Rust**
+
+- Too many threads with a new TTRPC connection
+   - TTRPC threads: reaper thread(1) + listener thread(1) + client handler(2)
+- Add 3 I/O threads with a new container
+- In Sync mode, implementing a timeout mechanism is challenging. For example, in TTRPC API interaction, the timeout mechanism is difficult to align with Golang
+#### How To Support Async
+The kata-runtime is controlled by TOKIO_RUNTIME_WORKER_THREADS to run the OS thread, which is 2 threads by default. For TTRPC and container-related threads run in the `tokio` thread in a unified manner, and related dependencies need to be switched to Async, such as Timer, File, Netlink, etc. With the help of Async, we can easily support no-block I/O and timer. Currently, we only utilize Async for kata-runtime. The built-in VMM keeps the OS thread because it can ensure that the threads are controllable.
+
+**For N `tokio` worker threads and M containers**
+
+- Sync runtime(both OS thread and `tokio` task are OS thread but without `tokio` worker thread)  OS thread number:  4 + 12*M
+- Async runtime(only OS thread is OS thread) OS thread number: 2 + N
+```shell
+├─ main(OS thread)
+├─ async-logger(OS thread)
+└─ tokio worker(N * OS thread)
+  ├─ agent log forwarder(1 * tokio task)
+  ├─ health check thread(1 * tokio task)
+  ├─ TTRPC reaper thread(M * tokio task)
+  ├─ TTRPC listener thread(M * tokio task)
+  ├─ TTRPC client handler thread(7 * M * tokio task)
+  ├─ container stdin io thread(M * tokio task)
+  ├─ container stdout io thread(M * tokio task)
+  └─ container stderr io thread(M * tokio task)
+```
+### Extensible Framework
+The Kata 3.x runtime is designed with the extension of service, runtime, and hypervisor, combined with configuration to meet the needs of different scenarios. At present, the service provides a register mechanism to support multiple services. Services could interact with runtime through messages. In addition, the runtime handler handles messages from services. To meet the needs of a binary that supports multiple runtimes and hypervisors, the startup must obtain the runtime handler type and hypervisor type through configuration.
+
+![framework](./images/framework.png)
+### Resource Manager
+In our case, there will be a variety of resources, and every resource has several subtypes. Especially for `Virt-Container`, every subtype of resource has different operations. And there may be dependencies, such as the share-fs rootfs and the share-fs volume will use share-fs resources to share files to the VM. Currently, network and share-fs are regarded as sandbox resources, while rootfs, volume, and cgroup are regarded as container resources. Also, we abstract a common interface for each resource and use subclass operations to evaluate the differences between different subtypes.
+![resource manager](./images/resourceManager.png)
+
+## Roadmap
+
+- Stage 1 (June): provide basic features (current delivered)
+- Stage 2 (September): support common features
+- Stage 3: support full features
+
+| **Class**                  | **Sub-Class**       | **Development Stage** | **Status** |
+| -------------------------- | ------------------- | --------------------- |------------|
+| Service                    | task service        | Stage 1               |  ✅        |
+|                            | extend service      | Stage 3               |  🚫        |
+|                            | image service       | Stage 3               |  🚫        |
+| Runtime handler            | `Virt-Container`    | Stage 1               |  ✅        |
+| Endpoint                   | VETH Endpoint       | Stage 1               |  ✅        |
+|                            | Physical Endpoint   | Stage 2               |  ✅        |
+|                            | Tap Endpoint        | Stage 2               |  ✅        |
+|                            | `Tuntap` Endpoint   | Stage 2               |  ✅        |
+|                            | `IPVlan` Endpoint   | Stage 2               |  ✅        |
+|                            | `MacVlan` Endpoint  | Stage 2               |  ✅        |
+|                            | MACVTAP Endpoint    | Stage 3               |  🚫        |
+|                            | `VhostUserEndpoint` | Stage 3               |  🚫        |
+| Network Interworking Model | Tc filter           | Stage 1               |  ✅        |
+|                            | `MacVtap`           | Stage 3               |  🚧        |
+| Storage                    | Virtio-fs           | Stage 1               |  ✅        |
+|                            | `nydus`             | Stage 2               |  🚧        |
+|                            | `device mapper`     | Stage 2               |  🚫        |
+| `Cgroup V2`                |                     | Stage 2               |  🚧        |
+| Hypervisor                 | `Dragonball`        | Stage 1               |  🚧        |
+|                            | QEMU                | Stage 2               |  🚫        |
+|                            | Cloud Hypervisor    | Stage 3               |  🚫        |
+|                            | Firecracker         | Stage 3               |  🚫        |
+
+## FAQ
+
+- Are the "service", "message dispatcher" and "runtime handler" all part of the single Kata 3.x runtime binary?
+
+  Yes. They are components in Kata 3.x runtime. And they will be packed into one binary.
+  1. Service is an interface, which is responsible for handling multiple services like task service, image service and etc.
+  2. Message dispatcher, it is used to match multiple requests from the service module.
+  3. Runtime handler is used to deal with the operation for sandbox and container.
+- What is the name of the Kata 3.x runtime binary?
+
+  Apparently we can't use `containerd-shim-v2-kata` because it's already used. We are facing the hardest issue of "naming" again. Any suggestions are welcomed.
+  Internally we use `containerd-shim-v2-rund`.
+
+- Is the Kata 3.x design compatible with the containerd shimv2 architecture?
+
+  Yes. It is designed to follow the functionality of go version kata.  And it implements the `containerd shim v2` interface/protocol.
+
+- How will users migrate to the Kata 3.x architecture?
+
+  The migration plan will be provided before the Kata 3.x is merging into the main branch.
+
+- Is `Dragonball` limited to its own built-in VMM? Can the `Dragonball` system be configured to work using an external `Dragonball` VMM/hypervisor?
+
+  The `Dragonball` could work as an external hypervisor. However, stability and performance is challenging in this case. Built in VMM could optimise the container overhead, and it's easy to maintain stability.
+
+  `runD` is the `containerd-shim-v2` counterpart of `runC` and can run a pod/containers. `Dragonball` is a `microvm`/VMM that is designed to run container workloads. Instead of `microvm`/VMM, we sometimes refer to it as secure sandbox.
+
+- QEMU, Cloud Hypervisor and Firecracker support are planned, but how that would work. Are they working in separate process?
+
+  Yes. They are unable to work as built in VMM.
+
+- What is `upcall`?
+
+    The `upcall` is used to hotplug CPU/memory/MMIO devices, and it solves two issues.
+    1. avoid dependency on PCI/ACPI
+    2. avoid dependency on `udevd` within guest and get deterministic results for hotplug operations. So `upcall` is an alternative to ACPI based CPU/memory/device hotplug. And we may cooperate with the community to add support for ACPI based CPU/memory/device hotplug if needed.
+
+    `Dbs-upcall` is a `vsock-based` direct communication tool between VMM and guests. The server side of the `upcall` is a driver in guest kernel (kernel patches are needed for this feature) and it'll start to serve the requests once the kernel has started. And the client side is in VMM , it'll be a thread that communicates with VSOCK through `uds`. We have accomplished device hotplug / hot-unplug directly through `upcall` in order to avoid virtualization of ACPI  to minimize virtual machine's overhead. And there could be many other usage through this direct communication channel. It's already open source.
+   https://github.com/openanolis/dragonball-sandbox/tree/main/crates/dbs-upcall
+
+- The URL below says the kernel patches work with 4.19, but do they also work with 5.15+ ?
+
+  Forward compatibility should be achievable, we have ported it to 5.10 based kernel.
+
+- Are these patches platform-specific or would they work for any architecture that supports VSOCK?
+
+  It's almost platform independent, but some message related to CPU hotplug are platform dependent.
+
+- Could the kernel driver be replaced with a userland daemon in the guest using loopback VSOCK?
+
+  We need to create device nodes for hot-added CPU/memory/devices, so it's not easy for userspace daemon to do these tasks.
+
+- The fact that `upcall` allows communication between the VMM and the guest suggests that this architecture might be incompatible with https://github.com/confidential-containers where the VMM should have no knowledge of what happens inside the VM.
+
+  1. `TDX` doesn't support CPU/memory hotplug yet.
+  2. For ACPI based device hotplug, it depends on ACPI `DSDT` table, and the guest kernel will execute `ASL` code to handle during handling those hotplug event. And it should be easier to audit VSOCK based communication than ACPI `ASL` methods.
+
+- What is the security boundary for the monolithic / "Built-in VMM" case?
+
+  It has the security boundary of virtualization. More details will be provided in next stage.

docs/design/architecture_4.0/README.md

@@ -1,433 +0,0 @@
-# Kata Containers 4.0 Architecture (Rust Runtime)
-
-## Overview
-
-Kata Containers 4.0 represents a significant architectural evolution, moving beyond the limitations of legacy multi-process container runtimes. Driven by a modern Rust-based stack, this release transitions to an asynchronous, unified architecture that drastically reduces resource consumption and latency.
-
-By consolidating the entire runtime into a single, high-performance binary, Kata 4.0 eliminates the overhead of cross-process communication and streamlines the container lifecycle. The result is a secure, production-tested runtime capable of handling high-density workloads with efficiency. With built-in support for diverse container abstractions and optimized hypervisor integration, Kata 4.0 delivers the agility and robustness required by modern, cloud-native infrastructure.
-
----
-
-## 1. Architecture Overview
-
-The Kata Containers Rust Runtime is designed to minimize resource overhead and startup latency. It achieves this by shifting from traditional process-based management to a more integrated, Rust-native control flow.
-
-```mermaid
-graph TD
-    containerd["containerd"] --> shimv2["containerd-shim-kata-v2 (shimv2)"]
-
-    subgraph BuiltIn["Built-in VMM (Integrated Mode)"]
-        direction TD
-        subgraph shimv2_bi["shimv2 process (Single Process)"]
-            runtime_bi["shimv2 runtime"]
-            subgraph dragonball["Dragonball VMM (library)"]
-                helpers_bi["virtiofs / nydus\n(BuiltIn)"]
-            end
-            runtime_bi -->|"direct function calls"| dragonball
-        end
-        subgraph guestvm_bi["Guest VM"]
-            agent_bi["kata-agent"]
-        end
-        shimv2_bi -->|"hybrid-vsock"| guestvm_bi
-    end
-
-    subgraph OptionalVMM["Optional VMM (External Mode)"]
-        direction TD
-        shimv2_ext["shimv2 process"]
-        imagesrvd_ext["virtiofsd / nydusd\n(Independent Process)"]
-        ext_vmm["External VMM process\n(QEMU / Cloud-Hypervisor / Firecracker)"]
-        subgraph guestvm_ext["Guest VM"]
-            agent_ext["kata-agent"]
-        end
-        shimv2_ext -->|"fork + IPC/RPC"| ext_vmm
-        shimv2_ext -->|"manages"| imagesrvd_ext
-        ext_vmm -->|"vsock / hybrid-vsock"| guestvm_ext
-    end
-
-    shimv2 --> BuiltIn
-    shimv2 --> OptionalVMM
-
-    classDef process fill:#d0e8ff,stroke:#336,stroke-width:1px
-    classDef vm fill:#d4edda,stroke:#155724,stroke-width:1px
-    classDef agent fill:#fff3cd,stroke:#856404,stroke-width:1px
-    class shimv2,runtime_bi,shimv2_ext,helpers_bi,imagesrvd_ext,ext_vmm process
-    class guestvm_bi,guestvm_ext vm
-    class agent_bi,agent_ext agent
-```
-
-The runtime employs a **flexible VMM strategy**, supporting both `built-in` and `optional` VMMs. This allows users to choose between a tightly integrated VMM (e.g., Dragonball) for peak performance, or external options (e.g., QEMU, Cloud-Hypervisor, Firecracker) for enhanced compatibility and modularity.
-
-### A. Built-in VMM (Integrated Mode)
-
-The built-in VMM mode is the default and recommended configuration for users, as it offers superior performance and resource efficiency.
-
-In this mode, the VMM (`Dragonball`) is **deeply integrated** into the `shimv2`'s lifecycle. This eliminates the overhead of IPC, enabling lower-latency message processing and tight API synchronization. Moreover, it ensures the runtime and VMM share a unified lifecycle, simplifying exception handling and resource cleanup.
-
-*   **Integrated Management**: The `shimv2` directly controls the VMM and its critical helper services (`virtiofsd` or `nydusd`).
-*   **Performance**: By eliminating external process overhead and complex inter-process communication (IPC), this mode achieves faster container startup and higher resource density.
-*   **Core Technology**: Primarily utilizes **Dragonball**, the native Rust-based VMM optimized and dedicated for cloud-native scenarios.
-
-> **Note**: The built-in VMM mode is the default and recommended configuration for users, as it offers superior performance and resource efficiency.
-
-### B. Optional VMM (External Mode)
-
-The optional VMM mode is available for users with specific requirements that necessitate external hypervisor support.
-
-In this mode, the runtime and the VMM operate as separate, decoupled processes. The runtime forks the VMM process and interacts with it via inter-process RPC. And the `containerd-shim-kata-v2`(short of `shimv2`) manages the VMM as an **external process**.
-
-*   **Decoupled Lifecycle**: The `shimv2` communicates with the VMM (e.g., QEMU, Cloud-Hypervisor, or Firecracker) via vsock/hybrid vsock.
-*   **Flexibility**: Ideal for environments that require specific hypervisor hardware emulation or legacy compatibility.
-
-> **Note**:  This approach (Optional VMM) introduces overhead due to context switching and cross-process communication. Furthermore, managing resources across process boundaries—especially during abnormal conditions—introduces significant complexity in error detection and recovery.
-
----
-
-## Core Architectural Principles
-
-*   **Safety via Rust**: Leveraging Rust's ownership and type systems to eliminate memory-related vulnerabilities (buffer overflows, dangling pointers) by design.
-*   **Performance via Async**: Utilizing Tokio to handle high-concurrency I/O, reducing the OS thread footprint by an order of magnitude.
-*   **Built-in VMM**: A modular, library-based approach to virtualization, enabling tighter integration with the runtime.
-*   **Pluggable Framework**: A clean abstraction layer allowing seamless swapping of hypervisors, network interfaces, and storage backends.
-
----
-
-## Design Deep Dive
-
-### Built-in VMM Integration (Dragonball)
-
-The legacy Kata 2.x architecture relied on inter-process communication (IPC) between the runtime and the VMM. This introduced context-switching latency and complex error-recovery requirements across process boundaries. In contrast, the built-in VMM approach embeds the VMM directly within the runtime's process space. This eliminates IPC overhead, allowing for direct function calls and shared memory access, resulting in significantly reduced startup times and improved performance.
-
-```mermaid
-graph LR
-    subgraph HostProcess["Host Process:containerd-shim-kata-v2 (shimv2)"]
-        shimv2["shimv2 runtime"]
-    end
-
-    imagesrvd["virtiofsd / nydusd\n(Independent Process)"]
-
-    subgraph ExtVMMProc["External VMM Process (e.g., QEMU)"]
-        vmm["VMM\n(QEMU / Cloud-Hypervisor\n/ Firecracker)"]
-    end
-
-    subgraph GuestVM["Guest VM"]
-        agent["kata-agent"]
-    end
-
-    shimv2 -->|"fork + IPC / RPC"| vmm
-    shimv2 -->|"manages"| imagesrvd
-    vmm -->|"vsock / hybrid-vsock"| GuestVM
-
-    classDef proc fill:#d0e8ff,stroke:#336,stroke-width:1px
-    classDef vm fill:#d4edda,stroke:#155724,stroke-width:1px
-    classDef ag fill:#fff3cd,stroke:#856404,stroke-width:1px
-    class shimv2,imagesrvd,vmm proc
-    class agent ag
-```
-
-```mermaid
-graph LR
-    subgraph SingleProcess["Single Process: containerd-shim-kata-v2 (shimv2)"]
-        shimv2["shimv2 runtime"]
-        subgraph dragonball["Dragonball VMM (library)"]
-            helpers["virtiofs / nydus\n(BuiltIn)"]
-        end
-        shimv2 -->|"direct function calls"| dragonball
-    end
-
-    subgraph GuestVM["Guest VM"]
-        agent["kata-agent"]
-    end
-
-    dragonball -->|"hybrid-vsock"| GuestVM
-
-    classDef proc fill:#d0e8ff,stroke:#336,stroke-width:1px
-    classDef vm fill:#d4edda,stroke:#155724,stroke-width:1px
-    classDef ag fill:#fff3cd,stroke:#856404,stroke-width:1px
-    class shimv2,helpers proc
-    class agent ag
-```
-
-By integrating Dragonball directly as a library, we eliminate the need for heavy IPC.
-
-*   **API Synchronization**: Direct function calls replace RPCs, reducing latency.
-*   **Unified Lifecycle**: The runtime and VMM share a single process lifecycle, significantly simplifying resource cleanup and fault isolation.
-
-### Layered Architecture
-
-The Kata 4.0 runtime utilizes a highly modular, layered architecture designed to decouple high-level service requests from low-level infrastructure execution. This design facilitates extensibility, allowing the system to support diverse container types and dragonball within a single, unified Rust binary and also support other hypervisors  as optional VMMs.
-
-```mermaid
-graph TD
-    subgraph L1["Layer 1 — Service & Orchestration Layer"]
-        TaskSvc["Task Service"]
-        ImageSvc["Image Service"]
-        OtherSvc["Other Services"]
-        Dispatcher["Message Dispatcher"]
-        TaskSvc --> Dispatcher
-        ImageSvc --> Dispatcher
-        OtherSvc --> Dispatcher
-    end
-
-    subgraph L2["Layer 2 — Management & Handler Layer"]
-        subgraph RuntimeHandler["Runtime Handler"]
-            SandboxMgr["Sandbox Manager"]
-            ContainerMgr["Container Manager"]
-        end
-        subgraph ContainerAbstractions["Container Abstractions"]
-            LinuxContainer["LinuxContainer"]
-            VirtContainer["VirtContainer"]
-            WasmContainer["WasmContainer"]
-        end
-    end
-
-    subgraph L3["Layer 3 — Infrastructure Abstraction Layer"]
-        subgraph HypervisorIface["Hypervisor Interface"]
-            Qemu["Qemu"]
-            CloudHV["Cloud Hypervisor"]
-            Firecracker["Firecracker"]
-            Dragonball["Dragonball"]
-        end
-        subgraph ResourceMgr["Resource Manager"]
-            Sharedfs["Sharedfs"]
-            Network["Network"]
-            Rootfs["Rootfs"]
-            Volume["Volume"]
-            Cgroup["Cgroup"]
-        end
-    end
-
-    subgraph L4["Layer 4 — Built-in Dragonball VMM Layer"]
-        BuiltinDB["Builtin Dragonball"]
-    end
-
-    Dispatcher --> RuntimeHandler
-    RuntimeHandler --> ContainerAbstractions
-    ContainerAbstractions --> HypervisorIface
-    ContainerAbstractions --> ResourceMgr
-    Dragonball --> BuiltinDB
-
-    classDef svc fill:#cce5ff,stroke:#004085,stroke-width:1px
-    classDef handler fill:#d4edda,stroke:#155724,stroke-width:1px
-    classDef infra fill:#fff3cd,stroke:#856404,stroke-width:1px
-    classDef builtin fill:#f8d7da,stroke:#721c24,stroke-width:1px
-    class TaskSvc,ImageSvc,OtherSvc,Dispatcher svc
-    class SandboxMgr,ContainerMgr,LinuxContainer,VirtContainer,WasmContainer handler
-    class Qemu,CloudHV,Firecracker,Dragonball,Sharedfs,Network,Rootfs,Volume,Cgroup infra
-    class BuiltinDB builtin
-```
-
-#### Service & Orchestration Layer
-
-*   **Service Layer**: The entry point for the runtime, providing specialized interfaces for external callers (e.g., `containerd`). It includes:
-    *   **Task Service**: Manages the lifecycle of containerized processes.
-    *   **Image Service**: Handles container image operations.
-    *   **Other Services**: An extensible framework allowing for custom modules.
-
-*   **Message Dispatcher**: Acts as a centralized traffic controller. It parses requests from the Service layer and routes them to the appropriate **Runtime Handler**, ensuring efficient message multiplexing.
-
-#### Management & Handler Layer
-
-*   **Runtime Handler**: The core processing engine. It abstracts the underlying workload, enabling the runtime to handle various container types through:
-    *   **Sandbox Manager**: Orchestrates the lifecycle of the entire Pod (Sandbox).
-    *   **Container Manager**: Manages individual containers within a Sandbox.
-
-*   **Container Abstractions**: The framework is agnostic to the container implementation, with explicit support paths for:
-    *   **LinuxContainer** (Standard/OCI)
-    *   **VirtContainer** (Virtualization-based)
-    *   **WasmContainer** (WebAssembly-based)
-
-#### Infrastructure Abstraction Layer
-
-This layer provides standardized interfaces for hardware and resource management, regardless of the underlying backend.
-
-*   **Hypervisor Interface**: A pluggable architecture supporting multiple virtualization backends, including **Qemu**, **Cloud Hypervisor**, **Firecracker**, and **Dragonball**.
-
-*   **Resource Manager**: A unified interface for managing critical infrastructure components:
-    *   **Sharedfs, Network, Rootfs, Volume, and cgroup management**.
-
-#### Built-in Dragonball VMM Layer
-
-Representing the core of the high-performance runtime, the `Builtin Dragonball` block demonstrates deep integration between the runtime and the hypervisor.
-
-#### Key Architectural Advantages
-
-*   **Uniformity**: By consolidating these layers into a single binary, the runtime ensures a consistent state across all sub-modules, preventing the "split-brain" scenarios common in multi-process runtimes.
-*   **Modularity**: The clear separation between the **Message Dispatcher** and the **Runtime Handler** allows developers to introduce new container types (e.g., WASM) or hypervisors without modifying existing core logic.
-*   **Efficiency**: The direct integration of `Dragonball` as a library allows for "Zero-Copy" resource management and direct API access, which drastically improves performance compared to traditional RPC-based hypervisor interaction.
-
-### Extensible Framework
-
-The Kata Rust runtime features a modular design that supports diverse services, runtimes, and hypervisors. We utilize a registration mechanism to decouple service logic from the core runtime. At startup, the runtime resolves the required runtime handler and hypervisor types based on configuration.
-
-```mermaid
-graph LR
-    API["API"]
-
-    subgraph Services["Configurable Services"]
-        TaskSvc["Task Service"]
-        ImageSvc["Image Service"]
-        OtherSvc["Other Service"]
-    end
-
-    Msg(["Message Dispatcher"])
-
-    subgraph Handlers["Configurable Runtime Handlers"]
-        WasmC["WasmContainer"]
-        VirtC["VirtContainer"]
-        LinuxC["LinuxContainer"]
-    end
-
-    subgraph HVs["Configurable Hypervisors"]
-        DB["Dragonball"]
-        QEMU["QEMU"]
-        CH["Cloud Hypervisor"]
-        FC["Firecracker"]
-    end
-
-    API --> Services
-    Services --> Msg
-    Msg --> Handlers
-    Handlers --> HVs
-
-    classDef api fill:#d0e8ff,stroke:#336,stroke-width:1px
-    classDef svc fill:#e2d9f3,stroke:#6610f2,stroke-width:1px
-    classDef msg fill:#fff3cd,stroke:#856404,stroke-width:1px
-    classDef handler fill:#d4edda,stroke:#155724,stroke-width:1px
-    classDef hv fill:#f8d7da,stroke:#721c24,stroke-width:1px
-    class API api
-    class TaskSvc,ImageSvc,OtherSvc svc
-    class Msg msg
-    class WasmC,VirtC,LinuxC handler
-    class DB,QEMU,CH,FC hv
-```
-
-### Modular Resource Manager
-
-Managing diverse resources—from Virtio-fs volumes to Cgroup V2—is handled by an abstracted resource manager. Each resource type implements a common trait, enabling uniform lifecycle hooks and deterministic dependency resolution.
-
-```mermaid
-graph LR
-    RM["Resource Manager"]
-
-    subgraph SandboxRes["Sandbox Resources"]
-        Network["Network Entity"]
-        SharedFs["Shared FS"]
-    end
-
-    subgraph ContainerRes["Container Resources"]
-        Rootfs["Rootfs"]
-        Cgroup["Cgroup"]
-        Volume["Volume"]
-    end
-
-    RM --> Network
-    RM --> SharedFs
-    RM --> Rootfs
-    RM --> Cgroup
-    RM --> Volume
-
-    Network --> Endpoint["endpoint\n(veth / physical)"]
-    Network --> NetModel["model\n(tcfilter / route)"]
-    SharedFs --> InlineVirtioFs["inline virtiofs"]
-    SharedFs --> StandaloneVirtioFs["standalone virtiofs"]
-
-    Rootfs --> RootfsTypes["block / virtiofs / nydus"]
-    Cgroup --> CgroupVers["v1 / v2"]
-    Volume --> VolumeTypes["sharefs / shm / local\nephemeral / direct / block"]
-
-    classDef rm fill:#e2d9f3,stroke:#6610f2,stroke-width:2px
-    classDef sandbox fill:#d0e8ff,stroke:#336,stroke-width:1px
-    classDef container fill:#d4edda,stroke:#155724,stroke-width:1px
-    classDef impl fill:#fff3cd,stroke:#856404,stroke-width:1px
-    class RM rm
-    class Network,SharedFs sandbox
-    class Rootfs,Cgroup,Volume container
-    class Endpoint,NetModel,InlineVirtioFs,StandaloneVirtioFs,RootfsTypes,CgroupVers,VolumeTypes impl
-```
-
-### Asynchronous I/O Model
-
-Synchronous runtimes are often limited by "thread bloat," where each container or connection spawns multiple OS threads.
-
-#### Why Async Rust?
-
-**The Rust async ecosystem is stable and highly efficient, providing several key benefits:**
-
-- Reduced Overhead: Significantly lower CPU and memory consumption, particularly for I/O-bound workloads.
-- Zero-Cost Abstractions: Rust's async model allows developers to "pay only for what they use," avoiding heap allocations and dynamic dispatch where possible.
-- For further reading, see [Why Async?](https://rust-lang.github.io/async-book/01_getting_started/02_why_async.html) and [The State of Asynchronous Rust](https://rust-lang.github.io/async-book/01_getting_started/03_state_of_async_rust.html).
-
-**Limitations of Synchronous Rust in kata-runtime:**
-
-- Thread Proliferation: Every TTRPC connection creates multiple threads (Reaper, Listener, Handler), and each container adds 3 additional I/O threads, leading to high thread count and memory pressure.
-- Timeout Complexity: Implementing reliable, cross-platform timeout mechanisms in synchronous code is difficult, especially when aligning with Golang-based components.
-
-#### Implementation
-
-The kata-runtime utilizes Tokio to manage asynchronous tasks. By offloading TTRPC and container-related I/O to a unified Tokio executor and switching dependencies (Timer, File, Netlink) to their asynchronous counterparts, we achieve non-blocking I/O. The built-in VMM remains on a dedicated OS thread to ensure control and real-time performance.
-
-**Comparison of OS Thread usage (for N tokio worker threads and M containers)**
-
-- Sync Runtime: OS thread count scales as 4 + 12*M.
-- Async Runtime: OS thread count scales as 2 + N.
-
-```shell
-├─ main(OS thread)
-├─ async-logger(OS thread)
-└─ tokio worker(N * OS thread)
-  ├─ agent log forwarder(1 * tokio task)
-  ├─ health check thread(1 * tokio task)
-  ├─ TTRPC reaper thread(M * tokio task)
-  ├─ TTRPC listener thread(M * tokio task)
-  ├─ TTRPC client handler thread(7 * M * tokio task)
-  ├─ container stdin io thread(M * tokio task)
-  ├─ container stdout io thread(M * tokio task)
-  └─ container stderr io thread(M * tokio task)
-```
-
-The Async Advantage:
-We move away from thread-per-task to a Tokio-driven task model.
-
-*   **Scalability**: The OS thread count is reduced from 4 + 12*M (Sync) to 2 + N (Async), where N is the worker thread count.
-*   **Efficiency**: Non-blocking I/O allows a single thread to handle multiplexed container operations, significantly lowering memory consumption for high-density pod deployments.
-
----
-
-## 2. Getting Started
-To configure your preferred VMM strategy, locate the `[hypervisor]` block in your runtime configuration file:
-
-- Install Kata Containers with the Rust Runtime and Dragonball as the built-in VMM by following the [containerd-kata](../../how-to/containerd-kata.md).
-- Run a kata with builtin VMM Dragonball
-
-```shell
-$ sudo ctr run  --runtime io.containerd.kata.v2 -d docker.io/library/ubuntu:latest hello
-```
-
-As the VMM and its image service have been builtin, you should only see a single containerd-shim-kata-v2 process.
-
----
-
-## FAQ
-
-* **Q1**: Is the architecture compatible with containerd?
-
-Yes. It implements the containerd-shim-v2 interface, ensuring drop-in compatibility with standard cloud-native tooling.
-
-* **Q2**: What is the security boundary for the "Built-in VMM" model?
-
-The security boundary remains established by the hypervisor (hardware virtualization). The shift to a monolithic process model does not compromise isolation; rather, it improves the integrity of the control plane by reducing the attack surface typically associated with complex IPC mechanisms.
-
-* **Q3**: What is the migration path?
-
-Migration is managed via configuration policies. The containerd shim configuration will allow users to toggle between the legacy runtime and the runtime-rs (internally `RunD`) binary, facilitating canary deployments and gradual migration.
-
-* **Q4**: Why upcall instead of ACPI?
-
-Standard ACPI-based hotplugging requires heavy guest-side kernel emulation and udevd interaction. Dbs-upcall utilizes a vsock-based direct channel to trigger hotplug events, providing:
-
-Deterministic execution: Bypassing complex guest-side ACPI state machines.
-Lower overhead: Minimizing guest kernel footprint.
-
-* **Q5**: How upcall works?
-
-The `Dbs-upcall` architecture consists of a server-side driver in the guest kernel and a client-side thread within the VMM. Once the guest kernel initializes, it establishes a communication channel via vsock (using uds). This allows the VMM to directly request device hot-add/hot-remove operations. We have already open-sourced this implementation: [dbs-upcall](https://github.com/openanolis/dragonball-sandbox/tree/main/crates/dbs-upcall).

docs/design/virtualization.md

@@ -1,324 +1,137 @@
 # Virtualization in Kata Containers
 
-## Overview
+Kata Containers, a second layer of isolation is created on top of those provided by traditional namespace-containers. The
+hardware virtualization interface is the basis of this additional layer. Kata will launch a lightweight virtual machine,
+and use the guest’s Linux kernel to create a container workload, or workloads in the case of multi-container pods. In Kubernetes
+and in the Kata implementation, the sandbox is carried out at the pod level. In Kata, this sandbox is created using a virtual machine.
 
-Kata Containers creates a second layer of isolation on top of traditional namespace-based containers using hardware virtualization. Kata launches a lightweight virtual machine (VM) and uses the guest Linux kernel to create container workloads. In Kubernetes, the sandbox is implemented at the pod level using VMs.
+This document describes how Kata Containers maps container technologies to virtual machines technologies, and how this is realized in
+the multiple hypervisors and virtual machine monitors that Kata supports.
 
-This document describes:
+## Mapping container concepts to virtual machine technologies
 
-- How Kata Containers maps container technologies to virtualization technologies
-- The multiple hypervisors and Virtual Machine Monitors (VMMs) supported by Kata
-- Guidance for selecting the appropriate hypervisor for your use case
+A typical deployment of Kata Containers will be in Kubernetes by way of a Container Runtime Interface (CRI) implementation. On every node,
+Kubelet will interact with a CRI implementer (such as containerd or CRI-O), which will in turn interface with Kata Containers (an OCI based runtime).
 
-### Architecture
+The CRI API, as defined at the [Kubernetes CRI-API repo](https://github.com/kubernetes/cri-api/), implies a few constructs being supported by the
+CRI implementation, and ultimately in Kata Containers. In order to support the full [API](https://github.com/kubernetes/cri-api/blob/a6f63f369f6d50e9d0886f2eda63d585fbd1ab6a/pkg/apis/runtime/v1alpha2/api.proto#L34-L110) with the CRI-implementer, Kata must provide the following constructs:
 
-A typical Kata Containers deployment integrates with Kubernetes through a Container Runtime Interface (CRI) implementation:
+![API to construct](./arch-images/api-to-construct.png)
 
-```
-Kubelet → CRI (containerd/CRI-O) → Kata Containers (OCI runtime) → VM → Containers
-```
+These constructs can then be further mapped to what devices are necessary for interfacing with the virtual machine:
 
-The CRI API requires Kata to support the following constructs:
+![construct to VM concept](./arch-images/construct-to-vm-concept.png)
 
-| CRI Construct | VM Equivalent | Virtualization Technology |
-|---------------|---------------|---------------------------|
-| Pod Sandbox | VM | Hypervisor/VMM |
-| Container | Process in VM | Namespace/Cgroup in guest |
-| Network | Network Interface | virtio-net, vhost-net, physical, etc. |
-| Storage | Block/File Device | virtio-block, virtio-scsi, virtio-fs |
-| Compute | vCPU/Memory | KVM, ACPI hotplug |
+Ultimately, these concepts map to specific para-virtualized devices or virtualization technologies.
 
-### Mapping Container Concepts to Virtualization Technologies
+![VM concept to underlying technology](./arch-images/vm-concept-to-tech.png)
 
-Kata Containers implements the Kubernetes Container Runtime Interface (CRI) to provide pod and container lifecycle management. The CRI API defines abstractions that Kata must translate into virtualization primitives.
+Each hypervisor or VMM varies on how or if it handles each of these.
 
-The mapping from CRI constructs to virtualization technologies follows a three-layer model:
+## Kata Containers Hypervisor and VMM support
 
-```
-CRI API Constructs → VM Abstractions → Para-virtualized Devices
-```
+Kata Containers [supports multiple hypervisors](../hypervisors.md).
 
-**Layer 1: CRI API Constructs**
-
-The CRI API ([kubernetes/cri-api](https://github.com/kubernetes/cri-api)) defines the following abstractions that Kata must implement:
-
-| Construct | Description |
-|-----------|-------------|
-| Pod Sandbox | Isolated execution environment for containers |
-| Container | Process workload within a sandbox |
-| Network | Pod and container networking interfaces |
-| Storage | Volume mounts and image storage |
-| RuntimeConfig | Resource constraints (CPU, memory, cgroups) |
-
-![CRI API to Kata Constructs](./arch-images/api-to-construct.png)
-
-**Layer 2: VM Abstractions**
-
-Kata translates CRI constructs into VM-level concepts:
-
-| CRI Construct | VM Equivalent |
-|---------------|---------------|
-| Pod Sandbox | Virtual Machine |
-| Container | Process/namespace in guest OS |
-| Network | Virtual NIC (vNIC) |
-| Storage | Virtual block device or filesystem |
-| RuntimeConfig | VM resources (vCPU, memory) |
-
-![Kata Constructs to VM Concepts](./arch-images/construct-to-vm-concept.png)
-
-**Layer 3: Para-virtualized Devices**
-
-VM abstractions are realized through para-virtualized drivers for optimal performance:
-
-| VM Concept | Device Technology |
-|------------|-------------------|
-| vNIC | virtio-net, vhost-net, macvtap |
-| Block Storage | virtio-block, virtio-scsi |
-| Shared Filesystem | virtio-fs |
-| Agent Communication | virtio-vsock |
-| Device Passthrough | VFIO with IOMMU |
-
-![VM Concepts to Underlying Technology](./arch-images/vm-concept-to-tech.png)
-
-> **Note:** Each hypervisor implements these mappings differently based on its device model and feature set. See the [Hypervisor Details](#hypervisor-details) section for specific implementations.
-
-### Device Mapping
-
-Container constructs map to para-virtualized devices:
-
-| Construct | Device Type | Technology |
-|-----------|-------------|------------|
-| Network | Network Interface | virtio-net, vhost-net |
-| Storage (ephemeral) | Block Device | virtio-block, virtio-scsi |
-| Storage (shared) | Filesystem | virtio-fs |
-| Communication | Socket | virtio-vsock |
-| GPU/Passthrough | PCI Device | VFIO, IOMMU |
-
-## Supported Hypervisors and VMMs
-
-Kata Containers supports multiple hypervisors, each with different characteristics:
-
-| Hypervisor | Language | Architectures | Type |
-|------------|----------|---------------|------|
-| [QEMU] | C | x86_64, aarch64, ppc64le, s390x, risc-v | Type 2 (KVM) |
-| [Cloud Hypervisor] | Rust | x86_64, aarch64 | Type 2 (KVM) |
-| [Firecracker] | Rust | x86_64, aarch64 | Type 2 (KVM) |
-| `Dragonball` | Rust | x86_64, aarch64 | Type 2 (KVM) Built-in |
-
-> **Note:** All supported hypervisors use KVM (Kernel-based Virtual Machine) as the underlying hardware virtualization interface on Linux.
-
-## Hypervisor Details
+Details of each solution and a summary are provided below.
 
 ### QEMU/KVM
 
-QEMU is the most mature and feature-complete hypervisor option for Kata Containers.
+Kata Containers with QEMU has complete compatibility with Kubernetes.
 
-**Machine Types:**
+Depending on the host architecture, Kata Containers supports various machine types,
+for example `q35` on x86 systems, `virt` on ARM systems and `pseries` on IBM Power systems. The default Kata Containers
+machine type is `q35`. The machine type and its [`Machine accelerators`](#machine-accelerators) can
+be changed by editing the runtime [`configuration`](architecture/README.md#configuration) file.
 
-- `q35` (x86_64, default)
-- `s390x` (s390x)
-- `virt` (aarch64)
-- `pseries` (ppc64le)
-- `risc-v` (riscv64, experimental)
+Devices and features used:
+- virtio VSOCK or virtio serial
+- virtio block or virtio SCSI
+- [virtio net](https://www.redhat.com/en/virtio-networking-series)
+- virtio fs or virtio 9p (recommend: virtio fs)
+- VFIO
+- hotplug
+- machine accelerators
 
-**Devices and Features:**
+Machine accelerators and hotplug are used in Kata Containers to manage resource constraints, improve boot time and reduce memory footprint. These are documented below.
 
-- virtio-vsock (agent communication)
-- virtio-block or virtio-scsi (storage)
-- virtio-net/vhost-net/vhost-user-net (networking)
-- virtio-fs (shared filesystem, virtio-fs recommended)
-- VFIO (device passthrough)
-- CPU and memory hotplug
-- NVDIMM (x86_64, for rootfs as persistent memory)
+#### Machine accelerators
 
-**Use Cases:**
+Machine accelerators are architecture specific and can be used to improve the performance
+and enable specific features of the machine types. The following machine accelerators
+are used in Kata Containers:
 
-- Production workloads requiring full CRI API compatibility
-- Scenarios requiring device passthrough (VFIO)
-- Multi-architecture deployments
+- NVDIMM: This machine accelerator is x86 specific and only supported by `q35` machine types.
+`nvdimm` is used to provide the root filesystem as a persistent memory device to the Virtual Machine.
 
-**Configuration:** See [`configuration-qemu.toml`](../../src/runtime/config/configuration-qemu.toml.in)
+#### Hotplug devices
 
-### Dragonball (Built-in VMM)
-
-Dragonball is a Rust-based VMM integrated directly into the Kata Containers Rust runtime as a library.
-
-**Advantages:**
-
-- **Zero IPC overhead**: VMM runs in the same process as the runtime
-- **Unified lifecycle**: Simplified resource management and error handling
-- **Optimized for containers**: Purpose-built for container workloads
-- **Upcall support**: Direct VMM-to-Guest communication for efficient hotplug operations
-- **Low resource overhead**: Minimal CPU and memory footprint
-
-**Architecture:**
-```
-┌─────────────────────────────────────────┐
-│     Kata Containers Runtime (Rust)      │
-│  ┌─────────────────────────────────┐    │
-│  │      Dragonball VMM Library     │    │
-│  └─────────────────────────────────┘    │
-└─────────────────────────────────────────┘
-```
-
-**Features:**
-
-- Built-in virtio-fs/nydus support
-- Async I/O via Tokio
-- Single binary deployment
-- Optimized startup latency
-
-**Use Cases:**
-
-- Default choice for most container workloads
-- High-density container deployments and low resource overhead scenarios
-- Scenarios requiring optimal startup performance
-
-**Configuration:** See [`configuration-dragonball.toml`](../../src/runtime-rs/config/configuration-dragonball.toml.in)
-
-### Cloud Hypervisor/KVM
-
-Cloud Hypervisor is a Rust-based VMM designed for modern cloud workloads with a focus on performance and security.
-
-**Features:**
-
-- CPU and memory resize
-- Device hotplug (disk, VFIO)
-- virtio-fs (shared filesystem)
-- virtio-pmem (persistent memory)
-- virtio-block (block storage)
-- virtio-vsock (agent communication)
-- Fine-grained seccomp filters per VMM thread
-- HTTP OpenAPI for management
-
-**Use Cases:**
-
-- High-performance cloud-native workloads
-- Applications requiring memory/CPU resizing
-- Security-sensitive deployments (seccomp isolation)
-
-**Configuration:** See [`configuration-cloud-hypervisor.toml`](../../src/runtime-rs/config/configuration-cloud-hypervisor.toml.in)
+The Kata Containers VM starts with a minimum amount of resources, allowing for faster boot time and a reduction in memory footprint.  As the container launch progresses,
+devices are hotplugged to the VM. For example, when a CPU constraint is specified which includes additional CPUs, they can be hot added.  Kata Containers has support
+for hot-adding the following devices:
+- Virtio block
+- Virtio SCSI
+- VFIO
+- CPU
 
 ### Firecracker/KVM
 
-Firecracker is a minimalist VMM built on rust-vmm crates, optimized for serverless and FaaS workloads.
+Firecracker, built on many rust crates that are within [rust-VMM](https://github.com/rust-vmm),  has a very limited device model, providing a lighter
+footprint and attack surface, focusing on function-as-a-service like use cases. As a result, Kata Containers with Firecracker VMM supports a subset of the CRI API.
+Firecracker does not support file-system sharing, and as a result only block-based storage drivers are supported. Firecracker does not support device
+hotplug nor does it support VFIO. As a result, Kata Containers with Firecracker VMM does not support updating container resources after boot, nor
+does it support device passthrough.
 
-**Devices:**
+Devices used:
+- virtio VSOCK
+- virtio block
+- virtio net
 
-- virtio-vsock (agent communication)
-- virtio-block (block storage)
-- virtio-net (networking)
+### Cloud Hypervisor/KVM
 
-**Limitations:**
+[Cloud Hypervisor](https://github.com/cloud-hypervisor/cloud-hypervisor), based
+on [rust-vmm](https://github.com/rust-vmm), is designed to have a
+lighter footprint and smaller attack surface for running modern cloud
+workloads. Kata Containers with Cloud
+Hypervisor provides mostly complete compatibility with Kubernetes
+comparable to the QEMU configuration. As of the 1.12 and 2.0.0 release
+of Kata Containers, the Cloud Hypervisor configuration supports both CPU
+and memory resize, device hotplug (disk and VFIO), file-system sharing through virtio-fs,
+block-based volumes, booting from VM images backed by pmem device, and
+fine-grained seccomp filters for each VMM threads (e.g. all virtio
+device worker threads).
 
-- No filesystem sharing (virtio-fs not supported)
-- No device hotplug
-- No VFIO/passthrough support
-- No CPU/memory hotplug
-- Limited CRI API support
+Devices and features used:
+- virtio VSOCK or virtio serial
+- virtio block
+- virtio net
+- virtio fs
+- virtio pmem
+- VFIO
+- hotplug
+- seccomp filters
+- [HTTP OpenAPI](https://github.com/cloud-hypervisor/cloud-hypervisor/blob/main/vmm/src/api/openapi/cloud-hypervisor.yaml)
 
-**Use Cases:**
+### StratoVirt/KVM
 
-- Serverless/FaaS workloads
-- Single-tenant microVMs
-- Scenarios prioritizing minimal attack surface
+[StratoVirt](https://gitee.com/openeuler/stratovirt) is an enterprise-level open source VMM oriented to cloud data centers, implements a unified architecture to support Standard-VMs, containers and serverless (Micro-VM). StratoVirt has some competitive advantages, such as lightweight and low resource overhead, fast boot, hardware acceleration, and language-level security with Rust.
 
-**Configuration:** See [`configuration-fc.toml`](../../src/runtime/config/configuration-fc.toml.in)
+Currently, StratoVirt in Kata supports Micro-VM machine type, mainly focus on FaaS cases, supporting device hotplug (virtio block), file-system sharing through virtio fs and so on. Kata Containers with StratoVirt now use virtio-mmio bus as driver, and doesn't support CPU/memory resize nor VFIO, thus doesn't support updating container resources after booted.
 
-## Hypervisor Comparison Summary
+Devices and features used currently:
+- Micro-VM machine type for FaaS(mmio, no ACPI)
+- Virtual Socket(vhost VSOCK、virtio console)
+- Virtual Storage(virtio block, mmio)
+- Virtual Networking(virtio net, mmio)
+- Shared Filesystem(virtio fs)
+- Device Hotplugging(virtio block hotplug)
+- Entropy Source(virtio RNG)
+- QMP API
 
-| Feature | QEMU | Cloud Hypervisor | Firecracker | Dragonball |
-|---------|------|------------------|-------------|------------|
-| Maturity | Excellent | Good | Good | Good |
-| CRI Compatibility | Full | Full | Partial | Full |
-| Filesystem Sharing | ✓ | ✓ | ✗ | ✓ |
-| Device Hotplug | ✓ | ✓ | ✗ | ✓ |
-| VFIO/Passthrough | ✓ | ✓ | ✗ | ✓ |
-| CPU/Memory Hotplug | ✓ | ✓ | ✗ | ✓ |
-| Security Isolation | Good | Excellent (seccomp) | Excellent | Excellent |
-| Startup Latency | Good | Excellent | Excellent | Best |
-| Resource Overhead | Medium | Low | Lowest | Lowest |
+### Summary
 
-## Choosing a Hypervisor
-
-### Decision Matrix
-
-| Requirement | Recommended Hypervisor |
-|-------------|------------------------|
-| Full CRI API compatibility | QEMU, Cloud Hypervisor, Dragonball |
-| Device passthrough (VFIO) | QEMU, Cloud Hypervisor, Dragonball |
-| Minimal resource overhead | Dragonball, Firecracker |
-| Fastest startup time | Dragonball, Firecracker |
-| Serverless/FaaS | Dragonball, Firecracker |
-| Production workloads | Dragonball, QEMU |
-| Memory/CPU resizing | Dragonball, Cloud Hypervisor, QEMU |
-| Maximum security isolation | Cloud Hypervisor (seccomp), Firecracker, Dragonball |
-| Multi-architecture | QEMU |
-
-### Recommendations
-
-**For Most Users:** Use the default Dragonball VMM with the Kata Containers Rust runtime. It provides the best balance of performance, security, and container density.
-
-**For Device Passthrough:** Use QEMU, Cloud Hypervisor, or Dragonball if you require VFIO device assignment.
-
-**For Serverless:** Use Dragonball or Firecracker for ultra-lightweight, single-tenant microVMs.
-
-**For Legacy/Ecosystem Compatibility:** Use QEMU for its extensive hardware emulation and multi-architecture support.
-
-## Hypervisor Configuration
-
-### Configuration Files
-
-Each hypervisor has a dedicated configuration file:
-
-| Hypervisor | Rust Runtime Configuration | Go Runtime Configuration |
-|------------|----------------|-----------------|
-| QEMU |`configuration-qemu-runtime-rs.toml` |`configuration-qemu.toml` |
-| Cloud Hypervisor | `configuration-cloud-hypervisor.toml` | `configuration-clh.toml` |
-| Firecracker | `configuration-rs-fc.toml` | `configuration-fc.toml` |
-| Dragonball | `configuration-dragonball.toml` (default) | `No` |
-
-> **Note:** Configuration files are typically installed in `/opt/kata/share/defaults/kata-containers/` or  `/opt/kata/share/defaults/kata-containers/runtime-rs/` or `/usr/share/defaults/kata-containers/`.
-
-### Switching Hypervisors
-
-Use the `kata-manager` tool to switch the configured hypervisor:
-
-```bash
-# List available hypervisors
-$ kata-manager -L
-
-# Switch to a different hypervisor
-$ sudo kata-manager -S <hypervisor-name>
-```
-
-For detailed instructions, see the [`kata-manager` documentation](../../utils/README.md).
-
-## Hypervisor Versions
-
-The following versions are used in this release (from [versions.yaml](../../versions.yaml)):
-
-| Hypervisor | Version | Repository |
-|------------|---------|------------|
-| Cloud Hypervisor | v51.1 | https://github.com/cloud-hypervisor/cloud-hypervisor |
-| Firecracker | v1.12.1 | https://github.com/firecracker-microvm/firecracker |
-| QEMU | v10.2.1 | https://github.com/qemu/qemu |
-| Dragonball | builtin | https://github.com/kata-containers/kata-containers/tree/main/src/dragonball |
-
-> **Note:** Dragonball is integrated into the Kata Containers Rust runtime and does not have a separate version number.
-> For the latest hypervisor versions, see the [versions.yaml](../../versions.yaml) file in the Kata Containers repository.
-
-## References
-
-- [Kata Containers Architecture](./architecture/README.md)
-- [Configuration Guide](../../src/runtime/README.md#configuration)
-- [QEMU Documentation](https://www.qemu.org/documentation/)
-- [Cloud Hypervisor Documentation](https://github.com/cloud-hypervisor/cloud-hypervisor/blob/main/docs/api.md)
-- [Firecracker Documentation](https://github.com/firecracker-microvm/firecracker/tree/main/docs)
-- [Dragonball Source](https://github.com/kata-containers/kata-containers/tree/main/src/dragonball)
-
-[KVM]: https://en.wikipedia.org/wiki/Kernel-based_Virtual_Machine
-[QEMU]: https://www.qemu.org
-[Cloud Hypervisor]: https://github.com/cloud-hypervisor/cloud-hypervisor
-[Firecracker]: https://github.com/firecracker-microvm/firecracker
-[`Dragonball`]: https://github.com/kata-containers/kata-containers/tree/main/src/dragonball
+| Solution | release introduced | brief summary |
+|-|-|-|
+| Cloud Hypervisor | 1.10 | upstream Cloud Hypervisor with rich feature support, e.g. hotplug, VFIO and FS sharing|
+| Firecracker | 1.5 | upstream Firecracker, rust-VMM based, no VFIO, no FS sharing, no memory/CPU hotplug |
+| QEMU | 1.0 | upstream QEMU, with support for hotplug and filesystem sharing |
+| StratoVirt | 3.3 | upstream StratoVirt with FS sharing and virtio block hotplug, no VFIO, no CPU/memory resize |

docs/how-to/README.md

@@ -3,9 +3,9 @@
 ## Kubernetes Integration
 
 - [Run Kata containers with `crictl`](run-kata-with-crictl.md)
+- [Run Kata Containers with Kubernetes](run-kata-with-k8s.md)
 - [How to use Kata Containers and Containerd](containerd-kata.md)
 - [How to use Kata Containers and containerd with Kubernetes](how-to-use-k8s-with-containerd-and-kata.md)
-- [How to use Kata Containers and CRI-O with Kubernetes](how-to-use-k8s-with-crio-and-kata.md)
 - [Kata Containers and service mesh for Kubernetes](service-mesh.md)
 - [How to import Kata Containers logs into Fluentd](how-to-import-kata-logs-with-fluentd.md)
 
@@ -50,4 +50,3 @@
 - [How to pull images in the guest](how-to-pull-images-in-guest-with-kata.md)
 - [How to use mem-agent to decrease the memory usage of Kata container](how-to-use-memory-agent.md)
 - [How to use seccomp with runtime-rs](how-to-use-seccomp-with-runtime-rs.md)
-- [How to use passthroughfd-IO with runtime-rs and Dragonball](how-to-use-passthroughfd-io-within-runtime-rs.md)

docs/how-to/containerd-kata.md

@@ -5,7 +5,7 @@ and [Kata Containers](https://katacontainers.io). The containerd provides not on
 command line tool, but also the [CRI](https://kubernetes.io/blog/2016/12/container-runtime-interface-cri-in-kubernetes/)
 interface for [Kubernetes](https://kubernetes.io) and other CRI clients.
 
-This document is primarily written for Kata Containers v3.28 or above, and containerd v1.7.0 or above.
+This document is primarily written for Kata Containers v1.5.0-rc2 or above, and containerd v1.2.0 or above.
 Previous versions are addressed here, but we suggest users upgrade to the newer versions for better support.
 
 ## Concepts
@@ -14,7 +14,7 @@ Previous versions are addressed here, but we suggest users upgrade to the newer
 
 [`RuntimeClass`](https://kubernetes.io/docs/concepts/containers/runtime-class/) is a Kubernetes feature first
 introduced in Kubernetes 1.12 as alpha. It is the feature for selecting the container runtime configuration to
-use to run a pod's containers. This feature is supported in `containerd` since [v1.2.0](https://github.com/containerd/containerd/releases/tag/v1.2.0).
+use to run a pod’s containers. This feature is supported in `containerd` since [v1.2.0](https://github.com/containerd/containerd/releases/tag/v1.2.0).
 
 Before the `RuntimeClass` was introduced, Kubernetes was not aware of the difference of runtimes on the node. `kubelet`
 creates Pod sandboxes and containers through CRI implementations, and treats all the Pods equally. However, there
@@ -123,56 +123,18 @@ The following sections outline how to add Kata Containers to the configurations.
 
 #### Kata Containers as a `RuntimeClass`
 
-For Kubernetes users, we suggest using `RuntimeClass` to select Kata Containers as the runtime for untrusted workloads. The configuration is as follows:
-
-- Kata Containers v3.28.0 or above
-- Containerd v1.7.0 or above
-- Kubernetes v1.33 or above
+For
+- Kata Containers v1.5.0 or above (including `1.5.0-rc`)
+- Containerd v1.2.0 or above
+- Kubernetes v1.12.0 or above
 
 The `RuntimeClass` is suggested.
 
-The following example registers custom runtimes into containerd:
-
-You can check the detailed information about the configuration of containerd in the [Containerd config documentation](https://github.com/containerd/containerd/blob/main/docs/cri/config.md).
-
-+ In containerd 2.x
-
-```toml
-version = 3
-[plugins."io.containerd.cri.v1.runtime".containerd]
-  [plugins."io.containerd.cri.v1.runtime".containerd.runtimes]
-    [plugins."io.containerd.cri.v1.runtime".containerd.runtimes.runc]
-      runtime_type = "io.containerd.runc.v2"
-    [plugins."io.containerd.cri.v1.runtime".containerd.runtimes.kata]
-      runtime_type = "io.containerd.kata.v2"
-      [plugins."io.containerd.cri.v1.runtime".containerd.runtimes.kata.options]
-        ConfigPath = "/opt/kata/share/defaults/kata-containers/configuration.toml"
-```
-
-+ In containerd 1.7.x
-
-```toml
-version = 2
-[plugins."io.containerd.grpc.v1.cri".containerd]
-  [plugins."io.containerd.grpc.v1.cri".containerd.runtimes]
-    [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc]
-      runtime_type = "io.containerd.runc.v2"
-    [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.kata]
-      runtime_type = "io.containerd.kata.v2"
-      [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.kata.options]
-        ConfigPath = "/opt/kata/share/defaults/kata-containers/configuration.toml"
-```
-
 The following configuration includes two runtime classes:
-
-- `plugins.<X>.containerd.runtimes.runc`: the runc, and it is the default runtime.
-- `plugins.<X>.containerd.runtimes.kata`: The function in containerd (reference [the document here](https://github.com/containerd/containerd/tree/main/core/runtime/v2))
+- `plugins.cri.containerd.runtimes.runc`: the runc, and it is the default runtime.
+- `plugins.cri.containerd.runtimes.kata`: The function in containerd (reference [the document here](https://github.com/containerd/containerd/tree/main/core/runtime/v2))
   where the dot-connected string `io.containerd.kata.v2` is translated to `containerd-shim-kata-v2` (i.e. the
-  binary name of the Kata implementation of [Containerd Runtime V2 (Shim API)](https://github.com/containerd/containerd/tree/main/core/runtime/v2)). By default, the `containerd-shim-kata-v2` (short of `shimv2`) binary will be installed under the path of `/usr/local/bin/`.
-
-And `<X>` is `io.containerd.cri.v1.runtime` for containerd v2.x and `io.containerd.grpc.v1.cri` for containerd v1.7.x.
-
-+ In containerd 1.7.x
+  binary name of the Kata implementation of [Containerd Runtime V2 (Shim API)](https://github.com/containerd/containerd/tree/main/core/runtime/v2)).
 
 ```toml
     [plugins.cri.containerd]
@@ -187,7 +149,7 @@ And `<X>` is `io.containerd.cri.v1.runtime` for containerd v2.x and `io.containe
             CriuPath = ""
             CriuWorkPath = ""
             IoGid = 0
-      [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.kata]
+      [plugins.cri.containerd.runtimes.kata]
          runtime_type = "io.containerd.kata.v2"
          privileged_without_host_devices = true
          pod_annotations = ["io.katacontainers.*"]
@@ -196,71 +158,13 @@ And `<X>` is `io.containerd.cri.v1.runtime` for containerd v2.x and `io.containe
             ConfigPath = "/opt/kata/share/defaults/kata-containers/configuration.toml"
 ```
 
-+ In containerd 2.x
-
-```toml
-    [plugins."io.containerd.cri.v1.runtime".containerd]
-      no_pivot = false
-    [plugins."io.containerd.cri.v1.runtime".containerd.runtimes]
-      [plugins."io.containerd.cri.v1.runtime".containerd.runtimes.runc]
-         privileged_without_host_devices = false
-         runtime_type = "io.containerd.runc.v2"
-        [plugins."io.containerd.cri.v1.runtime".containerd.runtimes.runc.options]
-            BinaryName = ""
-            CriuImagePath = ""
-            CriuPath = ""
-            CriuWorkPath = ""
-            IoGid = 0
-      [plugins."io.containerd.cri.v1.runtime".containerd.runtimes.kata]
-         runtime_type = "io.containerd.kata.v2"
-         privileged_without_host_devices = true
-         pod_annotations = ["io.katacontainers.*"]
-         container_annotations = ["io.katacontainers.*"]
-         [plugins."io.containerd.cri.v1.runtime".containerd.runtimes.kata.options]
-            ConfigPath = "/opt/kata/share/defaults/kata-containers/configuration.toml"
-```
-
 `privileged_without_host_devices` tells containerd that a privileged Kata container should not have direct access to all host devices. If unset, containerd will pass all host devices to Kata container, which may cause security issues.
 
 `pod_annotations` is the list of pod annotations passed to both the pod sandbox as well as container through the OCI config.
 
 `container_annotations` is the list of container annotations passed through to the OCI config of the containers.
 
-This `ConfigPath` option is optional. If you want to use a different configuration file, you can specify the path of the configuration file with `ConfigPath` in the containerd configuration file. We use containerd 2.x configuration as an example here, and the configuration for containerd 1.7.x is similar, just replace `io.containerd.cri.v1.runtime` with `io.containerd.grpc.v1.cri`.
-
-```toml
-         [plugins."io.containerd.cri.v1.runtime".containerd.runtimes.kata.options]
-            ConfigPath = "/opt/kata/share/defaults/kata-containers/configuration-qemu.toml"
-```
-
-> **Note:** In this example, the specified `ConfigPath` is valid in Kubernetes/Containerd workflow with containerd v1.7+ but doesn't work with ctr and nerdctl.
-
-If you do not specify it, `shimv2` first tries to get the configuration file from the environment variable `KATA_CONF_FILE`. If you want to adopt this way, you should first create a shell script as `containerd-shim-kata-v2` which is placed under the path of `/usr/local/bin/`. The following is an example of the shell script `containerd-shim-kata-qemu-v2` which specifies the configuration file with `KATA_CONF_FILE`
-
-> **Note:** Just use containerd 2.x configuration as an example, the configuration for containerd 1.7.x is similar, just replace `io.containerd.cri.v1.runtime` with `io.containerd.grpc.v1.cri`
-
-```shell
-~$ cat /usr/local/bin/containerd-shim-kata-qemu-v2
-#!/bin/bash
-KATA_CONF_FILE=/opt/kata/share/defaults/kata-containers/configuration-qemu.toml /opt/kata/bin/containerd-shim-kata-v2 "$@"
-```
-
-And then just reference it in the configuration of containerd:
-
-```toml
-      [plugins."io.containerd.cri.v1.runtime".containerd.runtimes.kata-qemu]
-         runtime_type = "io.containerd.kata-qemu.v2"
-```
-
-Finally you can run a Kata container with the runtime `io.containerd.kata-qemu.v2`:
-
-```shell
-$ sudo ctr run --cni --runtime io.containerd.kata-qemu.v2 -t --rm docker.io/library/busybox:latest hello sh
-```
-
-> **Note:** The `KATA_CONF_FILE` environment variable is valid in both Kubernetes/Containerd workflow with containerd and containerd tools(ctr, nerdctl, etc.) scenarios.
-
-If neither are set, shimv2 will use the default Kata configuration file paths (`/etc/kata-containers/configuration.toml` and `/usr/share/defaults/kata-containers/configuration.toml` and `/opt/kata/share/defaults/kata-containers/configuration.toml`).
+This `ConfigPath` option is optional. If you do not specify it, shimv2 first tries to get the configuration file from the environment variable `KATA_CONF_FILE`. If neither are set, shimv2 will use the default Kata configuration file paths (`/etc/kata-containers/configuration.toml` and `/usr/share/defaults/kata-containers/configuration.toml`).
 
 #### Kata Containers as the runtime for untrusted workload
 
@@ -269,20 +173,18 @@ for an untrusted workload. With the following configuration, you can run trusted
 and then, run an untrusted workload with Kata Containers:
 
 ```toml
-    [plugins."io.containerd.grpc.v1.cri".containerd]
-    # "plugins."io.containerd.grpc.v1.cri".containerd.default_runtime" is the runtime to use in containerd.
-    [plugins."io.containerd.grpc.v1.cri".containerd.default_runtime]
+    [plugins.cri.containerd]
+    # "plugins.cri.containerd.default_runtime" is the runtime to use in containerd.
+    [plugins.cri.containerd.default_runtime]
       # runtime_type is the runtime type to use in containerd e.g. io.containerd.runtime.v1.linux
       runtime_type = "io.containerd.runtime.v1.linux"
 
-    # "plugins."io.containerd.grpc.v1.cri".containerd.untrusted_workload_runtime" is a runtime to run untrusted workloads on it.
-    [plugins."io.containerd.grpc.v1.cri".containerd.untrusted_workload_runtime]
+    # "plugins.cri.containerd.untrusted_workload_runtime" is a runtime to run untrusted workloads on it.
+    [plugins.cri.containerd.untrusted_workload_runtime]
       # runtime_type is the runtime type to use in containerd e.g. io.containerd.runtime.v1.linux
       runtime_type = "io.containerd.kata.v2"
 ```
 
-> **Note:** The `untrusted_workload_runtime` is deprecated since containerd v1.7.0, and it is recommended to use `RuntimeClass` instead.
-
 You can find more information on the [Containerd config documentation](https://github.com/containerd/containerd/blob/main/docs/cri/config.md)
 
 #### Kata Containers as the default runtime
@@ -290,8 +192,8 @@ You can find more information on the [Containerd config documentation](https://g
 If you want to set Kata Containers as the only runtime in the deployment, you can simply configure as follows:
 
 ```toml
-    [plugins."io.containerd.grpc.v1.cri".containerd]
-    [plugins."io.containerd.grpc.v1.cri".containerd.default_runtime]
+    [plugins.cri.containerd]
+    [plugins.cri.containerd.default_runtime]
       runtime_type = "io.containerd.kata.v2"
 ```
 
@@ -344,14 +246,11 @@ debug: true
 
 ### Launch containers with `ctr` command line
 
-> **Note:** With containerd command tool `ctr`, the `ConfigPath` is not supported, and the configuration file should be explicitly specified with the option `--runtime-config-path`, otherwise, it'll use the default configurations.
-
 To run a container with Kata Containers through the containerd command line, you can run the following:
 
 ```bash
 $ sudo ctr image pull docker.io/library/busybox:latest
-$ CONFIG_PATH="/opt/kata/share/defaults/kata-containers/configuration-qemu.toml"
-$ sudo ctr run --cni --runtime io.containerd.kata.v2 --runtime-config-path $CONFIG_PATH -t --rm docker.io/library/busybox:latest hello sh
+$ sudo ctr run --cni --runtime io.containerd.run.kata.v2 -t --rm docker.io/library/busybox:latest hello sh
 ```
 
 This launches a BusyBox container named `hello`, and it will be removed by `--rm` after it quits.
@@ -361,9 +260,7 @@ loopback interface is created.
 ### Launch containers using `ctr` command line with rootfs bundle
 
 #### Get rootfs
-
 Use the script to create rootfs
-
 ```bash
 ctr i pull quay.io/prometheus/busybox:latest
 ctr i export rootfs.tar quay.io/prometheus/busybox:latest
@@ -381,9 +278,7 @@ for ((i=0;i<$(cat ${layers_dir}/manifest.json | jq -r ".[].Layers | length");i++
   tar -C ${rootfs_dir} -xf ${layers_dir}/$(cat ${layers_dir}/manifest.json | jq -r ".[].Layers[${i}]")
 done
 ```
-
 #### Get `config.json`
-
 Use runc spec to generate `config.json`
 ```bash
 cd ./bundle/rootfs
@@ -400,13 +295,10 @@ Change the root `path` in `config.json` to the absolute path of rootfs
 ```
 
 #### Run container
-
 ```bash
-CONFIG_PATH="/opt/kata/share/defaults/kata-containers/configuration-qemu.toml"
-sudo ctr run -d --runtime io.containerd.kata.v2 --runtime-config-path $CONFIG_PATH --config bundle/config.json hello
+sudo ctr run -d --runtime io.containerd.run.kata.v2 --config bundle/config.json hello
 sudo ctr t exec --exec-id ${ID} -t hello sh
 ```
-
 ### Launch Pods with `crictl` command line
 
 With the `crictl` command line of `cri-tools`, you can specify runtime class with `-r` or `--runtime` flag.

docs/how-to/how-to-run-kata-containers-with-SNP-VMs.md

@@ -96,10 +96,6 @@ path = "/path/to/qemu/build/qemu-system-x86_64"
 ```toml
 shared_fs = "virtio-9p"
 ```
-- Use `blockfile` snapshotter: Since virtio-fs remains unsupported due to bugs in QEMU snp-v3, and virtio-9p is no longer supported in runtime-rs, it is recommended to use the blockfile snapshotter. This allows container images to be managed via block devices without relying on a shared file system. To enable this, set the `snapshotter` to `blockfile` in the containerd config file, please refer to [blockfile guide](https://github.com/containerd/containerd/blob/main/docs/snapshotters/blockfile.md) for more information. Additionally, shared_fs should be set to "none" since no shared file system is used.
-```toml
-shared_fs = "none"
-```
 - Disable `virtiofsd` since it is no longer required (comment out)
 ```toml
 # virtio_fs_daemon = "/usr/libexec/virtiofsd"

docs/how-to/how-to-run-kata-containers-with-kinds-of-Block-Volumes.md

@@ -12,11 +12,11 @@ Currently, there is no widely applicable and convenient method available for use
 
 According to the proposal, it requires to use the `kata-ctl direct-volume` command to add a direct assigned block volume device to the Kata Containers runtime.
 
-And then with the help of method [get_volume_mount_info](https://github.com/kata-containers/kata-containers/blob/099b4b0d0e3db31b9054e7240715f0d7f51f9a1c/src/libs/kata-types/src/mount.rs#L95), get information from JSON file: `(mountInfo.json)` and parse them into structure [Direct Volume Info](https://github.com/kata-containers/kata-containers/blob/099b4b0d0e3db31b9054e7240715f0d7f51f9a1c/src/libs/kata-types/src/mount.rs#L70) which is used to save device-related information.
+And then with the help of method [get_volume_mount_info](https://github.com/kata-containers/kata-containers/blob/099b4b0d0e3db31b9054e7240715f0d7f51f9a1c/src/libs/kata-types/src/mount.rs#L95), get information from JSON file: `(mountinfo.json)` and parse them into structure [Direct Volume Info](https://github.com/kata-containers/kata-containers/blob/099b4b0d0e3db31b9054e7240715f0d7f51f9a1c/src/libs/kata-types/src/mount.rs#L70) which is used to save device-related information.
 
-We only fill the `mountInfo.json`, such as `device` ,`volume-type`, `fstype`, `metadata` and `options`, which correspond to the fields in [Direct Volume Info](https://github.com/kata-containers/kata-containers/blob/099b4b0d0e3db31b9054e7240715f0d7f51f9a1c/src/libs/kata-types/src/mount.rs#L70), to describe a device.
+We only fill the `mountinfo.json`, such as `device` ,`volume_type`, `fs_type`, `metadata` and `options`, which correspond to the fields in [Direct Volume Info](https://github.com/kata-containers/kata-containers/blob/099b4b0d0e3db31b9054e7240715f0d7f51f9a1c/src/libs/kata-types/src/mount.rs#L70), to describe a device.
 
-The JSON file `mountInfo.json` placed in a sub-path `/kubelet/kata-test-vol-001/volume001` which under fixed path `/run/kata-containers/shared/direct-volumes/`.
+The JSON file `mountinfo.json` placed in a sub-path `/kubelet/kata-test-vol-001/volume001` which under fixed path `/run/kata-containers/shared/direct-volumes/`.
 And the full path looks like: `/run/kata-containers/shared/direct-volumes/kubelet/kata-test-vol-001/volume001`, But for some security reasons. it is
 encoded as `/run/kata-containers/shared/direct-volumes/L2t1YmVsZXQva2F0YS10ZXN0LXZvbC0wMDEvdm9sdW1lMDAx`.
 
@@ -47,18 +47,18 @@ $ sudo mkfs.ext4 /tmp/stor/rawdisk01.20g
 ```json
 {
   "device": "/tmp/stor/rawdisk01.20g",
-  "volume-type": "directvol",
-  "fstype": "ext4",
+  "volume_type": "directvol",
+  "fs_type": "ext4",
   "metadata":"{}",
   "options": []
 }
 ```
 
 ```bash
-$ sudo kata-ctl direct-volume add /kubelet/kata-direct-vol-002/directvol002 "{\"device\": \"/tmp/stor/rawdisk01.20g\", \"volume-type\": \"directvol\", \"fstype\": \"ext4\", \"metadata\":"{}", \"options\": []}"
+$ sudo kata-ctl direct-volume add /kubelet/kata-direct-vol-002/directvol002 "{\"device\": \"/tmp/stor/rawdisk01.20g\", \"volume_type\": \"directvol\", \"fs_type\": \"ext4\", \"metadata\":"{}", \"options\": []}"
 $# /kubelet/kata-direct-vol-002/directvol002 <==> /run/kata-containers/shared/direct-volumes/W1lMa2F0ZXQva2F0YS10a2F0DAxvbC0wMDEvdm9sdW1lMDAx
 $ cat W1lMa2F0ZXQva2F0YS10a2F0DAxvbC0wMDEvdm9sdW1lMDAx/mountInfo.json
-{"volume-type":"directvol","device":"/tmp/stor/rawdisk01.20g","fstype":"ext4","metadata":{},"options":[]}
+{"volume_type":"directvol","device":"/tmp/stor/rawdisk01.20g","fs_type":"ext4","metadata":{},"options":[]}
 ```
 
 #### Run a Kata container with direct block device volume
@@ -76,7 +76,7 @@ $ sudo ctr run -t --rm --runtime io.containerd.kata.v2 --mount type=directvol,sr
 > **Tip:** It only supports `vfio-pci` based PCI device passthrough mode.
 
 In this scenario, the device's host kernel driver will be replaced by `vfio-pci`, and IOMMU group ID generated.
-And either device's BDF or its VFIO IOMMU group ID in `/dev/vfio/` is fine for "device" in `mountInfo.json`.
+And either device's BDF or its VFIO IOMMU group ID in `/dev/vfio/` is fine for "device" in `mountinfo.json`.
 
 ```bash
 $ lspci -nn -k -s 45:00.1
@@ -92,15 +92,15 @@ $ ls /sys/kernel/iommu_groups/110/devices/
 
 #### setup VFIO device for kata-containers
 
-First, configure the `mountInfo.json`, as below:
+First, configure the `mountinfo.json`, as below:
 
 - (1) device with `BB:DD:F`
 
 ```json
 {
   "device": "45:00.1",
-  "volume-type": "vfiovol",
-  "fstype": "ext4",
+  "volume_type": "vfiovol",
+  "fs_type": "ext4",
   "metadata":"{}",
   "options": []
 }
@@ -111,8 +111,8 @@ First, configure the `mountInfo.json`, as below:
 ```json
 {
   "device": "0000:45:00.1",
-  "volume-type": "vfiovol",
-  "fstype": "ext4",
+  "volume_type": "vfiovol",
+  "fs_type": "ext4",
   "metadata":"{}",
   "options": []
 }
@@ -123,8 +123,8 @@ First, configure the `mountInfo.json`, as below:
 ```json
 {
   "device": "/dev/vfio/110",
-  "volume-type": "vfiovol",
-  "fstype": "ext4",
+  "volume_type": "vfiovol",
+  "fs_type": "ext4",
   "metadata":"{}",
   "options": []
 }
@@ -133,10 +133,10 @@ First, configure the `mountInfo.json`, as below:
 Second, run kata-containers with device(`/dev/vfio/110`) as an example:
 
 ```bash
-$ sudo kata-ctl direct-volume add /kubelet/kata-vfio-vol-003/vfiovol003 "{\"device\": \"/dev/vfio/110\", \"volume-type\": \"vfiovol\", \"fstype\": \"ext4\", \"metadata\":"{}", \"options\": []}"
+$ sudo kata-ctl direct-volume add /kubelet/kata-vfio-vol-003/vfiovol003 "{\"device\": \"/dev/vfio/110\", \"volume_type\": \"vfiovol\", \"fs_type\": \"ext4\", \"metadata\":"{}", \"options\": []}"
 $ # /kubelet/kata-vfio-vol-003/directvol003 <==> /run/kata-containers/shared/direct-volumes/F0va22F0ZvaS12F0YS10a2F0DAxvbC0F0ZXvdm9sdF0Z0YSx
 $ cat F0va22F0ZvaS12F0YS10a2F0DAxvbC0F0ZXvdm9sdF0Z0YSx/mountInfo.json
-{"volume-type":"vfiovol","device":"/dev/vfio/110","fstype":"ext4","metadata":{},"options":[]}
+{"volume_type":"vfiovol","device":"/dev/vfio/110","fs_type":"ext4","metadata":{},"options":[]}
 ```
 
 #### Run a Kata container with VFIO block device based volume
@@ -190,25 +190,25 @@ be passed to Hypervisor, such as Dragonball, Cloud-Hypervisor, Firecracker or QE
 
 First, `mkdir` a sub-path `kubelet/kata-test-vol-001/` under `/run/kata-containers/shared/direct-volumes/`.
 
-Second, fill fields in `mountInfo.json`, it looks like as below:
+Second, fill fields in `mountinfo.json`, it looks like as below:
 ```json
 {
   "device": "/tmp/vhu-targets/vhost-blk-rawdisk01.sock",
-  "volume-type": "spdkvol",
-  "fstype": "ext4",
+  "volume_type": "spdkvol",
+  "fs_type": "ext4",
   "metadata":"{}",
   "options": []
 }
 ```
 
-Third, with the help of `kata-ctl direct-volume` to add block device to generate `mountInfo.json`, and run a kata container with `--mount`.
+Third, with the help of `kata-ctl direct-volume` to add block device to generate `mountinfo.json`, and run a kata container with `--mount`.
 
 ```bash
 $ # kata-ctl direct-volume add
-$ sudo kata-ctl direct-volume add /kubelet/kata-test-vol-001/volume001 "{\"device\": \"/tmp/vhu-targets/vhost-blk-rawdisk01.sock\", \"volume-type\":\"spdkvol\", \"fstype\": \"ext4\", \"metadata\":"{}", \"options\": []}"
+$ sudo kata-ctl direct-volume add /kubelet/kata-test-vol-001/volume001 "{\"device\": \"/tmp/vhu-targets/vhost-blk-rawdisk01.sock\", \"volume_type\":\"spdkvol\", \"fs_type\": \"ext4\", \"metadata\":"{}", \"options\": []}"
 $ # /kubelet/kata-test-vol-001/volume001 <==> /run/kata-containers/shared/direct-volumes/L2t1YmVsZXQva2F0YS10ZXN0LXZvbC0wMDEvdm9sdW1lMDAx
 $ cat L2t1YmVsZXQva2F0YS10ZXN0LXZvbC0wMDEvdm9sdW1lMDAx/mountInfo.json
-$ {"volume-type":"spdkvol","device":"/tmp/vhu-targets/vhost-blk-rawdisk01.sock","fstype":"ext4","metadata":{},"options":[]}
+$ {"volume_type":"spdkvol","device":"/tmp/vhu-targets/vhost-blk-rawdisk01.sock","fs_type":"ext4","metadata":{},"options":[]}
 ```
 
 As `/run/kata-containers/shared/direct-volumes/` is a fixed path , we will be able to run a kata pod with `--mount` and set

docs/how-to/how-to-set-prometheus-in-k8s.md

@@ -17,7 +17,7 @@ You must have a running Kubernetes cluster first. If not, [install a Kubernetes
 Also you should ensure that `kubectl` working correctly.
 
 > **Note**: More information about Kubernetes integrations:
->   - [Run Kata Containers with Kubernetes](how-to-use-k8s-with-crio-and-kata.md)
+>   - [Run Kata Containers with Kubernetes](run-kata-with-k8s.md)
 >   - [How to use Kata Containers and Containerd](containerd-kata.md)
 >   - [How to use Kata Containers and containerd with Kubernetes](how-to-use-k8s-with-containerd-and-kata.md)
 

docs/how-to/how-to-set-sandbox-config-kata.md

@@ -46,8 +46,6 @@ There are several kinds of Kata configurations and they are listed below.
 | `io.katacontainers.config.hypervisor.block_device_cache_noflush` | `boolean` | Denotes whether flush requests for the device are ignored |
 | `io.katacontainers.config.hypervisor.block_device_cache_set` | `boolean` | cache-related options will be set to block devices or not |
 | `io.katacontainers.config.hypervisor.block_device_driver` | string | the driver to be used for block device, valid values are `virtio-blk`, `virtio-scsi`, `nvdimm`|
-| `io.katacontainers.config.hypervisor.blk_logical_sector_size` | uint32 | logical sector size in bytes reported by block devices to the guest (0 = hypervisor default, must be a power of 2 between 512 and 65536) |
-| `io.katacontainers.config.hypervisor.blk_physical_sector_size` | uint32 | physical sector size in bytes reported by block devices to the guest (0 = hypervisor default, must be a power of 2 between 512 and 65536) |
 | `io.katacontainers.config.hypervisor.cpu_features` | `string` | Comma-separated list of CPU features to pass to the CPU (QEMU) |
 | `io.katacontainers.config.hypervisor.default_max_vcpus` | uint32| the maximum number of vCPUs allocated for the VM by the hypervisor |
 | `io.katacontainers.config.hypervisor.default_memory` | uint32| the memory assigned for a VM by the hypervisor in `MiB` |

docs/how-to/how-to-use-passthroughfd-io-within-runtime-rs.md

@@ -1,159 +0,0 @@
-# How to Use Passthrough-FD IO within Runtime-rs and Dragonball
-
-This document describes the Passthrough-FD (pass-fd) technology implemented in Kata Containers to optimize IO performance. By bypassing the intermediate proxy layers, this technology significantly reduces latency and CPU overhead for container IO streams.
-
-## Important Limitation
-
-Before diving into the technical details, please note the following restriction:
-
-- Exclusive Support for Dragonball VMM: This feature is currently implemented only for Kata Containers' built-in VMM, Dragonball.
-- Unsupported VMMs: Other VMMs such as QEMU, Cloud Hypervisor, and Firecracker do not support this feature at this time.
-
-## Overview
-
-The original IO implementation in Kata Containers suffered from an excessively long data path, leading to poor efficiency. For instance, copying a 10GB file could take as long as 10 minutes.
-
-To address this, Kata AC member @lifupan and @frezcirno introduced a series of optimizations using passthrough-fd technology. This approach allows the VMM to directly handle file descriptors (FDs), dramatically improving IO throughput.
-
-## Traditional IO Path
-
-Before the introduction of Passthrough-FD, Kata's IO streams were implemented using `ttrpc + virtio-vsock`.
-
-The data flow was as follows:
-
-```mermaid
-graph LR
-    subgraph Host ["Host"]
-        direction LR
-        Containerd["Containerd"]
-
-        subgraph KS ["kata-shim"]
-            buffer(("buffer"))
-        end
-
-        Vsock["vsock"]
-
-        subgraph VM ["vm"]
-            Agent["kata-agent"]
-            Container["container"]
-        end
-    end
-
-    Containerd -->|stdin| buffer
-    buffer --> Vsock
-    Vsock --> Agent
-    Agent -.-> Container
-
-    %% Style Rendering
-    style Host fill:#f0f8ff,stroke:#333,stroke-dasharray: 5 5
-    style VM fill:#fff9c4,stroke:#e0e0e0
-    style buffer fill:#c8e6c9,stroke:#ff9800,stroke-dasharray: 5 5
-    style Vsock fill:#bbdefb,stroke:#2196f3
-    style Containerd fill:#f5f5f5,stroke:#333
-    style Agent fill:#fff,stroke:#333
-    style Container fill:#fff,stroke:#333
-
-```
-
-The kata-shim (containerd-shim-kata-v2) on the Host opens the FIFO pipes provided by containerd via the shimv2 interface.
-This results in three FDs (stdin, stdout, and stderr).
-The kata-shim manages three separate threads to handle these streams.
-The Bottleneck: kata-shim acts as a "middleman," maintaining three internal buffers. It must read data from the FDs into its own buffers before forwarding them via ttrpc over vsock to the destination.
-This multi-threaded proxying and buffering in the shim layer introduced significant overhead.
-
-
-## What is Passthrough-FD?
-
-Passthrough-FD technology enhances the Dragonball VMM's hybrid-vsock implementation with support for recv-fd.
-
-```mermaid
-graph LR
-    subgraph Host ["Host"]
-        direction LR
-        Containerd["Containerd"]
-
-        Vsock["vsock"]
-
-        subgraph VM ["vm"]
-            Agent["kata-agent"]
-            Container["container"]
-        end
-    end
-
-    Containerd -->|stdin| Vsock
-    Vsock --> Agent
-    Agent -.-> Container
-
-    %% Style Rendering
-    style Host fill:#f0f8ff,stroke:#333,stroke-dasharray: 5 5
-    style VM fill:#fff9c4,stroke:#e0e0e0
-    style Vsock fill:#bbdefb,stroke:#2196f3
-    style Containerd fill:#f5f5f5,stroke:#333
-    style Agent fill:#fff,stroke:#333
-    style Container fill:#fff,stroke:#333
-```
-
-Instead of requiring an intermediate layer to read and forward data, the hybrid-vsock module can now directly receive file descriptors from the Host. This allows the system to "pass through" the host's FDs directly to the kata-agent. By eliminating the proxying logic in kata-shim, the IO stream is effectively connected directly to the guest environment.
-
-## Technical Details
-
-The end-to-end process follows these steps:
-
-```mermaid
-sequenceDiagram
-    autonumber
-
-    box rgb(220,235,255) Guest (VM)
-        participant Agent as kata-agent<br/>(Server)
-        participant VSOCK as AF_VSOCK socket<br/>(Hybrid Vsock)
-    end
-
-    box rgb(255,240,220) Host
-        participant Shim as kata-shim<br/>(Client)
-        participant FIFO as File or FIFO<br/>(stdin/stdout/stderr)
-    end
-
-    Note over Agent: Agent Initialization:<br/>listen() on passfd_listener_port
-
-    Shim->>FIFO: open() to acquire Fd<br/>(for stdin / stdout / stderr)
-
-    Shim->>VSOCK: connect() + send("passfd\n")<br/>+ send_with_fd(Fd, PortA)
-
-    Note over VSOCK,Agent: FD Transfer via Hybrid Vsock<br/>(repeat for stdin-port, stdout-port, stderr-port)
-
-    VSOCK->>Agent: forward connection + Fd + PortA
-
-    Agent->>Agent: accept() → get conn_fd + host-port<br/>save: map[host-port] = conn_fd<br/>(3 entries: stdin-port, stdout-port, stderr-port)
-
-    Shim->>Agent: create_container RPC<br/>(includes stdin-port, stdout-port, stderr-port)
-
-    Agent->>Agent: lookup map[stdin-port] → bind to container stdin<br/>lookup map[stdout-port] → bind to container stdout<br/>lookup map[stderr-port] → bind to container stderr
-
-    Agent-->>Shim: create_container RPC response (OK)
-```
-
-1. Agent Initialization: The kata-agent starts a server listening on the port specified by passfd_listener_port.
-2. FD Transfer: During the container creation phase, the kata-shim sends the FDs for stdin, stdout, and stderr to the Dragonball hybrid-vsock module using the sendfd mechanism.
-3. Connection Establishment: Through hybrid-vsock, these FDs connect to the server started by the agent in Step 1.
-4. Identification: The agent's server calls accept() to obtain the connection FD and a corresponding host-port. It saves the connection using the host-port as a unique identifier. At this stage, the agent has three established connections (identified by stdin-port, stdout-port, and stderr-port).
-5. RPC Mapping: When kata-shim invokes the create_container RPC, it includes these three port identifiers in the request.
-6. Final Binding: Upon receiving the RPC, the agent retrieves the saved connections using the provided ports and binds them directly to the container's standard IO streams.
-
-
-## How to enable PassthroughFD IO within Configuration?
-
-The Passthrough-FD feature is controlled by two main parameters in the Kata configuration file:
-
-- use_passfd_io: A boolean flag to enable or disable the Passthrough-FD IO feature.
-- passfd_listener_port: Specifies the port on which the kata-agent listens for FD connections. The default value is 1027.
-To enable Passthrough-FD IO, set use_passfd_io to true in the configuration file:
-
-```toml
-...
-# If enabled, the runtime will attempt to use fd passthrough feature for process io.
-# Note: this feature is only supported by the Dragonball hypervisor.
-use_passfd_io = true
-
-# If fd passthrough io is enabled, the runtime will attempt to use the specified port instead of the default port.
-passfd_listener_port = 1027
-```

docs/how-to/privileged.md

@@ -73,5 +73,5 @@ See below example config:
   privileged_without_host_devices = true
 ```
 
- - [Kata Containers with CRI-O](../how-to/how-to-use-k8s-with-crio-and-kata.md#cri-o)
+ - [Kata Containers with CRI-O](../how-to/run-kata-with-k8s.md#cri-o)
 

docs/how-to/run-kata-with-k8s.md

@@ -1,7 +1,6 @@
-# How to use Kata Containers and CRI-O with Kubernetes
+# Run Kata Containers with Kubernetes
 
 ## Prerequisites
-
 This guide requires Kata Containers available on your system, install-able by following [this guide](../install/README.md).
 
 ## Install a CRI implementation
@@ -10,16 +9,22 @@ Kubernetes CRI (Container Runtime Interface) implementations allow using any
 OCI-compatible runtime with Kubernetes, such as the Kata Containers runtime.
 
 Kata Containers support both the [CRI-O](https://github.com/kubernetes-incubator/cri-o) and
-[containerd](https://github.com/containerd/containerd) CRI implementations. We choose `CRI-O` for our examples in this guide.
+[containerd](https://github.com/containerd/containerd) CRI implementations.
+
+After choosing one CRI implementation, you must make the appropriate configuration
+to ensure it integrates with Kata Containers.
+
+Kata Containers 1.5 introduced the `shimv2` for containerd 1.2.0, reducing the components
+required to spawn pods and containers, and this is the preferred way to run Kata Containers with Kubernetes ([as documented here](../how-to/how-to-use-k8s-with-containerd-and-kata.md#configure-containerd-to-use-kata-containers)).
+
+An equivalent shim implementation for CRI-O is planned.
 
 ### CRI-O
-
 For CRI-O installation instructions, refer to the [CRI-O Tutorial](https://github.com/cri-o/cri-o/blob/main/tutorial.md) page.
 
 The following sections show how to set up the CRI-O snippet configuration file (default path: `/etc/crio/crio.conf`) for Kata.
 
 Unless otherwise stated, all the following settings are specific to the `crio.runtime` table:
-
 ```toml
 # The "crio.runtime" table contains settings pertaining to the OCI
 # runtime used and options for how to set up and manage the OCI runtime.
@@ -28,17 +33,16 @@ Unless otherwise stated, all the following settings are specific to the `crio.ru
 A comprehensive documentation of the configuration file can be found [here](https://github.com/cri-o/cri-o/blob/main/docs/crio.conf.5.md).
 
 > **Note**: After any change to this file, the CRI-O daemon have to be restarted with:
-
 >````
 >$ sudo systemctl restart crio
 >````
 
 #### Kubernetes Runtime Class (CRI-O v1.12+)
-
 The [Kubernetes Runtime Class](https://kubernetes.io/docs/concepts/containers/runtime-class/)
 is the preferred way of specifying the container runtime configuration to run a Pod's containers.
-To use this feature, Kata must added as a runtime handler. This can be done by dropping a `50-kata`
-snippet file into `/etc/crio/crio.conf.d`, with the content shown below:
+To use this feature, Kata must added as a runtime handler. This can be done by
+dropping a `50-kata` snippet file into `/etc/crio/crio.conf.d`, with the
+content shown below:
 
 ```toml
 [crio.runtime.runtimes.kata]
@@ -48,6 +52,13 @@ snippet file into `/etc/crio/crio.conf.d`, with the content shown below:
 	privileged_without_host_devices = true
 ```
 
+
+### containerd
+
+To customize containerd to select Kata Containers runtime, follow our
+"Configure containerd to use Kata Containers" internal documentation
+[here](../how-to/how-to-use-k8s-with-containerd-and-kata.md#configure-containerd-to-use-kata-containers).
+
 ## Install Kubernetes
 
 Depending on what your needs are and what you expect to do with Kubernetes,
@@ -61,16 +72,25 @@ implementation you chose, and the Kubelet service has to be updated accordingly.
 ### Configure for CRI-O
 
 `/etc/systemd/system/kubelet.service.d/0-crio.conf`
-
 ```
 [Service]
 Environment="KUBELET_EXTRA_ARGS=--container-runtime=remote --runtime-request-timeout=15m --container-runtime-endpoint=unix:///var/run/crio/crio.sock"
 ```
 
+### Configure for containerd
+
+`/etc/systemd/system/kubelet.service.d/0-cri-containerd.conf`
+```
+[Service]
+Environment="KUBELET_EXTRA_ARGS=--container-runtime=remote --runtime-request-timeout=15m --container-runtime-endpoint=unix:///run/containerd/containerd.sock"
+```
+For more information about containerd see the "Configure Kubelet to use containerd"
+documentation [here](../how-to/how-to-use-k8s-with-containerd-and-kata.md#configure-kubelet-to-use-containerd).
+
 ## Run a Kubernetes pod with Kata Containers
 
-After you update your Kubelet service based on the CRI implementation you are using, reload and restart Kubelet. Then, start your cluster:
-
+After you update your Kubelet service based on the CRI implementation you
+are using, reload and restart Kubelet. Then, start your cluster:
 ```bash
 $ sudo systemctl daemon-reload
 $ sudo systemctl restart kubelet
@@ -78,6 +98,12 @@ $ sudo systemctl restart kubelet
 # If using CRI-O
 $ sudo kubeadm init --ignore-preflight-errors=all --cri-socket /var/run/crio/crio.sock --pod-network-cidr=10.244.0.0/16
 
+# If using containerd
+$ cat <<EOF | tee kubeadm-config.yaml
+apiVersion: kubeadm.k8s.io/v1beta3
+kind: InitConfiguration
+nodeRegistration:
+  criSocket: "/run/containerd/containerd.sock"
 ---
 kind: KubeletConfiguration
 apiVersion: kubelet.config.k8s.io/v1beta1
@@ -92,7 +118,6 @@ $ export KUBECONFIG=/etc/kubernetes/admin.conf
 ### Allow pods to run in the control-plane node
 
 By default, the cluster will not schedule pods in the control-plane node. To enable control-plane node scheduling:
-
 ```bash
 $ sudo -E kubectl taint nodes --all node-role.kubernetes.io/control-plane-
 ```
@@ -136,7 +161,6 @@ If a pod has the `runtimeClassName` set to `kata`, the CRI plugin runs the pod w
   ```
 
 - Create the pod
-
   ```bash
   $ sudo -E kubectl apply -f nginx-kata.yaml
   ```
@@ -148,7 +172,6 @@ If a pod has the `runtimeClassName` set to `kata`, the CRI plugin runs the pod w
   ```
 
 - Check hypervisor is running
-
   ```bash
   $ ps aux | grep qemu
   ```

docs/install/README.md

@@ -18,3 +18,6 @@ artifacts required to run Kata Containers on Kubernetes.
 * [upgrading document](../Upgrading.md)
 * [developer guide](../Developer-Guide.md)
 * [runtime documentation](../../src/runtime/README.md)
+
+## Kata Containers 3.0 rust runtime installation
+* [installation guide](../install/kata-containers-3.0-rust-runtime-installation-guide.md)

docs/install/kata-containers-3.0-rust-runtime-installation-guide.md

@@ -0,0 +1,116 @@
+# Kata Containers 3.0 rust runtime installation
+The following is an overview of the different installation methods available.
+
+## Prerequisites
+
+Kata Containers 3.0 rust runtime requires nested virtualization or bare metal. Check
+[hardware requirements](/src/runtime/README.md#hardware-requirements) to see if your system is capable of running Kata
+Containers.
+
+### Platform support
+
+Kata Containers 3.0 rust runtime currently runs on 64-bit systems supporting the following
+architectures:
+
+> **Notes:**
+> For other architectures, see https://github.com/kata-containers/kata-containers/issues/4320
+
+| Architecture | Virtualization technology |
+|-|-|
+| `x86_64`| [Intel](https://www.intel.com) VT-x |
+| `aarch64` ("`arm64`")| [ARM](https://www.arm.com) Hyp |
+
+## Packaged installation methods
+
+| Installation method                                  | Description                                                                                  | Automatic updates | Use case                                                                                      | Availability
+|------------------------------------------------------|----------------------------------------------------------------------------------------------|-------------------|-----------------------------------------------------------------------------------------------|----------- |
+| [Using kata-deploy](#kata-deploy-installation)       | The preferred way to deploy the Kata Containers distributed binaries on a Kubernetes cluster | **No!**           | Best way to give it a try on kata-containers on an already up and running Kubernetes cluster. | Yes |
+| [Using official distro packages](#official-packages) | Kata packages provided by Linux distributions official repositories                          | yes               | Recommended for most users. | No |
+| [Automatic](#automatic-installation)                 | Run a single command to install a full system                                                | **No!**           | For those wanting the latest release quickly.                                                 | No |
+| [Manual](#manual-installation)                       | Follow a guide step-by-step to install a working system                                      | **No!**           | For those who want the latest release with more control.                                      | No |
+| [Build from source](#build-from-source-installation) | Build the software components manually                                                       | **No!**           | Power users and developers only.  | Yes |
+
+### Kata Deploy Installation
+
+Follow the [`kata-deploy`](../../tools/packaging/kata-deploy/helm-chart/README.md).
+### Official packages
+`ToDo`
+### Automatic Installation
+`ToDo`
+### Manual Installation
+`ToDo`
+
+## Build from source installation
+
+### Rust Environment Set Up
+
+* Download `Rustup` and install  `Rust`
+    > **Notes:**
+    > For Rust version, please set `RUST_VERSION` to the value of `languages.rust.meta.newest-version key` in [`versions.yaml`](../../versions.yaml) or, if `yq` is available on your system, run `export RUST_VERSION=$(yq read versions.yaml languages.rust.meta.newest-version)`.
+
+    Example for `x86_64`
+    ```
+    $ curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
+    $ source $HOME/.cargo/env
+    $ rustup install ${RUST_VERSION}
+    $ rustup default ${RUST_VERSION}-x86_64-unknown-linux-gnu
+    ```
+
+* Musl support for fully static binary
+
+    Example for `x86_64`
+    ```
+    $ rustup target add x86_64-unknown-linux-musl
+    ```
+* [Musl `libc`](http://musl.libc.org/) install
+
+    Example for musl 1.2.3
+    ```
+    $ curl -O https://git.musl-libc.org/cgit/musl/snapshot/musl-1.2.3.tar.gz
+    $ tar vxf musl-1.2.3.tar.gz
+    $ cd musl-1.2.3/
+    $ ./configure --prefix=/usr/local/
+    $ make && sudo make install
+    ```
+
+
+### Install Kata 3.0 Rust Runtime Shim
+
+```
+$ git clone https://github.com/kata-containers/kata-containers.git
+$ cd kata-containers/src/runtime-rs
+$ make && sudo make install
+```
+After running the command above, the default config file `configuration.toml` will be installed under `/usr/share/defaults/kata-containers/`,  the binary file `containerd-shim-kata-v2` will be installed under `/usr/local/bin/` .
+
+### Install Shim Without Builtin Dragonball VMM
+
+By default, runtime-rs includes the `Dragonball` VMM. To build without the built-in `Dragonball` hypervisor, use `make USE_BUILDIN_DB=false`:
+```bash
+$ cd kata-containers/src/runtime-rs
+$ make USE_BUILDIN_DB=false
+```
+After building, specify the desired hypervisor during installation using `HYPERVISOR`. For example, to use `qemu` or `cloud-hypervisor`:
+
+```
+sudo make install HYPERVISOR=qemu
+```
+or
+```
+sudo make install HYPERVISOR=cloud-hypervisor
+```
+
+### Build Kata Containers Kernel
+Follow the [Kernel installation guide](/tools/packaging/kernel/README.md).
+
+### Build Kata Rootfs
+Follow the [Rootfs installation guide](../../tools/osbuilder/rootfs-builder/README.md).
+
+### Build Kata Image
+Follow the [Image installation guide](../../tools/osbuilder/image-builder/README.md).
+
+### Install Containerd
+
+Follow the [Containerd installation guide](container-manager/containerd/containerd-install.md).
+
+

src/agent/Cargo.toml

@@ -1,3 +1,102 @@
+[workspace]
+members = ["rustjail", "policy", "vsock-exporter"]
+
+[workspace.package]
+authors = ["The Kata Containers community <kata-dev@lists.katacontainers.io>"]
+edition = "2018"
+license = "Apache-2.0"
+rust-version = "1.88.0"
+
+[workspace.dependencies]
+oci-spec = { version = "0.8.1", features = ["runtime"] }
+lazy_static = "1.3.0"
+ttrpc = { version = "0.8.4", features = ["async"], default-features = false }
+protobuf = "3.7.2"
+libc = "0.2.94"
+
+# Notes:
+# - Needs to stay in sync with libs
+# - Upgrading to 0.27+ will require code changes (see #11842)
+nix = "0.26.4"
+
+capctl = "0.2.0"
+scan_fmt = "0.2.6"
+scopeguard = "1.0.0"
+thiserror = "1.0.26"
+regex = "1.10.5"
+serial_test = "0.10.0"
+url = "2.5.0"
+derivative = "2.2.0"
+const_format = "0.2.30"
+
+# Async helpers
+async-trait = "0.1.50"
+async-recursion = "0.3.2"
+futures = "0.3.30"
+
+# Async runtime
+tokio = { version = "1.46.1", features = ["full"] }
+tokio-vsock = "0.3.4"
+
+netlink-sys = { version = "0.7.0", features = ["tokio_socket"] }
+rtnetlink = "0.14.0"
+netlink-packet-route = "0.19.0"
+netlink-packet-core = "0.7.0"
+ipnetwork = "0.17.0"
+
+
+slog = "2.5.2"
+slog-scope = "4.1.2"
+slog-term = "2.9.0"
+
+# Redirect ttrpc log calls
+slog-stdlog = "4.0.0"
+log = "0.4.11"
+
+cfg-if = "1.0.0"
+prometheus = { version = "0.14.0", features = ["process"] }
+procfs = "0.12.0"
+
+anyhow = "1"
+
+cgroups = { package = "cgroups-rs", git = "https://github.com/kata-containers/cgroups-rs", rev = "v0.3.5" }
+
+# Tracing
+tracing = "0.1.41"
+tracing-subscriber = "0.3.20"
+tracing-opentelemetry = "0.17.0"
+opentelemetry = { version = "0.17.0", features = ["rt-tokio"] }
+
+# Configuration
+serde = { version = "1.0.129", features = ["derive"] }
+serde_json = "1.0.39"
+toml = "0.5.8"
+clap = { version = "4.5.40", features = ["derive"] }
+strum = "0.26.2"
+strum_macros = "0.26.2"
+
+tempfile = "3.19.1"
+which = "4.3.0"
+rstest = "0.18.0"
+
+# Local dependencies
+kata-agent-policy = { path = "policy" }
+rustjail = { path = "rustjail" }
+vsock-exporter = { path = "vsock-exporter" }
+
+mem-agent = { path = "../libs/mem-agent" }
+
+kata-sys-util = { path = "../libs/kata-sys-util" }
+kata-types = { path = "../libs/kata-types", features = ["safe-path"] }
+# Note: this crate sets the slog 'max_*' features which allows the log level
+# to be modified at runtime.
+logging = { path = "../libs/logging" }
+protocols = { path = "../libs/protocols" }
+runtime-spec = { path = "../libs/runtime-spec" }
+safe-path = { path = "../libs/safe-path" }
+test-utils = { path = "../libs/test-utils" }
+
+
 [package]
 name = "kata-agent"
 version = "0.1.0"
@@ -57,8 +156,7 @@ cgroups.workspace = true
 # Tracing
 tracing.workspace = true
 tracing-subscriber.workspace = true
-# TODO: bump tracing-opentelemetry to sync with version in workspace
-tracing-opentelemetry = "0.17.0"
+tracing-opentelemetry.workspace = true
 opentelemetry.workspace = true
 
 # Configuration
@@ -107,3 +205,7 @@ seccomp = ["rustjail/seccomp"]
 standard-oci-runtime = ["rustjail/standard-oci-runtime"]
 agent-policy = ["kata-agent-policy"]
 init-data = []
+
+[[bin]]
+name = "kata-agent"
+path = "src/main.rs"

src/agent/Makefile

@@ -63,7 +63,7 @@ ifneq ($(EXTRA_RUSTFEATURES),)
     override EXTRA_RUSTFEATURES := --features "$(EXTRA_RUSTFEATURES)"
 endif
 
-TARGET_PATH = ../../target/$(TRIPLE)/$(BUILD_TYPE)/$(TARGET)
+TARGET_PATH = target/$(TRIPLE)/$(BUILD_TYPE)/$(TARGET)
 
 ##VAR DESTDIR=<path> is a directory prepended to each installed target file
 DESTDIR ?=
@@ -153,7 +153,7 @@ vendor:
 
 #TARGET test: run cargo tests
 test: $(GENERATED_FILES)
-	@RUST_LIB_BACKTRACE=0 RUST_BACKTRACE=1 cargo test -p kata-agent --target $(TRIPLE) $(EXTRA_RUSTFEATURES) -- --nocapture
+	@RUST_LIB_BACKTRACE=0 RUST_BACKTRACE=1 cargo test --all --target $(TRIPLE) $(EXTRA_RUSTFEATURES) -- --nocapture
 
 ##TARGET check: run test
 check: $(GENERATED_FILES) standard_rust_check

src/libs/README.md

@@ -1,114 +1,13 @@
-# Kata Containers Library Crates
+The `src/libs` directory hosts library crates which may be shared by multiple Kata Containers components
+or published to [`crates.io`](https://crates.io/index.html).
 
-The `src/libs` directory hosts library crates shared by multiple Kata Containers components. These libraries provide common utilities, data types, and protocol definitions to facilitate development and maintain consistency across the project.
-
-## Library Crates
+### Library Crates
+Currently it provides following library crates:
 
 | Library | Description |
-|---------|-------------|
-| [kata-types](kata-types/) | Constants, data types, and configuration structures shared by Kata Containers components |
-| [kata-sys-util](kata-sys-util/) | System utilities: CPU, device, filesystem, hooks, K8s, mount, netns, NUMA, PCI, protection, spec validation |
-| [protocols](protocols/) | ttrpc protocol definitions for agent, health, remote, CSI, OCI, confidential data hub |
-| [runtime-spec](runtime-spec/) | OCI runtime spec data structures and constants |
-| [shim-interface](shim-interface/) | Shim management interface with RESTful API over Unix domain socket |
-| [logging](logging/) | Slog-based logging with JSON output and systemd journal support |
-| [safe-path](safe-path/) | Safe path resolution to prevent symlink and TOCTOU attacks |
-| [mem-agent](mem-agent/) | Memory management agent: memcg, compact, PSI monitoring |
-| [test-utils](test-utils/) | Test macros for root/non-root privileges and KVM accessibility |
-
-## Details
-
-### kata-types
-
-Core types and configurations including:
-
-- Annotations for CRI-containerd, CRI-O, dockershim
-- Hypervisor configurations (QEMU, Cloud Hypervisor, Firecracker, Dragonball)
-- Agent and runtime configurations
-- Kubernetes-specific utilities
-
-### kata-sys-util
-
-System-level utilities:
-
-- `cpu`: CPU information and affinity
-- `device`: Device management
-- `fs`: Filesystem operations
-- `hooks`: Hook execution
-- `k8s`: Kubernetes utilities
-- `mount`: Mount operations
-- `netns`: Network namespace handling
-- `numa`: NUMA topology
-- `pcilibs`: PCI device access
-- `protection`: Hardware protection features
-- `spec`: OCI spec loading
-- `validate`: Input validation
-
-### protocols
-
-Generated ttrpc protocol bindings:
-
-- `agent`: Kata agent API
-- `health`: Health check service
-- `remote`: Remote hypervisor API
-- `csi`: Container storage interface
-- `oci`: OCI specifications
-- `confidential_data_hub`: Confidential computing support
-
-Features: `async` for async ttrpc, `with-serde` for serde support.
-
-### runtime-spec
-
-OCI runtime specification types:
-
-- `ContainerState`: Creating, Created, Running, Stopped, Paused
-- `State`: Container state with version, id, status, pid, bundle, annotations
-- Namespace constants: pid, network, mount, ipc, user, uts, cgroup
-
-### shim-interface
-
-Shim management service interface:
-
-- RESTful API over Unix domain socket (`/run/kata/<sid>/shim-monitor.sock`)
-- `MgmtClient` for HTTP requests to shim management server
-- Sandbox ID resolution with prefix matching
-
-### logging
-
-Slog-based logging framework:
-
-- JSON output to file or stdout
-- systemd journal support
-- Runtime log level filtering per component/subsystem
-- Async drain for thread safety
-
-### safe-path
-
-Secure filesystem path handling:
-
-- `scoped_join()`: Safely join paths under a root directory
-- `scoped_resolve()`: Resolve paths constrained by root
-- `PinnedPathBuf`: TOCTOU-safe path reference
-- `ScopedDirBuilder`: Safe directory creation
-
-### mem-agent
-
-Memory management for containers:
-
-- `memcg`: Memory cgroup configuration and monitoring
-- `compact`: Memory compaction control
-- `psi`: Pressure stall information monitoring
-- Async runtime with configurable policies
-
-### test-utils
-
-Testing utilities:
-
-- `skip_if_root!`: Skip test if running as root
-- `skip_if_not_root!`: Skip test if not running as root
-- `skip_if_kvm_unaccessable!`: Skip test if KVM is unavailable
-- `assert_result!`: Assert expected vs actual results
-
-## License
-
-All crates are licensed under Apache-2.0.
+|-|-|
+| [logging](logging/) | Facilities to setup logging subsystem based on slog. |
+| [system utilities](kata-sys-util/) | Collection of facilities and helpers to access system services. |
+| [types](kata-types/) | Collection of constants and data types shared by multiple Kata Containers components. |
+| [safe-path](safe-path/) | Utilities to safely resolve filesystem paths. |
+| [test utilities](test-utils/) | Utilities to share test code. |

src/libs/kata-sys-util/README.md

@@ -1,100 +1,16 @@
 # `kata-sys-util`
 
-System utilities and helpers for [Kata Containers](https://github.com/kata-containers/kata-containers/) components to access Linux system services.
+This crate is a collection of utilities and helpers for
+[Kata Containers](https://github.com/kata-containers/kata-containers/) components to access system services.
 
-## Overview
+It provides safe wrappers over system services, such as:
+- file systems
+- mount
+- NUMA
 
-This crate provides safe wrappers and utility functions for interacting with various Linux system services and kernel interfaces. It is designed specifically for the Kata Containers ecosystem.
-
-## Features
-
-### File System Operations (`fs`)
-
-- Path canonicalization and basename extraction
-- Filesystem type detection (FUSE, OverlayFS)
-- Symlink detection
-- Reflink copy with fallback to regular copy
-
-### Mount Operations (`mount`)
-
-- Bind mount and remount operations
-- Mount propagation type management (SHARED, PRIVATE, SLAVE, UNBINDABLE)
-- Overlay filesystem mount option compression
-- Safe mount destination creation
-- Umount with timeout support
-- `/proc/mounts` parsing utilities
-
-### CPU Utilities (`cpu`)
-
-- CPU information parsing from `/proc/cpuinfo`
-- CPU flags detection and validation
-- Architecture-specific support (x86_64, s390x)
-
-### NUMA Support (`numa`)
-
-- CPU to NUMA node mapping
-- NUMA node information retrieval from sysfs
-- NUMA CPU validation
-
-### Device Management (`device`)
-
-- Block device major/minor number detection
-- Device ID resolution for cgroup operations
-
-### Kubernetes Support (`k8s`)
-
-- Ephemeral volume detection
-- EmptyDir volume handling
-- Kubernetes-specific mount type identification
-
-### Network Namespace (`netns`)
-
-- Network namespace switching with RAII guard pattern
-- Network namespace name generation
-
-### OCI Specification Utilities (`spec`)
-
-- Container type detection (PodSandbox, PodContainer)
-- Sandbox ID extraction from OCI annotations
-- OCI spec loading utilities
-
-### Validation (`validate`)
-
-- Container/exec ID validation
-- Environment variable validation
-
-### Hooks (`hooks`)
-
-- OCI hook execution and management
-- Hook state tracking
-- Timeout handling for hook execution
-
-### Guest Protection (`protection`)
-
-- Confidential computing detection (TDX, SEV, SNP, PEF, SE, ARM CCA , etc.)
-- Architecture-specific protection checking (x86_64, s390x, aarch64, powerpc64)
-
-### Random Generation (`rand`)
-
-- Secure random byte generation
-- UUID generation
-
-### PCI Device Management (`pcilibs`)
-
-- PCI device enumeration and management
-- PCI configuration space access
-- Memory resource allocation for PCI devices
-
-## Supported Architectures
-
-- x86_64
-- aarch64
-- s390x
-- powerpc64 (little-endian)
-- riscv64
-
-## Supported Operating Systems
+## Support
 
+**Operating Systems**:
 - Linux
 
 ## License

src/libs/kata-sys-util/src/mount.rs

@@ -177,7 +177,7 @@ pub fn get_linux_mount_info(mount_point: &str) -> Result<LinuxMountInfo> {
 ///
 /// To ensure security, the `create_mount_destination()` function takes an extra parameter `root`,
 /// which is used to ensure that `dst` is within the specified directory. And a safe version of
-/// `PathBuf` is returned to avoid TOCTOU type of flaws.
+/// `PathBuf` is returned to avoid TOCTTOU type of flaws.
 pub fn create_mount_destination<S: AsRef<Path>, D: AsRef<Path>, R: AsRef<Path>>(
     src: S,
     dst: D,

src/libs/kata-types/Cargo.toml

@@ -41,7 +41,6 @@ sysctl = "0.7.1"
 tempfile = "3.19.1"
 test-utils = { path = "../test-utils" }
 nix = "0.26.4"
-rstest = "0.18"
 
 [features]
 default = []

src/libs/kata-types/README.md

@@ -1,53 +1,18 @@
 # kata-types
 
-Constants and data types shared by Kata Containers components.
+This crate is a collection of constants and data types shared by multiple
+[Kata Containers](https://github.com/kata-containers/kata-containers/) components.
 
-## Overview
-
-This crate provides common constants, data types, and configuration structures used across multiple [Kata Containers](https://github.com/kata-containers/kata-containers/) components. It includes definitions from:
-
-- Kata Containers project
+It defines constants and data types used by multiple Kata Containers components. Those constants
+and data types may be defined by Kata Containers or by other projects/specifications, such as:
 - [Containerd](https://github.com/containerd/containerd)
-- [Kubelet](https://github.com/kubernetes/kubernetes)
+- [Kubelet](https://github.com/kubernetes/kubelet)
 
-## Modules
+## Support
 
-| Module | Description |
-|--------|-------------|
-| `annotations` | Annotation keys for CRI-containerd, CRI-O, dockershim, and third-party integrations |
-| `capabilities` | Hypervisor capability flags (block device, multi-queue, filesystem sharing, etc.) |
-| `config` | Configuration structures for agent, hypervisor (QEMU, Cloud Hypervisor, Firecracker, Dragonball), and runtime |
-| `container` | Container-related constants and types |
-| `cpu` | CPU resource management types |
-| `device` | Device-related definitions |
-| `fs` | Filesystem constants |
-| `handler` | Handler-related types |
-| `initdata` | Initdata specification for TEE data injection |
-| `k8s` | Kubernetes-specific paths and utilities (empty-dir, configmap, secret, projected volumes) |
-| `machine_type` | Machine type definitions |
-| `mount` | Mount point structures and validation |
-| `rootless` | Rootless VMM support utilities |
-
-## Configuration
-
-The `config` module supports:
-
-- TOML-based configuration loading
-- Drop-in configuration files
-- Hypervisor-specific configurations (QEMU, Cloud Hypervisor, Firecracker, Dragonball, Remote)
-- Agent configuration
-- Runtime configuration
-- Shared mount definitions
-
-## Features
-
-- `enable-vendor`: Enable vendor-specific extensions
-- `safe-path`: Enable safe path resolution (platform-specific)
-
-## Platform Support
-
-- **Linux**: Fully supported
+**Operating Systems**:
+- Linux
 
 ## License
 
-Apache-2.0 - See [LICENSE](../../../LICENSE)
+This code is licensed under [Apache-2.0](../../../LICENSE).

src/libs/kata-types/src/config/hypervisor/mod.rs

@@ -1077,81 +1077,6 @@ impl MemoryInfo {
         if self.default_maxmemory == 0 || u64::from(self.default_maxmemory) > host_memory {
             self.default_maxmemory = host_memory as u32;
         }
-
-        // Apply PowerPC64 memory alignment
-        #[cfg(all(target_arch = "powerpc64", target_endian = "little"))]
-        self.adjust_ppc64_memory_alignment()?;
-
-        Ok(())
-    }
-
-    /// Adjusts memory values for PowerPC64 little-endian systems to meet
-    /// QEMU's 256MB block size alignment requirement.
-    ///
-    /// Ensures default_memory is at least 1024MB and both default_memory
-    /// and default_maxmemory are aligned to 256MB boundaries.
-    /// Returns an error if aligned values would be equal.
-    #[cfg(all(target_arch = "powerpc64", target_endian = "little"))]
-    fn adjust_ppc64_memory_alignment(&mut self) -> Result<()> {
-        const PPC64_MEM_BLOCK_SIZE: u64 = 256;
-        const MIN_MEMORY_MB: u64 = 1024;
-
-        fn align_memory(value: u64) -> u64 {
-            (value / PPC64_MEM_BLOCK_SIZE) * PPC64_MEM_BLOCK_SIZE
-        }
-
-        let mut mem_size = u64::from(self.default_memory);
-        let max_mem_size = u64::from(self.default_maxmemory);
-
-        // Ensure minimum memory size
-        if mem_size < MIN_MEMORY_MB {
-            info!(
-                sl!(),
-                "PowerPC: Increasing default_memory from {}MB to minimum {}MB",
-                mem_size,
-                MIN_MEMORY_MB
-            );
-            mem_size = MIN_MEMORY_MB;
-        }
-
-        // Align both values to 256MB boundaries
-        let aligned_mem = align_memory(mem_size);
-        let aligned_max_mem = align_memory(max_mem_size);
-
-        if aligned_mem != mem_size {
-            info!(
-                sl!(),
-                "PowerPC: Aligned default_memory from {}MB to {}MB", mem_size, aligned_mem
-            );
-        }
-
-        if aligned_max_mem != max_mem_size {
-            info!(
-                sl!(),
-                "PowerPC: Aligned default_maxmemory from {}MB to {}MB",
-                max_mem_size,
-                aligned_max_mem
-            );
-        }
-
-        // Check if aligned values are equal
-        if aligned_max_mem != 0 && aligned_max_mem <= aligned_mem {
-            return Err(std::io::Error::other(format!(
-                "PowerPC: default_maxmemory ({}MB) <= default_memory ({}MB) after alignment. \
-                Requires maxmemory > memory. Please increase default_maxmemory.",
-                aligned_max_mem, aligned_mem
-            )));
-        }
-        info!(
-            sl!(),
-            "PowerPC: Memory alignment applied - memory: {}MB, max_memory: {}MB",
-            aligned_mem,
-            aligned_max_mem
-        );
-
-        self.default_memory = aligned_mem as u32;
-        self.default_maxmemory = aligned_max_mem as u32;
-
         Ok(())
     }
 
@@ -2023,72 +1948,4 @@ mod tests {
             );
         }
     }
-
-    #[cfg(all(target_arch = "powerpc64", target_endian = "little"))]
-    use rstest::rstest;
-
-    #[rstest]
-    #[case::memory_below_minimum(512, 2048, 1024, 2048)]
-    #[case::already_aligned(1024, 2048, 1024, 2048)]
-    #[case::unaligned_rounds_down(1100, 2100, 1024, 2048)]
-    #[cfg(all(target_arch = "powerpc64", target_endian = "little"))]
-    fn test_adjust_ppc64_memory_alignment_success(
-        #[case] input_memory: u32,
-        #[case] input_maxmemory: u32,
-        #[case] expected_memory: u32,
-        #[case] expected_maxmemory: u32,
-    ) {
-        let mut mem = MemoryInfo {
-            default_memory: input_memory,
-            default_maxmemory: input_maxmemory,
-            ..Default::default()
-        };
-
-        let result = mem.adjust_ppc64_memory_alignment();
-        assert!(
-            result.is_ok(),
-            "Expected success but got error: {:?}",
-            result.err()
-        );
-        assert_eq!(
-            mem.default_memory, expected_memory,
-            "Memory not aligned correctly"
-        );
-        assert_eq!(
-            mem.default_maxmemory, expected_maxmemory,
-            "Max memory not aligned correctly"
-        );
-    }
-
-    #[rstest]
-    #[case::equal_after_alignment(1024, 1100, "Requires maxmemory > memory")]
-    #[case::maxmemory_less_than_memory(2048, 1500, "Requires maxmemory > memory")]
-    #[cfg(all(target_arch = "powerpc64", target_endian = "little"))]
-    fn test_adjust_ppc64_memory_alignment_errors(
-        #[case] input_memory: u32,
-        #[case] input_maxmemory: u32,
-        #[case] expected_error_msg: &str,
-    ) {
-        let mut mem = MemoryInfo {
-            default_memory: input_memory,
-            default_maxmemory: input_maxmemory,
-            ..Default::default()
-        };
-
-        let result = mem.adjust_ppc64_memory_alignment();
-        assert!(
-            result.is_err(),
-            "Expected error but got success for memory={}, maxmemory={}",
-            input_memory,
-            input_maxmemory
-        );
-
-        let error_msg = result.unwrap_err().to_string();
-        assert!(
-            error_msg.contains(expected_error_msg),
-            "Error message '{}' does not contain expected text '{}'",
-            error_msg,
-            expected_error_msg
-        );
-    }
 }

src/libs/safe-path/src/lib.rs

@@ -26,7 +26,7 @@
 //! information and ensure data out of the container rootfs directory won't be affected
 //! by the container. There are several types of attacks related to container mount namespace:
 //! - symlink based attack
-//! - Time of check to time of use (TOCTOU)
+//! - Time of check to time of use (TOCTTOU)
 //!
 //! This crate provides several mechanisms for container runtimes to safely handle filesystem paths
 //! when preparing mount namespace for containers.
@@ -35,13 +35,13 @@
 //! - [scoped_resolve()](crate::scoped_resolve()): resolve `unsafe_path` to a relative path,
 //!   rooted at and constrained by `root`.
 //! - [struct PinnedPathBuf](crate::PinnedPathBuf): safe version of `PathBuf` to protect from
-//!   TOCTOU style of attacks, which ensures:
+//!   TOCTTOU style of attacks, which ensures:
 //!     - the value of [`PinnedPathBuf::as_path()`] never changes.
 //!     - the path returned by [`PinnedPathBuf::as_path()`] is always a symlink.
 //!     - the filesystem object referenced by the symlink [`PinnedPathBuf::as_path()`] never changes.
 //!     - the value of [`PinnedPathBuf::target()`] never changes.
 //! - [struct ScopedDirBuilder](crate::ScopedDirBuilder): safe version of `DirBuilder` to protect
-//!   from symlink race and TOCTOU style of attacks, which enhances security by:
+//!   from symlink race and TOCTTOU style of attacks, which enhances security by:
 //!     - ensuring the new directories are created under a specified `root` directory.
 //!     - avoiding symlink race attacks during making directories.
 //!     - returning a [PinnedPathBuf] for the last level of directory, so it could be used for other

src/libs/safe-path/src/pinned_path_buf.rs

@@ -15,7 +15,7 @@ use std::path::{Component, Path, PathBuf};
 use crate::scoped_join;
 
 /// A safe version of [`PathBuf`] pinned to an underlying filesystem object to protect from
-/// `TOCTOU` style of attacks.
+/// `TOCTTOU` style of attacks.
 ///
 /// A [`PinnedPathBuf`] is a resolved path buffer pinned to an underlying filesystem object, which
 /// guarantees:

src/libs/safe-path/src/scoped_path_resolver.rs

@@ -117,7 +117,7 @@ pub fn scoped_resolve<R: AsRef<Path>, U: AsRef<Path>>(root: R, unsafe_path: U) -
 /// Note that the guarantees provided by this function only apply if the path components in the
 /// returned string are not modified (in other words are not replaced with symlinks on the
 /// filesystem) after this function has returned. You may use [crate::PinnedPathBuf] to protect
-/// from such TOCTOU attacks.
+/// from such TOCTTOU attacks.
 pub fn scoped_join<R: AsRef<Path>, U: AsRef<Path>>(root: R, unsafe_path: U) -> Result<PathBuf> {
     do_scoped_resolve(root, unsafe_path).map(|(root, path)| root.join(path))
 }

src/runtime-rs/Makefile

@@ -33,11 +33,15 @@ test:
 	exit 0
 install: install-runtime install-configs
 else ifeq ($(ARCH), powerpc64le)
-default: runtime show-header
-test:
-	@echo "powerpc64le is not currently supported"
+default:
+	@echo "PowerPC 64 LE is not currently supported"
+	exit 0
+test:
+	@echo "PowerPC 64 LE is not currently supported"
+	exit 0
+install:
+	@echo "PowerPC 64 LE is not currently supported"
 	exit 0
-install: install-runtime install-configs
 else ifeq ($(ARCH), riscv64gc)
 default: runtime show-header
 test:
@@ -95,11 +99,11 @@ HYPERVISOR_REMOTE = remote
 ARCH_SUPPORT_DB := x86_64 aarch64
 ifneq ($(filter $(ARCH),$(ARCH_SUPPORT_DB)),)
     # When set to true, builds the built-in Dragonball hypervisor
-    USE_BUILTIN_DB := true
+    USE_BUILDIN_DB := true
 else
-    USE_BUILTIN_DB := false
+    USE_BUILDIN_DB := false
     $(info Dragonball does not support ARCH $(ARCH), disabled. \
-        Specify "USE_BUILTIN_DB=true" to force enable.)
+        Specify "USE_BUILDIN_DB=true" to force enable.)
 endif
 
 HYPERVISOR ?= $(HYPERVISOR_DB)
@@ -479,7 +483,7 @@ USER_VARS += CONFIG_REMOTE_IN
 USER_VARS += CONFIG_QEMU_COCO_DEV_IN
 USER_VARS += DESTDIR
 USER_VARS += HYPERVISOR
-USER_VARS += USE_BUILTIN_DB
+USER_VARS += USE_BUILDIN_DB
 USER_VARS += DBCMD
 USER_VARS += DBCTLCMD
 USER_VARS += FCCTLCMD
@@ -647,7 +651,7 @@ COMMIT_MSG = $(if $(COMMIT),$(COMMIT),unknown)
 EXTRA_RUSTFEATURES :=
 
 # if use dragonball hypervisor, add the feature to build dragonball in runtime
-ifeq ($(USE_BUILTIN_DB),true)
+ifeq ($(USE_BUILDIN_DB),true)
     EXTRA_RUSTFEATURES +=  dragonball
 endif
 

src/runtime-rs/README.md

@@ -1,179 +1,131 @@
 # runtime-rs
 
-## What is runtime-rs
+## Wath's runtime-rs
 
-`runtime-rs` is a core component of Kata Containers 4.0. It is a high-performance, Rust-based implementation of the containerd shim v2 runtime.
+`runtime-rs` is a new component introduced in Kata Containers 3.0, it is a Rust version of runtime(shim). It like [runtime](../runtime), but they have many difference:
 
-Key characteristics:
+- `runtime-rs` is written in Rust, and `runtime` is written in Go.
+- `runtime` is the default shim in Kata Containers 3.0, `runtime-rs` is still under heavy development.
+- `runtime-rs` has a completed different architecture than `runtime`, you can check at the [architecture overview](../../docs/design/architecture_3.0).
 
-- **Implementation Language**: Rust, leveraging memory safety and zero-cost abstractions
-- **Project Maturity**: Production-ready component of Kata Containers 4.0
-- **Architectural Design**: Modular framework optimized for Kata Containers 4.0
+**Note**:
 
-For architecture details, see [Architecture Overview](../../docs/design/architecture_4.0).
+`runtime-rs` is still under heavy development, you should avoid using it in critical system.
 
-## Architecture Overview
+## Architecture overview
 
-Key features:
+Also, `runtime-rs` provides the following features:
 
-- **Built-in VMM (Dragonball)**: Deeply integrated into shim lifecycle, eliminating IPC overhead for peak performance
-- **Asynchronous I/O**: Tokio-based async runtime for high-concurrency with reduced thread footprint
-- **Extensible Framework**: Pluggable hypervisors, network interfaces, and storage backends
-- **Resource Lifecycle Management**: Comprehensive sandbox and container resource management
+- Turn key solution with builtin `Dragonball` Sandbox, all components in one process
+- Async I/O to reduce resource consumption
+- Extensible framework for multiple services, runtimes and hypervisors
+- Lifecycle management for sandbox and container associated resources
+
+See the [architecture overview](../../docs/design/architecture_3.0)
+for details on the `runtime-rs` design.
+
+`runtime-rs` is a runtime written in Rust, it is composed of several crates.
+
+This picture shows the overview about the crates under this directory and the relation between crates.
 
 ![crates overview](docs/images/crate-overview.svg)
 
+Not all the features have been implemented yet, for details please check the [roadmap](../../docs/design/architecture_3.0/README.md#roadmap).
+
 ## Crates
 
+The `runtime-rs` directory contains some crates in the crates directory that compose the `containerd-shim-kata-v2`.
+
 | Crate | Description |
-|-------|-------------|
-| [`shim`](crates/shim) | Containerd shim v2 entry point (start, delete, run commands) |
-| [`service`](crates/service) | Services including TaskService for containerd shim protocol |
-| [`runtimes`](crates/runtimes) | Runtime handlers: VirtContainer (default), LinuxContainer(experimental), WasmContainer(experimental) |
-| [`resource`](crates/resource) | Resource management: network, share_fs, rootfs, volume, cgroups, cpu_mem |
-| [`hypervisor`](crates/hypervisor) | Hypervisor implementations |
-| [`agent`](crates/agent) | Guest agent communication (KataAgent) |
-| [`persist`](crates/persist) | State persistence to disk (JSON format) |
-| [`shim-ctl`](crates/shim-ctl) | Development tool for testing shim without containerd |
+|-|-|
+| [`shim`](crates/shim)| containerd shimv2 implementation |
+| [`service`](crates/service)| services for containers, includes task service |
+| [`runtimes`](crates/runtimes)| container runtimes |
+| [`resource`](crates/resource)| sandbox and container resources |
+| [`hypervisor`](crates/hypervisor)| hypervisor that act as a sandbox |
+| [`agent`](crates/agent)| library used to communicate with agent in the guest OS |
+| [`persist`](crates/persist)| persist container state to disk |
 
 ### shim
 
-Entry point implementing [containerd shim v2 binary protocol](https://github.com/containerd/containerd/tree/main/runtime/v2#commands):
+`shim` is the entry point of the containerd shim process, it implements containerd shim's [binary protocol](https://github.com/containerd/containerd/tree/v1.6.8/runtime/v2#commands):
 
-- `start`: Start new shim process
-- `delete`: Delete existing shim process
-- `run`: Run ttRPC service
+- start: start a new shim process
+- delete: delete exist a shim process
+- run: run ttRPC service in shim
+
+containerd will launch a shim process and the shim process will serve as a ttRPC server to provide shim service through `TaskService` from `service` crate.
 
 ### service
 
-Extensible service framework. Currently implements `TaskService` conforming to [containerd shim protocol](https://docs.rs/containerd-shim-protos/).
+The `runtime-rs` has an extensible framework, includes extension of services, runtimes, and hypervisors.
+
+Currently, only containerd compatible `TaskService` is implemented.
+
+`TaskService` has implemented the [containerd shim protocol](https://docs.rs/containerd-shim-protos/0.2.0/containerd_shim_protos/),
+and interacts with runtimes through messages.
 
 ### runtimes
 
-Runtime handlers manage sandbox and container operations:
+Runtime is a container runtime, the runtime handler handles messages from task services to manage containers.
+Runtime handler and Runtime instance is used to deal with the operation for sandbox and container.
 
-| Handler | Feature Flag | Description |
-|---------|--------------|-------------|
-| `VirtContainer` | `virt` (default) | Virtual machine-based containers |
-| `LinuxContainer` | `linux` | Linux container runtime (experimental) |
-| `WasmContainer` | `wasm` | WebAssembly runtime (experimental) |
+Currently, only `VirtContainer` has been implemented.
 
 ### resource
 
-All resources abstracted uniformly:
+In `runtime-rs`, all networks/volumes/rootfs are abstracted as resources.
 
-- **Sandbox resources**: network, share-fs
-- **Container resources**: rootfs, volume, cgroup
+Resources are classified into two types:
 
-Sub-modules: `cpu_mem`, `cdi_devices`, `coco_data`, `network`, `share_fs`, `rootfs`, `volume`
+- sandbox resources: network, share-fs
+- container resources: rootfs, volume, cgroup
+
+[Here](../../docs/design/architecture_3.0/README.md#resource-manager) is a detailed description of the resources.
 
 ### hypervisor
 
-Supported hypervisors:
+For `VirtContainer`, there will be more hypervisors to choose.
 
-| Hypervisor | Mode | Description |
-|------------|------|-------------|
-| Dragonball | Built-in | Integrated VMM for peak performance (default) |
-| QEMU | External | Full-featured emulator |
-| Cloud Hypervisor | External | Modern VMM (x86_64, aarch64) |
-| Firecracker | External | Lightweight microVM |
-| Remote | External | Remote hypervisor |
-
-The built-in VMM mode (Dragonball) is recommended for production, offering superior performance by eliminating IPC overhead.
+Currently, built-in `Dragonball` has been implemented. We have also added initial support for `cloud-hypervisor` with CI being added next.
 
 ### agent
 
-Communication with guest OS agent via ttRPC. Supports `KataAgent` for full container lifecycle management.
+`agent` is used to communicate with agent in the guest OS from the shim side. The only supported agent is `KataAgent`.
 
 ### persist
 
-State serialization to disk for sandbox recovery after restart. Stores `state.json` under `/run/kata/<sandbox-id>/`.
+Persist defines traits and functions to help different components save state to disk and load state from disk.
 
-## Build from Source and Install
+### helper libraries
 
-### Prerequisites
+Some helper libraries are maintained in [the library directory](../libs) so that they can be shared with other rust components.
 
-Download `Rustup` and install Rust. For Rust version, see `languages.rust.meta.newest-version` in [`versions.yaml`](../../versions.yaml).
+## Build and install
 
-Example for `x86_64`:
-
-```bash
-curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
-source $HOME/.cargo/env
-rustup install ${RUST_VERSION}
-rustup default ${RUST_VERSION}-x86_64-unknown-linux-gnu
-```
-
-### Musl Support (Optional)
-
-For fully static binary:
-
-```bash
-# Add musl target
-rustup target add x86_64-unknown-linux-musl
-
-# Install musl libc (example: musl 1.2.3)
-curl -O https://git.musl-libc.org/cgit/musl/snapshot/musl-1.2.3.tar.gz
-tar vxf musl-1.2.3.tar.gz
-cd musl-1.2.3/
-./configure --prefix=/usr/local/
-make && sudo make install
-```
-
-### Install Kata 4.0 Rust Runtime Shim
-
-```bash
-git clone https://github.com/kata-containers/kata-containers.git
-cd kata-containers/src/runtime-rs
-make && sudo make install
-```
-
-After installation:
-- Config file: `/usr/share/defaults/kata-containers/configuration.toml`
-- Binary: `/usr/local/bin/containerd-shim-kata-v2`
-
-### Install Without Built-in Dragonball VMM
-
-To build without the built-in Dragonball hypervisor:
-
-```bash
-make USE_BUILTIN_DB=false
-```
-
-Specify hypervisor during installation:
-
-```bash
-sudo make install HYPERVISOR=qemu
-# or
-sudo make install HYPERVISOR=cloud-hypervisor
-```
+See the
+[build from the source section of the rust runtime installation guide](../../docs/install/kata-containers-3.0-rust-runtime-installation-guide.md#build-from-source-installation).
 
 ## Configuration
 
-Configuration files in `config/`:
-
-| Config File | Hypervisor | Notes |
-|-------------|------------|-------|
-| `configuration-dragonball.toml.in` | Dragonball | Built-in VMM |
-| `configuration-qemu-runtime-rs.toml.in` | QEMU | Default external |
-| `configuration-cloud-hypervisor.toml.in` | Cloud Hypervisor | Modern VMM |
-| `configuration-rs-fc.toml.in` | Firecracker | Lightweight microVM |
-| `configuration-remote.toml.in` | Remote | Remote hypervisor |
-| `configuration-qemu-tdx-runtime-rs.toml.in` | QEMU + TDX | Intel TDX confidential computing |
-| `configuration-qemu-snp-runtime-rs.toml.in` | QEMU + SEV-SNP | AMD SEV-SNP confidential computing |
-| `configuration-qemu-se-runtime-rs.toml.in` | QEMU + SEV | AMD SEV confidential computing |
-| `configuration-qemu-coco-dev-runtime-rs.toml.in` | QEMU + CoCo | CoCo development |
-
-See [runtime configuration](../runtime/README.md#configuration) for configuration options.
+`runtime-rs` has the same [configuration as `runtime`](../runtime/README.md#configuration) with some [limitations](#limitations).
 
 ## Logging
 
-See [Developer Guide - Troubleshooting](../../docs/Developer-Guide.md#troubleshoot-kata-containers).
+See the
+[debugging section of the developer guide](../../docs/Developer-Guide.md#troubleshoot-kata-containers).
 
 ## Debugging
 
-For development, use [`shim-ctl`](crates/shim-ctl/README.md) to test shim without containerd dependencies.
+See the
+[debugging section of the developer guide](../../docs/Developer-Guide.md#troubleshoot-kata-containers).
+
+An [experimental alternative binary](crates/shim-ctl/README.md) is available that removes containerd dependencies and makes it easier to run the shim proper outside of the runtime's usual deployment environment (i.e. on a developer machine).
 
 ## Limitations
 
-See [Limitations](../../docs/Limitations.md) for details.
+For Kata Containers limitations, see the
+[limitations file](../../docs/Limitations.md)
+for further details.
+
+`runtime-rs` is under heavy developments, and doesn't support all features as the Golang version [`runtime`](../runtime), check the [roadmap](../../docs/design/architecture_3.0/README.md#roadmap) for details.

src/runtime-rs/arch/powerpc64le-options.mk

@@ -7,6 +7,9 @@
 MACHINETYPE := pseries
 KERNELPARAMS := cgroup_no_v1=all systemd.unified_cgroup_hierarchy=1
 MACHINEACCELERATORS := "cap-cfpc=broken,cap-sbbc=broken,cap-ibs=broken,cap-large-decr=off,cap-ccf-assist=off"
-CPUFEATURES :=
+CPUFEATURES := pmu=off
 
 QEMUCMD := qemu-system-ppc64
+
+# dragonball binary name
+DBCMD := dragonball

src/runtime-rs/crates/hypervisor/README.md

@@ -1,21 +1,23 @@
-# Multi-VMM Support for runtime-rs
+# Multi-vmm support for runtime-rs
 
 ## 0. Status
 
-Multiple external hypervisors are supported in the Rust runtime, including QEMU, Firecracker, and Cloud Hypervisor. This document outlines the key implementation details for multi-VMM support in the Rust runtime.
+External hypervisor support is currently being developed.
 
-## 1. Hypervisor Configuration
+See [the main tracking issue](https://github.com/kata-containers/kata-containers/issues/4634)
+for further details.
 
-The diagram below provides an overview of the hypervisor configuration:
+Some key points for supporting multi-vmm in rust runtime.
+## 1. Hypervisor Config
+
+The diagram below gives an overview for the hypervisor config
 
 ![hypervisor config](../../docs/images/hypervisor-config.svg)
 
-VMM configuration information is loaded during runtime instance initialization. The following key functions are critical to this process:
-
+VMM's config info will be loaded when initialize the runtime instance, there are some important functions need to be focused on.
 ### `VirtContainer::init()`
 
-This function initializes the runtime handler and registers plugins into the `HYPERVISOR_PLUGINS` registry. Different hypervisors require different plugins:
-
+This function initialize the runtime handler. It will register the plugins into the HYPERVISOR_PLUGINS. Different plugins are needed for different hypervisors.
 ```rust
 #[async_trait]
 impl RuntimeHandler for VirtContainer {
@@ -28,24 +30,21 @@ impl RuntimeHandler for VirtContainer {
 }
 ```
 
-Currently, the QEMU plugin is fully implemented, we can take it as an example. The QEMU plugin defines methods to adjust and validate the hypervisor configuration file. These methods can be customized as needed.
-
-Details of the QEMU plugin implementation can be found in [QEMU Plugin Implementation](../../../libs/kata-types/src/config/hypervisor/qemu.rs)
-
-When loading the TOML configuration, the registered plugins are invoked to adjust and validate the configuration file:
+[This is the plugin method for QEMU. Other VMM plugin methods haven't support currently.](../../../libs/kata-types/src/config/hypervisor/qemu.rs)
+QEMU plugin defines the methods to adjust and validate the hypervisor config file, those methods could be modified if it is needed.
 
+After that, when loading the TOML config, the plugins will be called to adjust and validate the config file.
 ```rust
-async fn try_init(&mut self, spec: &oci::Spec) -> Result<()> {
+async fn try_init(&mut self, spec: &oci::Spec) -> Result<()> {、
     ...
     let config = load_config(spec).context("load config")?;
     ...
 }
 ```
 
-### `new_instance`
-
-This function creates a runtime instance that manages container and sandbox operations. During this process, a hypervisor instance is created. For QEMU, the hypervisor instance is instantiated and configured with the appropriate configuration file:
+### new_instance
 
+This function will create a runtime_instance which include the operations for container and sandbox.  At the same time, a hypervisor instance will be created.  QEMU instance will be created here as well, and set the hypervisor config file
 ```rust
 async fn new_hypervisor(toml_config: &TomlConfig) -> Result<Arc<dyn Hypervisor>> {
     let hypervisor_name = &toml_config.runtime.hypervisor_name;
@@ -71,8 +70,7 @@ async fn new_hypervisor(toml_config: &TomlConfig) -> Result<Arc<dyn Hypervisor>>
 
 ## 2. Hypervisor Trait
 
-[The hypervisor trait must be implemented to support multi-VMM architectures.](./src/lib.rs)
-
+[To support multi-vmm, the hypervisor trait need to be implemented.](./src/lib.rs)
 ```rust
 pub trait Hypervisor: Send + Sync {
     // vm manager
@@ -99,7 +97,6 @@ pub trait Hypervisor: Send + Sync {
     async fn save_state(&self) -> Result<HypervisorState>;
    }
 ```
-
-In the current design, the VM startup process follows these steps:
+In current design, VM will be started in the following steps.
 
 ![vmm start](../../docs/images/vm-start.svg)

src/runtime-rs/crates/hypervisor/src/device/tap.rs

@@ -147,7 +147,7 @@ impl Tap {
 
         // ioctl is safe since we call it with a valid tap fd and check the return
         // value.
-        let ret = unsafe { ioctl_with_mut_ref(&tuntap, libc::TUNSETIFF as libc::c_ulong, ifr) };
+        let ret = unsafe { ioctl_with_mut_ref(&tuntap, TUNSETIFF(), ifr) };
         if ret < 0 {
             return Err(Error::CreateTap(IoError::last_os_error()));
         }

src/runtime-rs/crates/hypervisor/src/firecracker/fc_api.rs

@@ -111,7 +111,7 @@ impl FcInner {
 
         let body_config: String = json!({
             "mem_size_mib": self.config.memory_info.default_memory,
-            "vcpu_count": self.config.cpu_info.default_vcpus.ceil() as u8,
+            "vcpu_count": self.config.cpu_info.default_vcpus,
         })
         .to_string();
         let body_kernel: String = json!({
@@ -191,10 +191,13 @@ impl FcInner {
                 .disk_rate_limiter_ops_one_time_burst,
         );
 
+        let rate_limiter = serde_json::to_string(&block_rate_limit)
+            .with_context(|| format!("serde {block_rate_limit:?} to json"))?;
+
         let body: String = json!({
             "drive_id": format!("drive{drive_id}"),
             "path_on_host": new_drive_path,
-            "rate_limiter": block_rate_limit,
+            "rate_limiter": rate_limiter,
         })
         .to_string();
         self.request_with_retry(

src/runtime-rs/crates/hypervisor/src/qemu/inner.rs

@@ -617,10 +617,8 @@ impl QemuInner {
         todo!()
     }
 
-    pub(crate) fn set_capabilities(&mut self, flag: CapabilityBits) {
-        let mut caps = Capabilities::default();
-
-        caps.set(flag)
+    pub(crate) fn set_capabilities(&mut self, _flag: CapabilityBits) {
+        todo!()
     }
 
     pub(crate) fn set_guest_memory_block_size(&mut self, size: u32) {
@@ -858,12 +856,7 @@ impl QemuInner {
                         block_device.config.index,
                         &block_device.config.path_on_host,
                         &block_device.config.blkdev_aio.to_string(),
-                        Some(
-                            block_device
-                                .config
-                                .is_direct
-                                .unwrap_or(self.config.blockdev_info.block_device_cache_direct),
-                        ),
+                        block_device.config.is_direct,
                         block_device.config.is_readonly,
                         block_device.config.no_drop,
                     )

src/runtime-rs/crates/resource/src/manager.rs

@@ -84,16 +84,6 @@ impl ResourceManager {
         inner.handle_network(network_config).await
     }
 
-    pub async fn has_network_endpoints(&self) -> bool {
-        let inner = self.inner.read().await;
-        inner.has_network_endpoints().await
-    }
-
-    pub async fn setup_network_in_guest(&self) -> Result<()> {
-        let inner = self.inner.read().await;
-        inner.setup_network_in_guest().await
-    }
-
     #[instrument]
     pub async fn setup_after_start_vm(&self) -> Result<()> {
         let mut inner = self.inner.write().await;

src/runtime-rs/crates/resource/src/manager_inner.rs

@@ -296,33 +296,6 @@ impl ResourceManagerInner {
         Ok(())
     }
 
-    pub async fn has_network_endpoints(&self) -> bool {
-        if let Some(network) = &self.network {
-            match network.interfaces().await {
-                std::result::Result::Ok(interfaces) => !interfaces.is_empty(),
-                Err(_) => false,
-            }
-        } else {
-            false
-        }
-    }
-
-    pub async fn setup_network_in_guest(&self) -> Result<()> {
-        if let Some(network) = self.network.as_ref() {
-            let network = network.as_ref();
-            self.handle_interfaces(network)
-                .await
-                .context("handle interfaces during network rescan")?;
-            self.handle_neighbours(network)
-                .await
-                .context("handle neighbours during network rescan")?;
-            self.handle_routes(network)
-                .await
-                .context("handle routes during network rescan")?;
-        }
-        Ok(())
-    }
-
     pub async fn setup_after_start_vm(&mut self) -> Result<()> {
         self.cgroups_resource
             .setup_after_start_vm(self.hypervisor.as_ref())

src/runtime-rs/crates/resource/src/share_fs/mod.rs

@@ -165,6 +165,6 @@ pub fn new(id: &str, config: &SharedFsInfo) -> Result<Arc<dyn ShareFs>> {
         VIRTIO_FS => Ok(Arc::new(
             ShareVirtioFsStandalone::new(id, config).context("new standalone virtio fs")?,
         )),
-        _ => Err(anyhow!("unsupported shared fs {:?}", &shared_fs)),
+        _ => Err(anyhow!("unsupported shred fs {:?}", &shared_fs)),
     }
 }

src/runtime-rs/crates/runtimes/Cargo.toml

@@ -53,9 +53,6 @@ linux_container = { workspace = true, optional = true }
 virt_container = { workspace = true, optional = true }
 wasm_container = { workspace = true, optional = true }
 
-[dev-dependencies]
-rstest = { workspace = true }
-
 [features]
 default = ["virt"]
 linux = ["linux_container"]

src/runtime-rs/crates/runtimes/common/src/sandbox.rs

@@ -51,13 +51,6 @@ pub trait Sandbox: Send + Sync {
         shim_pid: u32,
     ) -> Result<()>;
 
-    /// Re-scan the network namespace for late-discovered endpoints.
-    /// This handles runtimes like Docker 26+ that configure networking
-    /// after the Start response. The default implementation is a no-op.
-    async fn rescan_network(&self) -> Result<()> {
-        Ok(())
-    }
-
     // metrics function
     async fn agent_metrics(&self) -> Result<String>;
     async fn hypervisor_metrics(&self) -> Result<String>;