← All guides

MIG on a Workstation GPU: Splitting an RTX PRO 6000's 96GB Into Isolated Instances

NVIDIA's datasheet says the RTX PRO 6000 Blackwell splits into up to four fully isolated instances. That is true, and it is the first workstation card where it is. What the datasheet does not say: MIG on this card needs a vBIOS your reseller has to send you, a firmware mode that disables every display output on the card, Linux, and a willingness to give each instance a quarter of the memory bandwidth. This page is for the person who wants to serve several models or several users from one 96GB card and needs to know whether MIG is the right tool or an expensive detour.

Bottom Line

  • The RTX PRO 6000 Blackwell is the first workstation card with MIG. Profiles: 4 x 1g.24gb, 2 x 2g.48gb, or 1 x 4g.96gb. All three variants, per NVIDIA’s MIG user guide.
  • Enabling it is real work. A vBIOS your reseller has to send you, a compute-only firmware mode that disables the card’s display outputs, Linux, an R580-class driver, ReBAR on.
  • Each 24GB slice gets a quarter of the SMs and roughly a quarter of the bandwidth, about 450 GB/s. A used RTX 3090 has the same 24GB at 936 GB/s.
  • MIG buys isolation, not capacity. One person running two models should not split the card.
  • Instances cannot be resized live. Reconfiguring means destroying and recreating them. MIG mode does not persist across reboots on this architecture.

What MIG Actually Is

Multi-Instance GPU partitions one physical GPU into several hardware-isolated GPUs. Each instance gets its own slice of streaming multiprocessors, its own memory, its own share of the memory controllers and L2 cache, and its own fault domain. A process on one instance cannot see, address or starve another. To the driver each instance is a separate CUDA device.

That is different from what most people do today, which is run two models on one card and let them share. Sharing works. It gives no guarantees. A runaway context on one model can evict the other, and a crash in one process can take the device down for both. MIG exists for the cases where that is unacceptable.

Until this generation MIG was a datacentre feature: A100, A30, H100, H200, B200. The RTX PRO 6000 Blackwell brings it to a card you can put in a tower under a desk, and NVIDIA’s own Max-Q datasheet leads with it.

The Profiles

From NVIDIA’s MIG user guide, table for the RTX PRO 6000 Blackwell (96GB):

ProfileMemorySM fractionInstancesNote
MIG 1g.24gb24 GB1/44The multi-tenant layout
MIG 1g.24gb+gfx24 GB1/44Graphics-capable variant
MIG 2g.48gb48 GB1/22Two “48GB cards”
MIG 2g.48gb+gfx48 GB1/22Graphics-capable variant
MIG 4g.96gb96 GB1/11The whole card, in MIG mode

Two things the table implies that the marketing does not state.

Bandwidth is sliced with memory. MIG partitions the memory controllers along with the memory, so a 1g.24gb instance gets a quarter of the memory slices and, by the design of the partition, roughly a quarter of the 1,792 GB/s: about 450 GB/s. We have not seen NVIDIA publish a per-instance bandwidth figure for this card, so treat 450 GB/s as arithmetic on the partition, not a measurement. Token generation is bandwidth-bound, so a 24GB slice generates tokens at roughly a quarter of the full card’s rate.

No instance can be bigger than the card, and no model can span instances. MIG isolates in both directions. A 75GB model does not run on two 48GB instances. If you might need the whole card for one model, you leave MIG off for that job, which means destroying the instances.

What It Costs to Turn On

This is the section that decides whether MIG is for you. Every item below is documented in NVIDIA’s own developer forums or user guide, and several of them cost owners weeks in 2025.

1. A vBIOS your card probably did not ship with. The minimum is 98.02.55.00.00 on the Workstation Edition and 98.02.6A.00.08 on the Max-Q. Cards from the first retail wave carried 98.02.52.00.02, and nvidia-smi -mig 1 on those answers “Not Supported”. NVIDIA forum staff direct owners to contact the reseller with the serial number, for a PNY card that means PNY, to obtain the field upgrade tool. NVIDIA does not distribute it directly, and one staff reply floated an RMA as the faster path. Ask the seller which vBIOS the card carries before you buy it for MIG.

2. Compute-only display mode, which kills the display outputs. MIG needs the large BAR1 address space that the card’s graphics firmware mode does not expose. NVIDIA’s displaymodeselector --mode=compute switches the firmware, and NVIDIA’s own guide states that on a single-card workstation this disables physical display output. The four DisplayPort 2.1 connectors go dark. You need an integrated GPU or a second card for a monitor, or you run the box headless.

3. Linux. The MIG user guide lists CUDA-supported Linux distributions as the operating environment. A forum owner who tried the mode switch on Windows got the switch to work and MIG itself to answer “Not Supported”. Treat MIG on this card as Linux-only until NVIDIA documents otherwise.

4. A current driver stack and ReBAR. R580-class driver with CUDA 13, and Resizable BAR enabled in system firmware. Both are quick. Both are also things a workstation vendor may ship disabled.

5. Re-creation on every boot. On Hopper and later, enabling MIG mode no longer needs a GPU reset, which is good. It is also no longer persistent across reboots, so you need a systemd unit that enables MIG and recreates your instances at startup, and every service that depends on them has to wait for it.

Add it up and MIG on this card is a day of setup and a dependency on your reseller, on top of a card that lists at $13,250 as of August 2026.

Who Should Split the Card

SituationSplit it?Why
One person, one modelNoYou give up 3/4 of the bandwidth for nothing
One person, two models (coder + embedder)NoRun both on the unsplit card. Each uses full bandwidth when the other idles.
A team of 2–4 sharing one workstationYes, 1g.24gb x4 or 2g.48gb x2Hard isolation. One person’s runaway context cannot evict another’s job.
Serving internal APIs with a latency guaranteeYesGuaranteed SM and bandwidth share per service
Experimental model beside a production modelYes, 2g.48gb x2A crash in the experiment stays in its instance
Fine-tuning while servingYes, 2g.48gb x2The two workloads have opposite memory behaviour
Anything that might need 96GB for one modelNo, or accept tear-downsNo instance spans the card

The honest summary: MIG is a multi-tenant feature. If the word “tenant” does not describe your situation, the unsplit card is faster and simpler.

The 24GB Slice Against a 24GB Card

The comparison that puts the feature in proportion. As of August 2026:

MIG 1g.24gb sliceUsed RTX 3090
Memory24 GB GDDR7, ECC24 GB GDDR6X, no ECC
Bandwidth~450 GB/s (1/4 of 1,792, derived)936 GB/s
Compute1/4 of 24,064 CUDA cores, Blackwell10,496 CUDA cores, Ampere
Cost per 24GB~$3,300 (a quarter of $13,250 list)$1,000–1,300
Slots and power for four of themOne dual slot, 600W (or 300W Max-Q)Four triple slots, ~1,400W, a 20A circuit
IsolationHardware, per instancePer card, by construction

Four 3090s are cheaper and faster per instance. They are also four cards, a server board with the lanes to feed them, roughly 1,400W of GPU, and a dedicated 20A circuit. One RTX PRO 6000 in MIG mode is four isolated 24GB devices in one slot on one power connector, with ECC and a warranty. That is what the price buys. It does not buy throughput.

What Runs in a Slice

A 1g.24gb instance is, for model-fitting purposes, a 24GB GPU with a quarter of the bandwidth. Our best local LLM for 24GB picks apply for weights. Adjust expectations for speed: a dense 27B at Q4 that runs at 30-plus tok/s on a full card lands near a quarter of that on a slice. A 3B-active MoE such as Qwen3.6-35B-A3B is the model class that stays comfortable, because it reads few bytes per token. The MoE vs dense at 24GB page is written for exactly this memory shape.

A 2g.48gb instance is a 48GB GPU at ~900 GB/s, which is close to a 3090’s bandwidth with double the memory. It runs a dense 70B at Q4 with the same context ceiling as any 48GB card.

The Card

The RTX PRO 6000 Blackwell is the one workstation card that does any of this. 96GB GDDR7 with ECC, 1,792 GB/s, PCIe 5.0 x16, MIG up to four instances on all three variants. NVIDIA lists it at $13,250 as of August 2026; street runs higher.

NVIDIA RTX PRO 6000 Blackwell 96GB — buy it for MIG only if the multi-tenant table above describes you, and ask the seller for the vBIOS version before you pay. For a 24/7 shared box the 300W Max-Q variant is the better fit; it has the same MIG profiles and a lower vBIOS floor to clear, and our comparison explains the rest. We do not have a link for the Max-Q; 300W total board power on the listing is how you identify it.

If the goal is several isolated 24GB devices and the budget is not five figures, the cheaper isolation is several cards:

EVGA GeForce RTX 3090 24GB — $1,000–1,300 used, 936 GB/s, and a whole card per tenant. Two of them is the 48GB tier; four is a multi-GPU rig with its own problems.

Enabling It, In Outline

On a card with a qualifying vBIOS, on Linux, with ReBAR on and no display attached to it:

# 1. Switch the card to compute-only mode (disables its display outputs), then reboot
sudo ./displaymodeselector --mode=compute --gpu=0

# 2. Enable MIG mode
sudo nvidia-smi -i 0 -mig 1

# 3. List the profiles the driver offers
nvidia-smi mig -lgip

# 4. Create four 24GB GPU instances, each with its compute instance
sudo nvidia-smi mig -i 0 -cgi 1g.24gb,1g.24gb,1g.24gb,1g.24gb -C

# 5. Confirm; each instance appears as its own CUDA device
nvidia-smi -L

Put steps 2 and 4 in a systemd unit that runs before your inference services. To go back to one 96GB device: destroy the compute instances, destroy the GPU instances, nvidia-smi -i 0 -mig 0. Every workload on the card stops while you do it.

The Decision

You wantDo this
One model, fastUnsplit card. MIG off.
Two models for yourselfUnsplit card. Both run; the idle one costs nothing.
Several people or services, isolatedMIG, 1g.24gb x4 or 2g.48gb x2
Isolation without a $13,250 cardSeveral cheaper cards, one tenant each
MIG on WindowsNot documented as supported. Plan for Linux.
MIG on a card that also drives your monitorNot possible. Compute mode disables the outputs.

See Also

Sources

  • NVIDIA Multi-Instance GPU User Guide, “Supported GPUs”: RTX PRO 6000 Blackwell Server Edition, Workstation Edition and Max-Q Workstation Edition, 96GB, maximum 4 instances. “Supported MIG Profiles”: MIG 1g.24gb (1/4 memory, 1/4 SM, 4 instances), 2g.48gb (1/2, 1/2, 2), 4g.96gb (full, 1), plus +gfx and media-engine variants
  • NVIDIA MIG User Guide, “Getting Started”: from Hopper onward enabling MIG no longer requires a GPU reset and MIG mode is no longer persistent across reboots; supported environment is CUDA-supported Linux distributions; on RTX PRO Blackwell GPUs setting display mode to compute disables physical display output
  • NVIDIA Display Mode Selector tool page: compatible with all three RTX PRO 6000 Blackwell variants; supported GPUs must operate in compute-only mode with physical display outputs disabled for MIG
  • NVIDIA developer forums, “RTX PRO 6000 Blackwell Workstation Edition — vBIOS too old for MIG (98.02.52.00.02)”: minimum vBIOS 98.02.55.00.00, driver 580.159.03 with CUDA 13.0, nvidia-smi “Not Supported” error, NVIDIA staff directing owners to the reseller with the serial number for the field upgrade tool
  • Level1Techs forum thread on MIG support for the RTX PRO 6000, citing NVIDIA documentation for the Max-Q minimum vBIOS of 98.02.6A.00.08 and the two-step enablement (vBIOS update, then displaymodeselector compute mode)
  • Exxact support guide on enabling MIG on RTX PRO 5000/6000 Blackwell: driver 580.95 or newer, CUDA 13.0, Resizable BAR enabled (read via search summary; the page itself refused our fetch)
  • NVIDIA RTX PRO 6000 Blackwell product page: 96GB GDDR7 ECC, 1,792 GB/s, 600W, dual slot, four DisplayPort 2.1, MIG up to four instances
  • Per-instance bandwidth (~450 GB/s) is our arithmetic on a quarter partition of 1,792 GB/s and is labelled as derived; NVIDIA publishes no per-instance figure we could find
  • Prices as of August 2026 from our hardware price reference: RTX PRO 6000 $13,250 NVIDIA list (VideoCardz, wccftech); used RTX 3090 $1,000–1,300 (ResalePrices, gpudojo)

Need OpenClaw fixed live?

Remote rescue sessions for gateway, auth, tunnel, VPS, and model access problems.

See Rescue Session

Read next

Is 96GB of VRAM Enough for Local AI in 2026?
96GB is the first tier where a dense 70B runs at its full 128K window: 42.5GB of Q4 weights plus exactly 40 GiB of FP16 KV cache is 82.5GB, and it fits. What 96GB unlocks, what it still cannot hold, and what the one card that has it costs in August 2026.
RTX PRO 6000 Blackwell Max-Q vs Workstation Edition for Local LLMs (August 2026)
Same 96GB, same 1,792 GB/s, same 24,064 CUDA cores — but 300W vs 600W. For local LLM inference the Max-Q loses almost nothing and gains 1.75x the AI TOPS per watt. The full datasheet delta, and the one spec that decides it.
Best Local LLM for 96GB of VRAM (August 2026)
96GB of VRAM is essentially one product: the RTX PRO 6000 Blackwell. It has the same 1,792 GB/s bandwidth as an RTX 5090 that costs a third as much. What 96GB actually runs — 70B at Q8, gpt-oss 120B, Llama 4 Scout — and where it still fails.
Best GPU for Fine-Tuning vs Inference (August 2026): Why the Answer Flips
Fine-tuning and inference reward opposite GPU traits. Inference wants bandwidth, so the RTX 5090 wins. Fine-tuning wants capacity and interconnect, and NVIDIA removed NVLink after the RTX 3090 — which is why two 3090s can beat two 5090s for training. Full VRAM math for full/LoRA/QLoRA, plus August 2026 prices.