Update vfio-manage to choose best VFIO driver #128
Merged
Conversation
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
Pull Request Test Coverage Report for Build 20018055700Details
💛 - Coveralls |
cdesiniotis
force-pushed
the
support-variant-vfio-modules
branch
2 times, most recently
from
fcfa6cf to
7829c7f
Compare
cdesiniotis
force-pushed
the
support-variant-vfio-modules
branch
2 times, most recently
from
ff28e1c to
b5da7d9
Compare
cdesiniotis
changed the title
cdesiniotis
force-pushed
the
support-variant-vfio-modules
branch
2 times, most recently
from
a95b741 to
ad775b1
Compare
tariq1890
reviewed
Nov 25, 2025
tariq1890
reviewed
Nov 25, 2025
cdesiniotis
force-pushed
the
support-variant-vfio-modules
branch
2 times, most recently
from
64f0f28 to
26d70dd
Compare
Rather than always binding GPUs to the vfio-pci driver, this commit
introduces logic to see if the running kernel has a VFIO variant
driver available that is a better match for the device. This is required
on Grace-based systems where the nvgrace_gpu_vfio_pci module is required
to be used in favor of the vfio-pci module.
We read the mod.alias file for a given device, then we look through
/lib/modules/${kernel_version}/modules.alias for the vfio_pci alias
that matches with the least number of wildcard ('*') fields.
The code introduced in this commit is inspired by:
https://gitlab.com/libvirt/libvirt/-/commit/82e2fac297105f554f57fb589002933231b4f711
Signed-off-by: Christopher Desiniotis <[email protected]>
Signed-off-by: Christopher Desiniotis <[email protected]>
cdesiniotis
force-pushed
the
support-variant-vfio-modules
branch
from
26d70dd to
3bafc14
Compare
karthikvetrivel
approved these changes
Dec 8, 2025
Member
karthikvetrivel
left a comment
karthikvetrivel
left a comment
There was a problem hiding this comment.
Thanks for your work on this, Chris! LGTM.
tariq1890
approved these changes
Dec 8, 2025
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.
Rather than always binding GPUs to the vfio-pci driver, this commit
introduces logic to see if the running kernel has a VFIO variant
driver available that is a better match for the device. This is required
on Grace-based systems where the nvgrace_gpu_vfio_pci module is required
to be used in favor of the vfio-pci module.
We read the mod.alias file for a given device, then we look through
/lib/modules/${kernel_version}/modules.alias for the vfio_pci alias
that matches with the least number of wildcard ('*') fields.
The code introduced in this commit is inspired by:
https://gitlab.com/libvirt/libvirt/-/commit/82e2fac297105f554f57fb589002933231b4f711
Depends on #127
Testing
On a GB200 compute tray:
On a system with one L40 (configured in graphics mode) and one L4 GPU: