[GH-ISSUE #3108] [Installation] Publish prebuilt ROCm/HIP wheels to PyPI #796

Open
opened 2026-10-29 21:19:38 +00:00 by bsakaguchi · 8 comments
Owner

Originally created by @charxwu on GitHub (Jul 24, 2026).
Original GitHub issue: https://github.com/kvcache-ai/Mooncake/issues/3108

Originally assigned to: @Aionw, @amd-arozanov on GitHub.

Summary

We are bringing up MiniMax-M3 MXFP4 vLLM disaggregated benchmarks on AMD MI355X with Mooncake DRAM KV offload (MooncakeStoreConnector + MultiConnector with MoRIIO P/D). HIP support landed in #1742, but today the only PyPI packages are CUDA (mooncake-transfer-engine, mooncake-transfer-engine-cuda13), CPU-only (mooncake-transfer-engine-non-cuda), and NPU (mooncake-transfer-engine-npu). There is no ROCm/HIP wheel.

Our current workaround is to build Mooncake from source at job runtime with -DUSE_HIP=ON -DUSE_CUDA=OFF and cache the artifact — workable but slow on first run and hard to satisfy downstream CI policies that require pinned images to run as shipped (no runtime builds).

Request

Please publish a prebuilt ROCm/HIP Python wheel to PyPI, e.g.:

  • mooncake-transfer-engine-rocm (or -hip), versioned alongside existing releases (we pin v0.3.11.post1 today)

Minimum requirements for our MI355X / ROCm 7.x stack:

  • Built with -DUSE_HIP=ON, -DWITH_STORE=ON
  • Includes Transfer Engine + Mooncake Store Python bindings (mooncake.engine, mooncake.store, mooncake_master CLI)
  • Links against libamdhip64.so but does not vendor incompatible ROCm runtime libs (same approach validated in #1742 dist-rocm-hip wheels)
  • manylinux_2_28_x86_64 for cp310–cp313 (matching existing CUDA wheel matrix)

Why not mooncake-transfer-engine-non-cuda?

The non-CUDA wheel is CPU-only. Our vLLM disagg path validates HIP linkage (libamdhip64.so) for the Store/TE stack on MI355X. CPU-only wheels do not satisfy this.

Current workaround

Runtime build in server_vllm.sh:

cmake -S Mooncake -B build -DUSE_CUDA=OFF -DUSE_HIP=ON -DWITH_STORE=ON ...
Originally created by @charxwu on GitHub (Jul 24, 2026). Original GitHub issue: https://github.com/kvcache-ai/Mooncake/issues/3108 Originally assigned to: @Aionw, @amd-arozanov on GitHub. ## Summary We are bringing up **MiniMax-M3 MXFP4 vLLM disaggregated benchmarks on AMD MI355X** with Mooncake DRAM KV offload (`MooncakeStoreConnector` + MultiConnector with MoRIIO P/D). HIP support landed in [#1742](https://github.com/kvcache-ai/Mooncake/pull/1742), but today the only PyPI packages are CUDA (`mooncake-transfer-engine`, `mooncake-transfer-engine-cuda13`), CPU-only (`mooncake-transfer-engine-non-cuda`), and NPU (`mooncake-transfer-engine-npu`). **There is no ROCm/HIP wheel.** Our current workaround is to **build Mooncake from source at job runtime** with `-DUSE_HIP=ON -DUSE_CUDA=OFF` and cache the artifact — workable but slow on first run and hard to satisfy downstream CI policies that require pinned images to run as shipped (no runtime builds). ## Request Please publish a **prebuilt ROCm/HIP Python wheel** to PyPI, e.g.: - `mooncake-transfer-engine-rocm` (or `-hip`), versioned alongside existing releases (we pin `v0.3.11.post1` today) Minimum requirements for our MI355X / ROCm 7.x stack: - Built with `-DUSE_HIP=ON`, `-DWITH_STORE=ON` - Includes Transfer Engine + Mooncake Store Python bindings (`mooncake.engine`, `mooncake.store`, `mooncake_master` CLI) - Links against `libamdhip64.so` but **does not vendor incompatible ROCm runtime libs** (same approach validated in #1742 `dist-rocm-hip` wheels) - `manylinux_2_28_x86_64` for cp310–cp313 (matching existing CUDA wheel matrix) ## Why not `mooncake-transfer-engine-non-cuda`? The non-CUDA wheel is CPU-only. Our vLLM disagg path validates HIP linkage (`libamdhip64.so`) for the Store/TE stack on MI355X. CPU-only wheels do not satisfy this. ## Current workaround Runtime build in `server_vllm.sh`: ```bash cmake -S Mooncake -B build -DUSE_CUDA=OFF -DUSE_HIP=ON -DWITH_STORE=ON ...
Author
Owner

@github-actions[bot] commented on GitHub (Jul 24, 2026):

Thanks for opening this issue, @charxwu!

Field Value
Issue #3108
GitHub user ID 296364977
Reporter @charxwu

A maintainer will triage this when possible. To help us respond faster, please include:

  • Mooncake version or commit SHA
  • Environment (OS, CUDA/driver, RDMA stack if relevant)
  • Steps to reproduce and expected vs. actual behavior

Useful links: Documentation · Contributing guide

This message was posted automatically by the issue bot.

<!-- gh-comment-id:5071869975 --> @github-actions[bot] commented on GitHub (Jul 24, 2026): Thanks for opening this issue, @charxwu! | Field | Value | |-------|-------| | **Issue** | #3108 | | **GitHub user ID** | `296364977` | | **Reporter** | @charxwu | A maintainer will triage this when possible. To help us respond faster, please include: - Mooncake version or commit SHA - Environment (OS, CUDA/driver, RDMA stack if relevant) - Steps to reproduce and expected vs. actual behavior Useful links: [Documentation](https://kvcache-ai.github.io/Mooncake/) · [Contributing guide](https://github.com/kvcache-ai/Mooncake/blob/main/CONTRIBUTING.md) > This message was posted automatically by the issue bot.
Author
Owner

@ykwd commented on GitHub (Jul 25, 2026):

Sounds good! We just released v0.3.12.post1, so this is a great version for us to start publishing an official ROCm/HIP wheel.

@amd-arozanov Would you be interested in collaborating on this when you have time? We'd really appreciate your expertise to help make official AMD wheels happen.

<!-- gh-comment-id:5078263736 --> @ykwd commented on GitHub (Jul 25, 2026): Sounds good! We just released **v0.3.12.post1**, so this is a great version for us to start publishing an official ROCm/HIP wheel. @amd-arozanov Would you be interested in collaborating on this when you have time? We'd really appreciate your expertise to help make official AMD wheels happen.
Author
Owner

@functionstackx commented on GitHub (Jul 27, 2026):

@andyluo7 @chunfangamd

<!-- gh-comment-id:5086179651 --> @functionstackx commented on GitHub (Jul 27, 2026): @andyluo7 @chunfangamd
Author
Owner

@Aionw commented on GitHub (Jul 27, 2026):

I'd be happy to collaborate with the ROCm and AMD teams to make Mooncake ROCm/HIP packages available on PyPI.

<!-- gh-comment-id:5090889170 --> @Aionw commented on GitHub (Jul 27, 2026): I'd be happy to collaborate with the ROCm and AMD teams to make Mooncake ROCm/HIP packages available on PyPI.
Author
Owner

@amd-arozanov commented on GitHub (Jul 28, 2026):

@Aionw, thanks! Feel free to reach me if you need any help or you have any questions

<!-- gh-comment-id:5102378155 --> @amd-arozanov commented on GitHub (Jul 28, 2026): @Aionw, thanks! Feel free to reach me if you need any help or you have any questions
Author
Owner

@tjtanaa commented on GitHub (Aug 23, 2026):

@amd-arozanov how is this effort going? It would be nice to have mooncake wheel as it is used in a very broad ecosystem, from inferencing to RL training as well.

<!-- gh-comment-id:5384629995 --> @tjtanaa commented on GitHub (Aug 23, 2026): @amd-arozanov how is this effort going? It would be nice to have mooncake wheel as it is used in a very broad ecosystem, from inferencing to RL training as well.
Author
Owner

@functionstackx commented on GitHub (Aug 23, 2026):

@tjtanaa andy luo has it here https://github.com/kvcache-ai/Mooncake/pulls?q=is%3Apr+is%3Aclosed+author%3Aandyluo7

<!-- gh-comment-id:5387869386 --> @functionstackx commented on GitHub (Aug 23, 2026): @tjtanaa andy luo has it here https://github.com/kvcache-ai/Mooncake/pulls?q=is%3Apr+is%3Aclosed+author%3Aandyluo7
Author
Owner

@tjtanaa commented on GitHub (Aug 23, 2026):

@tjtanaa andy luo has it here https://github.com/kvcache-ai/Mooncake/pulls?q=is%3Apr+is%3Aclosed+author%3Aandyluo7

Thank you @functionstackx , so we will get the wheel only in the next release.

<!-- gh-comment-id:5388703130 --> @tjtanaa commented on GitHub (Aug 23, 2026): > @tjtanaa andy luo has it here https://github.com/kvcache-ai/Mooncake/pulls?q=is%3Apr+is%3Aclosed+author%3Aandyluo7 Thank you @functionstackx , so we will get the wheel only in the next release.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
kvcache-ai/Mooncake#796
No description provided.