vllm-omni-npu-model-runner-upgrade

Upgrade vllm-omni NPU model runners to align with vllm-ascend interfaces.

6.0k|1.4k|Updated Sep 11, 2025
One-click install
npx skills add https://github.com/vllm-project/vllm-omni --skill vllm-omni-npu-model-runner-upgrade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vllm-omni-npu-model-runner-upgrade
Source: https://github.com/vllm-project/vllm-omni/tree/main/.claude/skills/vllm-omni-npu-upgrade
Command: npx skills add https://github.com/vllm-project/vllm-omni --skill vllm-omni-npu-model-runner-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Upgrade vllm-omni NPU model runners to align with the latest vllm-ascend codebase while preserving omni-specific logic.

Core Features & Use Cases

  • Updates OmniNPUModelRunner, NPUARModelRunner, and NPUGenerationModelRunner to the latest vllm-ascend interface, including ACLGraphWrapper integration and talker MTP handling.
  • Ensures compatibility with Omni models (Qwen3-Omni, Bagel, MiMo-Audio) across Ascend NPUs, with KV transfer hooks and multimodal outputs preserved.
  • Provides a structured upgrade workflow with omni-specific markers to guide safe porting, testing, and validation.

Quick Start

Follow the upgrade workflow to port the NPU model runners from vllm-omni to vllm-ascend, preserving Omni-specific logic.

Frequently Asked Questions about vllm-omni-npu-model-runner-upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade vllm-omni NPU model runners to align with the latest vllm-ascend?

To upgrade vllm-omni NPU model runners, port OmniNPUModelRunner, NPUARModelRunner, and NPUGenerationModelRunner to the latest vllm-ascend interface using a structured upgrade workflow that preserves omni-specific logic.

What is the process for preserving KV transfer hooks when porting to vllm-ascend?

Preserving KV transfer hooks during the vllm-ascend port involves enforcing Omni-new markers and cross-checking GPU changes to ensure multimodal outputs and hooks remain intact across Ascend NPUs.

Can I use ACLGraphWrapper integration with Omni models on Ascend NPUs?

Yes, ACLGraphWrapper integration is updated for Omni models like Qwen3-Omni, Bagel, and MiMo-Audio on Ascend NPUs, ensuring forward context updates and talker MTP handling maintain production-grade compatibility.

What is the best way to validate NPU model runner upgrades for vllm-omni?

The best way to validate NPU model runner upgrades is by enforcing Omni-new markers, cross-checking with GPU changes, and running type checks and imports to ensure safe porting and production-grade compatibility.

Does the vllm-ascend upgrade workflow support multimodal outputs for Qwen3-Omni?

Yes, the vllm-ascend upgrade workflow supports multimodal outputs for Qwen3-Omni by preserving omni-specific logic during forward context updates and KV transfer hooks integration.

Why does my NPUARModelRunner fail after updating to the latest vllm-ascend codebase?

NPUARModelRunner failures after updating to the latest vllm-ascend codebase typically occur because omni-specific logic requires structured porting with Omni-new markers to align ACLGraphWrapper usage and forward context updates.