Repository navigation
Conversation
|
|
||
| Users do not pick a physical device. They pick a **GPU class**, such as `NVIDIA RTX PRO 6000 Blackwell Server Edition`. Each AZ publishes the classes its hardware provides, so the list in the console depends on the AZ you select. | ||
|
|
||
| The AZ operator maps every class to the device that KubeVirt exposes on the GPU nodes. See [Enabling GPU passthrough](../../operations/compute/gpu-passthrough.md). |
Member
There was a problem hiding this comment.
As this is documenting features, we should try not to go into technical implementation details.
| - **Create or edit**: choose the GPU in the **Compute** step when you create the VM, or change it from **Edit**. | ||
| - **Restart required**: adding, changing or removing a GPU takes effect at the next restart. Until then, the **GPU** card on the instance details page shows *(applies after restart)*. | ||
| - **Scheduling**: the VM only starts on a node with a free GPU of the requested class. If every card of that class is in use, the VM stays `Pending` until one is released. | ||
| - **CPU model**: a VM with a GPU uses the host's CPU model (`host-passthrough`), so the firmware can map the GPU's large memory. This is automatic and works with UEFI guests, including Windows. |
Member
There was a problem hiding this comment.
Where does that come from?
Member
Author
There was a problem hiding this comment.
|
|
||
| The classes appear in the console as soon as the controller restarts with the new configuration. An AZ without `deviceMapping` shows no GPU option. | ||
|
|
||
| !!! note "GitOps deployments" |
Member
There was a problem hiding this comment.
We do not really mention GitOps yet anywhere, as it is a separate way of handling everything altogether, this could be removed
|
|
||
| Superphenix gives every VM that has a GPU the **`host-passthrough`** CPU model, instead of the cluster-wide CPU model. It does this automatically when a GPU is added, and restores the cluster model when the GPU is removed. | ||
|
|
||
| This matters for GPUs with a lot of memory, such as the 96 GB RTX PRO 6000: |
Member
There was a problem hiding this comment.
This all sounds like LLM hallucination, unless it is backed by something real?
Member
Author
There was a problem hiding this comment.
| ## Operational notes | ||
|
|
||
| - **No live migration**: VMs with a passthrough GPU cannot be live-migrated. Draining a GPU node stops these VMs, and they restart on another node only if a GPU of the same class is free there. Plan GPU node maintenance with the VM owners. | ||
| - **Memory**: a VM with a passthrough device locks all of its guest memory on the host. The platform's memory overcommit therefore does not apply to these VMs. Size GPU nodes for the full memory of their VMs. |
gign0766
marked this pull request as draft
October 14, 2026 06:46
gign0766
force-pushed
the
support-gpu
branch
3 times, most recently
from
November 4, 2026 13:22
fd1ce9a to
53ccc49
Compare
Signed-off-by: Brewal HENAFF <brewal44@gmail.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add documentations for GPU support in VM