Skip to content

Toggling MIG mode fails when nvidia_drm module is loaded #181

Closed as not planned

Description

@cdesiniotis

mig-parted will fail to perform a GPU reset, and therefore toggle the MIG mode on GPUs where a reset is required,
if the nvidia_drm kernel module is loaded. Below is the error message one might encounter:

$ sudo nvidia-mig-parted apply -f /etc/nvidia-mig-manager/config-default.yaml -k /etc/nvidia-mig-manager/hooks-default.yaml -c all-balanced
ERRO[0003]
The following GPUs could not be reset:
  GPU 00000000:01:00.0: In use by another client
  GPU 00000000:47:00.0: In use by another client
  GPU 00000000:81:00.0: In use by another client
  GPU 00000000:C2:00.0: In use by another client

4 devices are currently being used by one or more other processes (e.g., Fabric Manager, CUDA application, graphics application such as an X server, or a monitoring application such as another instance of nvidia-smi). Please first kill all processes using these devices and all compute applications running in the system.
FATA[0008] Error applying MIG configuration with hooks: error resetting all GPUs: exit status 255

A workaround is to unload the nvidia_drm kernel module before applying a MIG configuration and load it after the configuration change has been applied.

$ sudo rmmod nvidia_drm
$ sudo nvidia-mig-parted apply -f /etc/nvidia-mig-manager/config-default.yaml -k /etc/nvidia-mig-manager/hooks-default.yaml -c all-balanced
MIG configuration applied successfully

Activity

  1. bergentruckung commented on Oct 14, 2025

    @bergentruckung

    I'm seeing a similar behaviour on my GPUs as well. Few questions:

    1. Are there any downsides to doing this (unload/load) multiple times?
    2. For GPUs setup for compute, is it needed to load the nvidia_drm kernel module, since that's for rendering?
  2. 5-Jeremy commented on Nov 18, 2025

    @5-Jeremy

    I found that I needed to go all the way and restart the nvidia module itself before I could change the MIG mode after encountering this error.
    (For reference, I did this by running sudo rmmod nvidia_drm, sudo rmmod nvidia_modeset, sudo rmmod nvidia_uvm, and finally sudo rmmod nvidia; then I re-loaded the modules in reverse order)

  3. added
    documentationIssue/PR focused on fixing/editing/adding documentation bits
    enhancementImprovements to existing features, performance, or usability (not bug fixes or new features).
    on Mar 3, 2026
  4. rajathagasthya commented on Apr 6, 2026

    @rajathagasthya
    Contributor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationIssue/PR focused on fixing/editing/adding documentation bitsenhancementImprovements to existing features, performance, or usability (not bug fixes or new features).

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions