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
想在ascend-device-plugin里面实现vnpu自动切分和释放逻辑,可是提示容器内不允许操作,请求指教
宿主机执行 npu-smi set -t create-vnpu -i 7 -c 0 -f vir12_3c_32g npu-smi info -t info-vnpu -i 7 -c 0 显示结果:
+-------------------------------------------------------------------------------+ | NPU resource static info as follow: | | Format:Free/Total NA: Currently, query is not supported. | | AICORE Memory AICPU VPC VENC VDEC JPEGD JPEGE PNGD | | GB | |===============================================================================| | 12/24 30/64 4/7 5/10 0/0 1/2 14/28 2/4 NA/NA | +-------------------------------------------------------------------------------+ | Total number of vnpu: 1 | +-------------------------------------------------------------------------------+ | Vnpu ID | Vgroup ID | Container ID | Status | Template Name | +-------------------------------------------------------------------------------+ | 212 | 0 | 000000000000 | 0 | vir12_3c_32g | +-------------------------------------------------------------------------------+
容器内执行:npu-smi set -t destroy-vnpu -i 7 -c 0 -v 212 提示 This command cannot be executed on a VM or container.
代码里调用驱动: destroy virtual device failed, error code: -8002
The text was updated successfully, but these errors were encountered:
No branches or pull requests
想在ascend-device-plugin里面实现vnpu自动切分和释放逻辑,可是提示容器内不允许操作,请求指教
宿主机执行 npu-smi set -t create-vnpu -i 7 -c 0 -f vir12_3c_32g
npu-smi info -t info-vnpu -i 7 -c 0 显示结果:
容器内执行:npu-smi set -t destroy-vnpu -i 7 -c 0 -v 212
提示
This command cannot be executed on a VM or container.
代码里调用驱动:
destroy virtual device failed, error code: -8002
The text was updated successfully, but these errors were encountered: