We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
What happened: k3s 节点重启后,GPU虚拟化失效,nvidia.com/gpu 数目变回物理GPU数目,重启pod hami-device-plugin后,nvidia.com/gpu 数目恢复正常
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
nvidia-smi -a
/etc/docker/daemon.json
sudo journalctl -r -u kubelet
dmesg
Environment:
docker version
uname -a
The text was updated successfully, but these errors were encountered:
你应该是之前没卸载掉nvidiade device-plugin吧
Sorry, something went wrong.
先安装的nvidia GPU Opeartor,再安装的Hami,安装完hami之后需要把 nvidia-device-plugin-daemonset 卸载掉吗?
你应该是之前没卸载掉nvidiade device-plugin吧 先安装的nvidia GPU Opeartor,再安装的Hami,安装完hami之后需要把 nvidia-device-plugin-daemonset 卸载掉吗?
是的,除非你用自定义的资源名
No branches or pull requests
What happened:
k3s 节点重启后,GPU虚拟化失效,nvidia.com/gpu 数目变回物理GPU数目,重启pod hami-device-plugin后,nvidia.com/gpu 数目恢复正常
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
nvidia-smi -a
on your host/etc/docker/daemon.json
)sudo journalctl -r -u kubelet
)dmesg
Environment:
docker version
uname -a
The text was updated successfully, but these errors were encountered: