vllm - ✅(Solved) Fix [Tracking] NIXL 1.0.0 Support for NIXL KV Connector [3 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vllm-project/vllm#39521Fetched 2026-04-11 06:13:03
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
1
Author
Participants
Timeline (top)
subscribed ×2labeled ×1mentioned ×1

NIXL v1.0.0 was released on 2026-03-13 with several API changes. vLLM currently pins nixl[cu13] >= 0.7.1, < 0.10.0 (in requirements/kv_connectors.txt), which excludes 1.0.0. This issue tracks the work needed to support nixl 1.0.0+ in the NixlConnector.

Note: 0.10.x is compatible too.

Root Cause

NIXL v1.0.0 was released on 2026-03-13 with several API changes. vLLM currently pins nixl[cu13] >= 0.7.1, < 0.10.0 (in requirements/kv_connectors.txt), which excludes 1.0.0. This issue tracks the work needed to support nixl 1.0.0+ in the NixlConnector.

Note: 0.10.x is compatible too.

PR fix notes

PR #39797: [PD] Bump Nixl version

Description (problem / solution / changelog)

Address https://github.com/vllm-project/vllm/issues/39521.

Mind that we're pinning cu13 on vllm right now.

Changed files

  • requirements/kv_connectors.txt (modified, +3/-3)

PR #39851: [CI][NIXL] Fix PD CI breakage: pin nixl-cu{12,13} versions

Description (problem / solution / changelog)

nixl-cu12==1.0.1 dropped on PyPI today (19:38 UTC) and ships nixl_ep compiled against libcudart.so.12 — crashes on CUDA 13 CI runners. Our < 0.10.0 constraint only pins the meta-package, not the backends:

[2026-04-14T21:21:43Z]  + nixl==0.9.0
[2026-04-14T21:21:43Z]  + nixl-cu12==1.0.1
[2026-04-14T21:21:43Z]  + nixl-cu13==1.0.1

Temp fix: pin nixl-cu12 and nixl-cu13 to < 0.10.0. @NickLucche is working on the proper version bump in #39797 (tracking #39521).

Changed files

  • requirements/kv_connectors.txt (modified, +2/-0)

PR #1546: PLUGINMANAGER: Defer plugin load to the point where they are actually used

Description (problem / solution / changelog)

What?

Defer plugin dlopen from discovery time to first use. Plugins found on disk are now recorded by name only; the actual dlopen happens when createBackend() or getPluginParams() is called for that specific plugin.

Why?

https://github.com/vllm-project/vllm/issues/39521

Creating a nixl_agent crashes with a segfault on some systems (RHEL 9 / Rocky 9 bare-metal DGX H100) due to eager plugin loading.

During nixlPluginManager construction, every plugin .so in the plugins directory is dlopen'd, including plugins the user never requested (e.g. LIBFABRIC on InfiniBand systems). The dlopen triggers transitive dependency initialization (libnuma -> numa_hook.so) which crashes before any NIXL code even executes. The Python nixl_agent.__init__ further aggravates this by calling getPluginParams() on every discovered plugin, forcing a second dlopen attempt for each.

How?

C++ (plugin_manager.h, nixl_plugin_manager.cpp):

  • Add discovered_backend_plugins_ and discovered_telemetry_plugins_ sets to track plugin names found on disk without loading them.
  • Add explicit_plugin_paths_ map to preserve exact .so paths from the plugin list file, so loadBackendPlugin() tries those first before scanning directories.
  • discoverBackendPlugin() / discoverTelemetryPlugin(): record the plugin name instead of calling loadBackendPlugin().
  • loadPluginsFromList(): same, record names and paths instead of dlopen'ing.
  • getLoadedBackendPluginNames() / getLoadedTelemetryPluginNames(): include discovered names so getAvailPlugins() still returns them.
  • loadBackendPlugin() / loadTelemetryPlugin(): remove from the discovered set on load (success or failure).
  • unloadBackendPlugin() / unloadTelemetryPlugin(): put the name back into the discovered set so getAvailPlugins() still reports it after unload.

Python (_api.py):

  • Remove the for plugin in self.plugin_list: getPluginParams(plugin) loop from nixl_agent.__init__.
  • Add _load_plugin_params() helper that lazily populates the cache on first access.
  • get_plugin_params() and get_plugin_mem_types() call the helper before returning.

No API changes. get_plugin_list() returns the same names. create_backend(), getPluginParams(), and instantiate_all=True all work identically. The dlopen just happens on demand instead of unconditionally at init.

Changed files

  • src/api/python/_api.py (modified, +14/-4)
  • src/core/nixl_plugin_manager.cpp (modified, +46/-11)
  • src/core/plugin_manager.h (modified, +6/-0)
RAW_BUFFERClick to expand / collapse

Summary

NIXL v1.0.0 was released on 2026-03-13 with several API changes. vLLM currently pins nixl[cu13] >= 0.7.1, < 0.10.0 (in requirements/kv_connectors.txt), which excludes 1.0.0. This issue tracks the work needed to support nixl 1.0.0+ in the NixlConnector.

Note: 0.10.x is compatible too.

Changes in NIXL 1.0.0

...

TODO Items

...

@NickLucche

Before submitting a new issue...

  • Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

extent analysis

TL;DR

Update the nixl version range in requirements/kv_connectors.txt to include version 1.0.0.

Guidance

  • Review the API changes in NIXL 1.0.0 to understand the necessary adjustments for the NixlConnector.
  • Update the version range in requirements/kv_connectors.txt to nixl[cu13] >= 0.7.1, < 1.1.0 to include version 1.0.0 and potentially compatible future versions.
  • Verify that the updated version range does not introduce any compatibility issues with other dependencies.
  • Test the NixlConnector with the updated nixl version to ensure it works as expected.

Notes

The current version pinning excludes NIXL 1.0.0, and updating the version range is necessary to support the new release.

Recommendation

Apply workaround: Update the nixl version range in requirements/kv_connectors.txt to include version 1.0.0, as this is a straightforward change that can be made to support the new NIXL release.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING