Skip to content

NIXL Firmware Page Registration Fan-Out Triggers Host OOM Kills on HGX H200 and B200

NVIDIA Inference Xfer Library workloads on HGX H200 and HGX B200 instances triggered host OOM kills because UCX registered GPU memory as firmware pages across all 8 NICs simultaneously, consuming ~34 GiB of host memory per GPU in firmware-level registrations. The root cause was traced to UCX registering every reachable HCA for each buffer, creating firmware page fan-out proportional to NIC count.

Quick answer

NVIDIA Inference Xfer Library workloads on HGX H200 and HGX B200 instances triggered host OOM kills because UCX registered GPU memory as firmware pages across all 8 NICs simultaneously, consuming ~34 GiB of host memory per GPU in firmware-level registrations.

Reliability#crusoe#nixl#ucx#firmware-page#host-oom#h200

What this failure is

NIXL Firmware Page Registration Fan-Out Triggers Host OOM Kills on HGX H200 and B200 is a Reliability failure seen during ML training runs. NVIDIA Inference Xfer Library workloads on HGX H200 and HGX B200 instances triggered host OOM kills because UCX registered GPU memory as firmware pages across all 8 NICs simultaneously, consuming ~34 GiB of host memory per GPU in firmware-level registrations. The root cause was traced to UCX registering every reachable HCA for each buffer, creating firmware page fan-out proportional to NIC count. Common tags: Crusoe, Nixl, Ucx, Firmware Page.

Live diagnosis, no signup

Is this what broke your run? Paste your log.

You're reading about NIXL Firmware Page Registration Fan-Out Triggers Host OOM Kills on HGX H200 and B200. Paste your own crash log or traceback below and get the real root cause for YOUR run, not this generic entry. No account, no card. Logs are masked at ingress and never saved to account history.

training_logs.txt
No log to hand? Try one:

3 free diagnoses/day

Want 14 days on the Scale plan?

Request an evaluation code. A verified workplace organization activates up to 50 diagnoses a day, alerts, history, and follow-up questions. No credit card or automatic subscription.

Evaluate one incident

Why it happens (the mechanism)

UCX registers each GPU buffer on every reachable HCA (all 8 NICs per node) creating firmware page duplication factor of N_nics. Each firmware page consumes ~35 KB of locked host memory per registration entry. With 75 GB registered per GPU * 8 NICs, firmware overhead reaches ~34 GiB of host memory before any workload memory. Taken together, these mechanisms explain why the failure is reproducible, why it tends to surface on specific workloads or scales, and why generic mitigation attempts often fall short without addressing the underlying cause.

What you'll observe

  • Host processes killed by OOM killer with GPUs at normal HBM utilization levels
  • MemAvailable in /proc/meminfo drops to zero despite adequate host RAM capacity
  • Swap fills up and kernel OOM killer activates without GPU memory pressure

Common symptoms and what they mean

SymptomWhy it happens
/proc/meminfo shows MemAvailable = 0 with buffers/cache fully reclaimed during NIXL-heavy workloadsUCX registers each GPU buffer on every reachable HCA (all 8 NICs per node) creating firmware page duplication factor of N_nics
fw_pages_total in debug counters shows >1 million firmware pages per NIC for ~75 GB registered per GPUEach firmware page consumes ~35 KB of locked host memory per registration entry
Kernel dmesg: "Out of memory: Killed process <PID> (python)" with no GPU-side errorsWith 75 GB registered per GPU * 8 NICs, firmware overhead reaches ~34 GiB of host memory before any workload memory

Which systems are affected

  • NVIDIA HGX H200 and HGX B200 with 8 NICs per node
  • NIXL workloads with GPU memory registration exceeding ~75 GB per GPU
  • UCX-based communication (UCX 1.20 and earlier)
  • KVM-virtualized GPU instances with PCIe passthrough

How to confirm this is the problem

Use this checklist to test the hypothesis against a small reproduction. No single line proves the root cause, so preserve the preceding events and compare one variable at a time.

  • Reproduce the failure from a clean checkpoint/seed: the symptom must appear without warm-up state from a previous run.
  • Verified signal present: /proc/meminfo shows MemAvailable = 0 with buffers/cache fully reclaimed during NIXL-heavy workloads
  • Verified signal present: fw_pages_total in debug counters shows >1 million firmware pages per NIC for ~75 GB registered per GPU
  • Verified signal present: Kernel dmesg: "Out of memory: Killed process <PID> (python)" with no GPU-side errors
  • A targeted fix from the "How to fix it" section eliminates or substantially reduces the symptom within one validation pass.

The fix and the prevention pattern

The root cause is on this page and stays free. A free account adds the exact remediation steps, saved history, and the fix on every entry in the encyclopedia.

Sign up free. Unlock the full analysis

No credit card. Daily allowance follows verified trust tier. Instant access.

Diagnose this failure in VS Code

Select the traceback or open the failed terminal, then run Denpex locally to see the initiating rank, collateral failures, exact fix, and verification command without uploading the log.

Install the free VS Code extension

Root cause

  • UCX registers each GPU buffer on every reachable HCA (all 8 NICs per node) creating firmware page duplication factor of N_nics
  • Each firmware page consumes ~35 KB of locked host memory per registration entry
  • With 75 GB registered per GPU * 8 NICs, firmware overhead reaches ~34 GiB of host memory before any workload memory

The fix and how to prevent it

Evaluate Denpex on your own logs

Request a Scale evaluation code. A verified workplace organization activates 14 days with up to 50 diagnoses a day. Every account keeps its current diagnosis allowance and gets a verification path. No card or automatic subscription.

We send a single-use code tied to that address. Static provider and TLD rules do not reject valid addresses. Account trust determines the benefit after signup.

Don't just read the fix, diagnose your run

The encyclopedia tells you what went wrong. Denpex tells you what went wrong in YOUR training run. With your logs, your config, and your stack.