Skip to content

fix: backport broken relative links to v2.9.0 faq #614

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mesutoezdil merged 1 commit into from
Jul 21, 2026
Merged

fix: backport broken relative links to v2.9.0 faq #614

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion i18n/zh/docusaurus-plugin-content-docs/version-v2.9.0/faq/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -199,7 +199,7 @@ HAMi vGPU 是纯软件方案，无硬件要求。NVIDIA MIG 是硬件分区，

## 为什么 nvidia.com/gpumem 限制未生效？ {#why-is-my-nvidiagpumem-limit-not-enforced}

最常见的四种原因：设置了 `CUDA_DISABLE_CONTROL=true`、工作负载运行在 Docker-in-Docker 中、应用直接调用 GPU 驱动（绕过了 `libvgpu.so`）、或节点上 `nvidia-container-runtime` 未设为默认运行时。解决步骤参见[排障手册](./troubleshooting)。
最常见的四种原因：设置了 `CUDA_DISABLE_CONTROL=true`、工作负载运行在 Docker-in-Docker 中、应用直接调用 GPU 驱动（绕过了 `libvgpu.so`）、或节点上 `nvidia-container-runtime` 未设为默认运行时。解决步骤参见[排障手册](../troubleshooting/troubleshooting.md)。

## HAMi 是替换 kube-scheduler 还是与其并行运行？

Expand Down
2 changes: 1 addition & 1 deletion versioned_docs/version-v2.9.0/faq/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -202,7 +202,7 @@ Use HAMi vGPU when the GPU does not support MIG, workloads need flexible memory

## Why is my nvidia.com/gpumem limit not enforced? {#why-is-my-nvidiagpumem-limit-not-enforced}

The four most common causes: `CUDA_DISABLE_CONTROL=true` is set, the workload runs inside Docker-in-Docker, the application calls the GPU driver directly (bypassing `libvgpu.so`), or `nvidia-container-runtime` is not the default runtime on the node. See [Troubleshooting](./troubleshooting) for resolution steps.
The four most common causes: `CUDA_DISABLE_CONTROL=true` is set, the workload runs inside Docker-in-Docker, the application calls the GPU driver directly (bypassing `libvgpu.so`), or `nvidia-container-runtime` is not the default runtime on the node. See [Troubleshooting](../troubleshooting/troubleshooting.md) for resolution steps.

## Does HAMi replace kube-scheduler or run alongside it?

Expand Down