c500可以直接用vllm镜像启动bf16的模型吗

c500可以直接用vllm镜像启动bf16的模型吗，我从modelscope上下的原始模型，可以直接启动吗，qwen3.6-27b

尊敬的开发者您好，C500支持BF16，可以直接启动

我这边会一直起不来，持续重试，不知道是什么情况呢，

一、软硬件信息
1.服务器厂家:
2.沐曦GPU型号：MetaX C550
3.操作系统内核版本：Linux metax-host-013 5.15.0-119-generic #129-Ubuntu SMP Fri Aug 2 19:25:20 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
4.是否开启CPU虚拟化：Virtualization features:
Virtualization: VT-x
5.mx-smi回显：root@metax-host-013:/home/metax/models# mx-smi
mx-smi version: 2.3.1

=================== MetaX System Management Interface Log ===================
Timestamp : Wed Jun 3 08:52:42 2026

Attached GPUs : 8
+---------------------------------------------------------------------------------+
| MX-SMI 2.3.1 Kernel Mode Driver Version: 3.3.12 |
| MACA Version: 3.7.2.0 BIOS Version: 1.29.1.0 |
|------------------+-----------------+---------------------+----------------------|
| Board Name | GPU Persist-M | Bus-id | GPU-Util sGPU-M |
| Pwr:Usage/Cap | Temp Perf | Memory-Usage | GPU-State |
|==================+=================+=====================+======================|
| 0 MetaX C550 | 0 Off | 0000:2b:00.0 | 0% Disabled |
| 54W / 450W | 33C P0 | 858/65536 MiB | Available |
+------------------+-----------------+---------------------+----------------------+
| 1 MetaX C550 | 1 Off | 0000:3a:00.0 | 0% Disabled |
| 53W / 450W | 34C P0 | 858/65536 MiB | Available |
+------------------+-----------------+---------------------+----------------------+
| 2 MetaX C550 | 2 Off | 0000:4d:00.0 | 0% Disabled |
| 57W / 450W | 36C P0 | 858/65536 MiB | Available |
+------------------+-----------------+---------------------+----------------------+
| 3 MetaX C550 | 3 Off | 0000:5c:00.0 | 0% Disabled |
| 53W / 450W | 33C P0 | 858/65536 MiB | Available |
+------------------+-----------------+---------------------+----------------------+
| 4 MetaX C550 | 4 Off | 0000:aa:00.0 | 0% Disabled |
| 53W / 450W | 33C P0 | 858/65536 MiB | Available |
+------------------+-----------------+---------------------+----------------------+
| 5 MetaX C550 | 5 Off | 0000:ba:00.0 | 0% Disabled |
| 55W / 450W | 35C P0 | 858/65536 MiB | Available |
+------------------+-----------------+---------------------+----------------------+
| 6 MetaX C550 | 6 Off | 0000:ca:00.0 | 0% Disabled |
| 52W / 450W | 34C P0 | 858/65536 MiB | Available |
+------------------+-----------------+---------------------+----------------------+
| 7 MetaX C550 | 7 Off | 0000:da:00.0 | 0% Disabled |
| 54W / 450W | 34C P0 | 858/65536 MiB | Available |
+------------------+-----------------+---------------------+----------------------+

+---------------------------------------------------------------------------------+
| Process: |
| GPU PID Process Name GPU Memory |
| Usage(MiB) |
|=================================================================================|
| no process found |
+---------------------------------------------------------------------------------+

End of Log

6.docker info回显：root@metax-host-013:/home/metax/models# docker info
Client:
Version: 29.1.3
Context: default
Debug Mode: false
Plugins:
trust: Manage trust on Docker images (Docker Inc.)
Version: 29.1.3
Path: /usr/libexec/docker/cli-plugins/docker-trust

Server:
Containers: 1
Running: 1
Paused: 0
Stopped: 0
Images: 1
Server Version: 29.1.3
Storage Driver: overlayfs
driver-type: io.containerd.snapshotter.v1
Logging Driver: json-file
Cgroup Driver: systemd
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
CDI spec directories:
/etc/cdi
/var/run/cdi
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version:
runc version:
init version:
Security Options:
apparmor
seccomp
Profile: builtin
cgroupns
Kernel Version: 5.15.0-119-generic
Operating System: Ubuntu 22.04.5 LTS
OSType: linux
Architecture: x86_64
CPUs: 160
Total Memory: 1008GiB
Name: metax-host-013
ID: d1337572-eb0e-4bef-b8e6-e9c1e294c26e
Docker Root Dir: /home/metax/docker
Debug Mode: false
Experimental: false
Insecure Registries:
::1/128
127.0.0.0/8
Registry Mirrors:
docker.m.daocloud.io/
huecker.io/
dockerhub.timeweb.cloud/
Live Restore Enabled: false
Firewall Backend: iptables

7.镜像版本：mx-devops-acr-cn-shanghai.cr.volces.com/pub-registry1/ai-opentest/release/maca/vllm-metax:0.21.0-maca.ai3.7.1.2-dsv4-torch2.8-py310-ubuntu22.04-amd64
8.启动容器命令：
docker run -itd \
--privileged \
--network=host \
--ipc=host \
--security-opt seccomp=unconfined \
--security-opt apparmor=unconfined \
--ulimit memlock=-1 \
-v /pde_ai:/pde_ai \
--name deepseek-v4-flash \
-v /home/metax/:/home/metax/ \
mx-devops-acr-cn-shanghai.cr.volces.com/pub-registry1/ai-opentest/release/maca/vllm-metax:0.21.0-maca.ai3.7.1.2-dsv4-torch2.8-py310-ubuntu22.04-amd64 \
bash
9.容器内执行命令：
nohup env CUDA_VISIBLE_DEVICES=0,1,2,3,4,5,6,7 vllm serve /home/metax/models/Qwen3.6-27B --trust-remote-code --gpu-memory-utilization 0.9 --served-model-name qwen3.6-27b --api-key abcdaasdas--enable-auto-tool-choice --tool-call-parser qwen3_coder --reasoning-parser qwen3 --tensor-parallel-size 8 --max-num-batched-tokens 8192 --default-chat-template-kwargs '{"enable_thinking": false}' --enable-prompt-tokens-details --enable-force-include-usage --enable-prefix-caching> /home/metax/logs/vllm_log.log 2>&1 &
二、问题现象
vllm持续重试不启动

尊敬的开发者您好，请在裸金属执行

dmesg -T | grep -i err

回显如图，请查看

尊敬的开发者您好，请给出详细日志

全部日志在附件

尊敬的开发者您好，请裸金属执行

cd /opt/maca/samples/mccl_tests/perf
bash mccl.sh 8

看起来报错一样跟docker里

尊敬的开发者您好，请重启服务器尝试