🕷️ Crawler Inspector

URL Lookup

Direct Parameter Lookup

Raw Queries and Responses

1. Shard Calculation

Query:

Response:

Calculated Shard: 122 (from laksa128)

2. Crawled Status Check

Query:

curl -X POST \
  'http://laksa122.int.ahrefs:8124/' \
  -H 'Content-Type: text/plain' \
  -H 'X-ClickHouse-Database: crawler3' \
  -H 'Authorization: Basic YXBpOg==' \
  -d 'SELECT getAhrefsURLFromUnparsed(src_unparsed) AS found_url, ifNull(toUnixTimestamp(download_stamp), 0) AS crawl_time, ifNull(toUnixTimestamp(props_url_first_seen), 0) AS first_indexed_time, download_http_code AS http_code, src_unparsed AS src_unparsed, src_root_hash AS src_root_hash, history_drop_reason AS history_drop_reason, meta_title AS meta_title, meta_descriptions AS meta_descriptions, attrs_boilerpipe_text AS attrs_boilerpipe_text, attrs_markdown AS attrs_markdown, attrs_readable_markdown AS attrs_readable_markdown, meta_canonical AS meta_canonical FROM crawler3.page_info_local FINAL PREWHERE (src_root_hash, src_unparsed) IN ((getAhrefsRootHashFromUnparsed(getAhrefsUnparsedNoserviceFromURL(\'https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat\')), getAhrefsUnparsedNoserviceFromURL(\'https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat\'))) FORMAT JSONEachRow'

Response:

{"found_url":"https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat","crawl_time":1772990632,"first_indexed_time":1645547568,"http_code":200,"src_unparsed":"com,seimaxim!www,\/kb\/gpu\/nvidia-a100-mig-cheat-sheat s443","src_root_hash":"17739919741563513922","history_drop_reason":null,"meta_title":"NVIDIA A100 MIG Cheat Sheat – SeiMaxim","meta_descriptions":["MIG is only compatible with Linux distributions that support CUDA 11\/R450 or higher. It's also a good idea to use the NVIDIA Datacenter Linux driver version"],"attrs_boilerpipe_text":"MIG is only compatible with Linux distributions that support CUDA 11\/R450 or higher. It’s also a good idea to use the NVIDIA Datacenter Linux driver version 450.80.02 or higher. MIG is not supported on any Windows Pro or Server OS.\nThe new Multi-Instance GPU (MIG) functionality allows NVIDIA Ampere-based GPUs (such as the\nNVIDIA A100\n) to be securely partitioned into up to seven independent GPU Instances for CUDA applications, giving different users separate GPU resources for optimal GPU use.\nThis functionality is especially useful for workloads that do not completely utilize the GPU’s computing capabilities, and users may want to run many tasks in parallel to get the most out of their GPU.\nThe following prerequisites and software versions are highly recommended when using supported GPUs in MIG mode.\nOnly the GPUs and systems listed below are compatible with MIG.\nNVIDIA driver 450.80.02 or later is required for CUDA 11.\nLinux distributions that were supported by CUDA 11\nIf you are using Kubernetes or containers, make sure to use;\nVersion 2.5.0 or later of the NVIDIA Container Toolkit (nvidia-docker2)\nv0.7.0 or newer of the NVIDIA K8s Device Plugin\nVersion 0.2.0 or later of NVIDIA gpu-feature-discovery\nNVIDIA Management Library (NVML) APIs or the nvidia-smi command-line interface can be used to manage MIG programmatically. Some of the nvidia-smi output in the following examples may be cropped for brevity to highlight the relevant sections of interest.\nEnable or Disable MIG\nTo enable or disable MIG on all GPUs or a certain GPU, enable persistence mode on all GPUs.\nnvidia-smi -pm 1\n\nroot@server:~# nvidia-smi -pm 1\nEnabled persistence mode for GPU 00000000:31:00.0.\nEnabled persistence mode for GPU 00000000:CA:00.0.\nAll done.\nThen enable MIG by using the following command.\nroot@server:~# nvidia-smi -mig 1\nroot@server:~# nvidia-smi\nTue Feb 22 11:47:45 2022       \n+-----------------------------------------------------------------------------+\n| NVIDIA-SMI 510.39.01    Driver Version: 510.39.01    CUDA Version: 11.6     |\n|-------------------------------+----------------------+----------------------+\n| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |\n| Fan  Temp  Perf  Pwr:Usage\/Cap|         Memory-Usage | GPU-Util  Compute M. |\n|                               |                      |               MIG M. |\n|===============================+======================+======================|\n|   0  NVIDIA A100 80G...  On   | 00000000:31:00.0 Off |                   On |\n| N\/A   34C    P0    41W \/ 300W |      0MiB \/ 81920MiB |     N\/A      Default |\n|                               |                      |              Enabled |\n+-------------------------------+----------------------+----------------------+\n|   1  NVIDIA A100 80G...  On   | 00000000:CA:00.0 Off |                   On |\n| N\/A   34C    P0    43W \/ 300W |      0MiB \/ 81920MiB |     N\/A      Default |\n|                               |                      |              Enabled |\n+-------------------------------+----------------------+----------------------+\n\n+-----------------------------------------------------------------------------+\n| MIG devices:                                                                |\n+------------------+----------------------+-----------+-----------------------+\n| GPU  GI  CI  MIG |         Memory-Usage |        Vol|         Shared        |\n|      ID  ID  Dev |           BAR1-Usage | SM     Unc| CE  ENC  DEC  OFA  JPG|\n|                  |                      |        ECC|                       |\n|==================+======================+===========+=======================|\n|  No MIG devices found                                                       |\n+-----------------------------------------------------------------------------+\n\n+-----------------------------------------------------------------------------+\n| Processes:                                                                  |\n|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |\n|        ID   ID                                                   Usage      |\n|=============================================================================|\n|  No running processes found                                                 |\n+-----------------------------------------------------------------------------+\nTo disable MIG use the following command.\nnvidia-smi -mig 0\nroot@server:~# nvidia-smi -mig 0\nDisabled MIG Mode for GPU 00000000:31:00.0\nDisabled MIG Mode for GPU 00000000:CA:00.0\nAll done.\nTo enable or disable MIG on a specific device.\nnvidia-smi -i 3 -mig 1\nnvidia-smi -i 3 -mig 0\nList all GPU Instances\nroot@server:~# nvidia-smi mig -lgip\n+-----------------------------------------------------------------------------+\n| GPU instance profiles:                                                      |\n| GPU   Name             ID    Instances   Memory     P2P    SM    DEC   ENC  |\n|                              Free\/Total   GiB              CE    JPEG  OFA  |\n|=============================================================================|\n|   0  MIG 1g.10gb       19     7\/7        9.50       No     14     0     0   |\n|                                                             1     0     0   |\n+-----------------------------------------------------------------------------+\n|   0  MIG 1g.10gb+me    20     1\/1        9.50       No     14     1     0   |\n|                                                             1     1     1   |\n+-----------------------------------------------------------------------------+\n|   0  MIG 2g.20gb       14     3\/3        19.50      No     28     1     0   |\n|                                                             2     0     0   |\n+-----------------------------------------------------------------------------+\n|   0  MIG 3g.40gb        9     2\/2        39.25      No     42     2     0   |\n|                                                             3     0     0   |\n+-----------------------------------------------------------------------------+\n|   0  MIG 4g.40gb        5     1\/1        39.25      No     56     2     0   |\n|                                                             4     0     0   |\n+-----------------------------------------------------------------------------+\n|   0  MIG 7g.80gb        0     1\/1        78.75      No     98     5     0   |\n|                                                             7     1     1   |\n+-----------------------------------------------------------------------------+\n|   1  MIG 1g.10gb       19     7\/7        9.50       No     14     0     0   |\n|                                                             1     0     0   |\n+-----------------------------------------------------------------------------+\n|   1  MIG 1g.10gb+me    20     1\/1        9.50       No     14     1     0   |\n|                                                             1     1     1   |\n+-----------------------------------------------------------------------------+\n|   1  MIG 2g.20gb       14     3\/3        19.50      No     28     1     0   |\n|                                                             2     0     0   |\n+-----------------------------------------------------------------------------+\n|   1  MIG 3g.40gb        9     2\/2        39.25      No     42     2     0   |\n|                                                             3     0     0   |\n+-----------------------------------------------------------------------------+\n|   1  MIG 4g.40gb        5     1\/1        39.25      No     56     2     0   |\n|                                                             4     0     0   |\n+-----------------------------------------------------------------------------+\n|   1  MIG 7g.80gb        0     1\/1        78.75      No     98     5     0   |\n|                                                             7     1     1   |\n+-----------------------------------------------------------------------------+\nCreate GPU instances on MIG-enabled GPU\nroot@server:~# nvidia-smi mig -cgi 19,19,19,19,19,19,19 -i 3\nSuccessfully created GPU instance ID 13 on GPU  0 using profile MIG 1g.5gb (ID 19)\nSuccessfully created GPU instance ID 11 on GPU  0 using profile MIG 1g.5gb (ID 19)\nSuccessfully created GPU instance ID 12 on GPU  0 using profile MIG 1g.5gb (ID 19)\nSuccessfully created GPU instance ID  7 on GPU  0 using profile MIG 1g.5gb (ID 19)\nSuccessfully created GPU instance ID  8 on GPU  0 using profile MIG 1g.5gb (ID 19)\nSuccessfully created GPU instance ID  9 on GPU  0 using profile MIG 1g.5gb (ID 19)\nSuccessfully created GPU instance ID 10 on GPU  0 using profile MIG 1g.5gb (ID 19)\nCreate Compute instances on a MIG-enabled GPU\nroot@server:~# nvidia-smi mig -cci -i 3\nSuccessfully created compute instance ID  0 on GPU  0 GPU instance ID  7 using profile MIG 1g.5gb (ID  0)\nSuccessfully created compute instance ID  0 on GPU  0 GPU instance ID  8 using profile MIG 1g.5gb (ID  0)\nSuccessfully created compute instance ID  0 on GPU  0 GPU instance ID  9 using profile MIG 1g.5gb (ID  0)\nSuccessfully created compute instance ID  0 on GPU  0 GPU instance ID 10 using profile MIG 1g.5gb (ID  0)\nSuccessfully created compute instance ID  0 on GPU  0 GPU instance ID 11 using profile MIG 1g.5gb (ID  0)\nSuccessfully created compute instance ID  0 on GPU  0 GPU instance ID 12 using profile MIG 1g.5gb (ID  0)\nSuccessfully created compute instance ID  0 on GPU  0 GPU instance ID 13 using profile MIG 1g.5gb (ID  0)\nView MIG Instances\nroot@server:~# nvidia-smi\n\n+-----------------------------------------------------------------------------+\n| MIG devices:                                                                |\n+------------------+----------------------+-----------+-----------------------+\n| GPU  GI  CI  MIG |         Memory-Usage |        Vol|         Shared        |\n|      ID  ID  Dev |           BAR1-Usage | SM     Unc| CE  ENC  DEC  OFA  JPG|\n|                  |                      |        ECC|                       |\n|==================+======================+===========+=======================|\n|  0    7   0   0  |      1MiB \/  4864MiB | 14      0 |  1   0    0    0    0 |\n|                  |      0MiB \/  8191MiB |           |                       |\n+------------------+----------------------+-----------+-----------------------+\n|  0    8   0   1  |      1MiB \/  4864MiB | 14      0 |  1   0    0    0    0 |\n|                  |      0MiB \/  8191MiB |           |                       |\n+------------------+----------------------+-----------+-----------------------+\n|  0    9   0   2  |      1MiB \/  4864MiB | 14      0 |  1   0    0    0    0 |\n|                  |      0MiB \/  8191MiB |           |                       |\n+------------------+----------------------+-----------+-----------------------+\n|  0   10   0   3  |      1MiB \/  4864MiB | 14      0 |  1   0    0    0    0 |\n|                  |      0MiB \/  8191MiB |           |                       |\n+------------------+----------------------+-----------+-----------------------+\n|  0   11   0   4  |      1MiB \/  4864MiB | 14      0 |  1   0    0    0    0 |\n|                  |      0MiB \/  8191MiB |           |                       |\n+------------------+----------------------+-----------+-----------------------+\n|  0   12   0   5  |      1MiB \/  4864MiB | 14      0 |  1   0    0    0    0 |\n|                  |      0MiB \/  8191MiB |           |                       |\n+------------------+----------------------+-----------+-----------------------+\n|  0   13   0   6  |      1MiB \/  4864MiB | 14      0 |  1   0    0    0    0 |\n|                  |      0MiB \/  8191MiB |           |                       |\n+------------------+----------------------+-----------+-----------------------+\nroot@server:~# nvidia-smi -L\nGPU 0: A100-PCIE-40GB (UUID: GPU-0069414c-9f30-41f9-d5d8-87890423f0c4)\n  MIG 1g.5gb Device 0: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4\/7\/0)\n  MIG 1g.5gb Device 1: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4\/8\/0)\n  MIG 1g.5gb Device 2: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4\/9\/0)\n  MIG 1g.5gb Device 3: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4\/10\/0)\n  MIG 1g.5gb Device 4: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4\/11\/0)\n  MIG 1g.5gb Device 5: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4\/12\/0)\n  MIG 1g.5gb Device 6: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4\/13\/0)\nList GPU Instances\nroot@server:~# nvidia mig -lgi\nList Compute Instances\nroot@server:~# nvidia mig -lci\n\n+-------------------------------------------------------+\n| Compute instances:                                    |\n| GPU     GPU       Name             Profile   Instance |\n|       Instance                       ID        ID     |\n|         ID                                            |\n|=======================================================|\n|   0      7       MIG 1g.5gb           0         0     |\n+-------------------------------------------------------+\n|   0      8       MIG 1g.5gb           0         0     |\n+-------------------------------------------------------+\n|   0      9       MIG 1g.5gb           0         0     |\n+-------------------------------------------------------+\n|   0     11       MIG 1g.5gb           0         0     |\n+-------------------------------------------------------+\n|   0     12       MIG 1g.5gb           0         0     |\n+-------------------------------------------------------+\n|   0     13       MIG 1g.5gb           0         0     |\n+-------------------------------------------------------+\n|   0     14       MIG 1g.5gb           0         0     |\n+-------------------------------------------------------+\nDestroy Compute Instances\nroot@server:~# nvidia-smi mig -dci -i 3\nSuccessfully destroyed compute instance ID  0 from GPU  0 GPU instance ID  7\nSuccessfully destroyed compute instance ID  0 from GPU  0 GPU instance ID  8\nSuccessfully destroyed compute instance ID  0 from GPU  0 GPU instance ID  9\nSuccessfully destroyed compute instance ID  0 from GPU  0 GPU instance ID 10\nSuccessfully destroyed compute instance ID  0 from GPU  0 GPU instance ID 11\nSuccessfully destroyed compute instance ID  0 from GPU  0 GPU instance ID 12\nSuccessfully destroyed compute instance ID  0 from GPU  0 GPU instance ID 13\nDestroy GPU Instances\nroot@server:~# nvidia-smi mig -dgi -i 3\nSuccessfully destroyed GPU instance ID  7 from GPU  0\nSuccessfully destroyed GPU instance ID  8 from GPU  0\nSuccessfully destroyed GPU instance ID  9 from GPU  0\nSuccessfully destroyed GPU instance ID 10 from GPU  0\nSuccessfully destroyed GPU instance ID 11 from GPU  0\nSuccessfully destroyed GPU instance ID 12 from GPU  0\nSuccessfully destroyed GPU instance ID 13 from GPU  0\nGetting MIG Help\nroot@server:~# nvidia-smi mig -h\n\n    mig -- Multi Instance GPU management.\n\n    Usage: nvidia-smi mig [options]\n\n    Options include:\n    [-h | --help]: Display help information.\n    [-i | --id]: Enumeration index, PCI bus ID or UUID.\n                 Provide comma separated values for more than one device.\n    [-gi | --gpu-instance-id]: GPU instance ID.\n                               Provide comma separated values for more than one GPU instance.\n    [-ci | --compute-instance-id]: Compute instance ID.\n                                   Provide comma separated values for more than one compute \n                                   instance.\n    [-lgip | --list-gpu-instance-profiles]: List supported GPU instance profiles.\n                                            Option -i can be used to restrict the command to\n                                            run on a specific GPU.\n    [-lgipp | --list-gpu-instance-possible-placements]: List possible GPU instance placements\n                                                        in the following format, {Start}:Size.\n                                                        Option -i can be used to restrict the\n                                                        command to run on a specific GPU.\n    [-C | --default-compute-instance]: Create compute instance with the default profile when used\n                                       with the option to create a GPU instance (-cgi).\n    [-cgi | --create-gpu-instance]: Create GPU instances for the given profile tuples. A profile\n                                    tuple consists of a profile name or ID and an optional placement\n                                    specifier, which consists of a colon and a placement start index.\n                                    Provide comma separated values for more than one profile tuple.\n                                    Option -i can be used to restrict the command to run on\n                                    a specific GPU.\n    [-dgi | --destroy-gpu-instance]: Destroy GPU instances.\n                                     Options -i and -gi can be used individually or combined\n                                     to restrict the command to run on a specific GPU or GPU\n                                     instance.\n    [-lgi | --list-gpu-instances]: List GPU instances.\n                                   Option -i can be used to restrict the command to run on a\n                                   specific GPU.\n    [-lcip | --list-compute-instance-profiles]: List supported compute instance profiles.\n                                                Options -i and -gi can be used individually or\n                                                combined to restrict the command to run on a\n                                                specific GPU or GPU instance.\n    [-cci | --create-compute-instance]: Create compute instance for the given profile name or IDs.\n                                        Provide comma separated values for more than one profile.\n                                        If no profile name or ID is given, then the default*\n                                        compute instance profile ID will be used. Options -i and\n                                        -gi can be used individually or combined to restrict the\n                                        command to run on a specific GPU or GPU instance.\n    [-dci | --destroy-compute-instance]: Destroy compute instances.\n                                         Options -i, -gi and -ci can be used individually or\n                                         combined to restrict the command to run on a specific\n                                         GPU or GPU instance or compute instance.\n    [-lci | --list-compute-instances]: List compute instances.\n                                       Options -i and -gi can be used individually or combined\n                                       to restrict the command to run on a specific GPU or GPU\n                                       instance.","attrs_markdown":"[Skip to content](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat#site-content)\n\n# [seimaxim](https:\/\/www.seimaxim.com\/)\nMenu\n\n[![dashboard](https:\/\/www.seimaxim.com\/wp-content\/uploads\/2025\/11\/dashboard-seimaxim-1.webp)](https:\/\/app.seimaxim.com\/login)\n\n[![SeiMaxim Logo](https:\/\/www.seimaxim.com\/wp-content\/uploads\/2020\/12\/logo-2.svg)](https:\/\/www.seimaxim.com\/)\n\n- [![SeiMaxim Logo](https:\/\/www.seimaxim.com\/wp-content\/uploads\/2020\/12\/logo-2.svg)](https:\/\/www.seimaxim.com\/)\n- [Server](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat)\n  - [Dedicated Servers](https:\/\/www.seimaxim.com\/dedicated-servers)\n    - Deploy dedicated servers in 10 regions globally at unbeatable prices.\n    - ![datacenter](data:image\/svg+xml,%3Csvg%20xmlns='http:\/\/www.w3.org\/2000\/svg'%20width='300'%20height='157'%20viewBox='0%200%20300%20157'%3E%3C\/svg%3E)\n    - [Buy now](https:\/\/www.seimaxim.com\/dedicated-servers)\n  - [GPU Dedicated Servers](https:\/\/www.seimaxim.com\/dedicated-servers\/gpu)\n    - Dedicated GPU servers with nVIDIA A4, NVIDIA A100 80GB, and RTX A6000 are available.\n    - ![nvidia rtx a6000](data:image\/svg+xml,%3Csvg%20xmlns='http:\/\/www.w3.org\/2000\/svg'%20width='300'%20height='157'%20viewBox='0%200%20300%20157'%3E%3C\/svg%3E)\n    - [Buy now](https:\/\/www.seimaxim.com\/dedicated-servers\/gpu)\n  - [Game Dedicated Servers](https:\/\/www.seimaxim.com\/dedicated-servers\/game)\n    - Deliver a seamless multiplayer gaming experience to your players around the world.\n    - ![gaming servers](data:image\/svg+xml,%3Csvg%20xmlns='http:\/\/www.w3.org\/2000\/svg'%20width='300'%20height='157'%20viewBox='0%200%20300%20157'%3E%3C\/svg%3E)\n    - [Buy now](https:\/\/www.seimaxim.com\/dedicated-servers\/game)\n  - [AMD Ryzen Servers](https:\/\/www.seimaxim.com\/dedicated-servers\/amd-ryzen)\n    - Efficiently crunch numerical data, play the latest games, and create the most complex design.\n    - ![amd ryzen server](data:image\/svg+xml,%3Csvg%20xmlns='http:\/\/www.w3.org\/2000\/svg'%20width='300'%20height='157'%20viewBox='0%200%20300%20157'%3E%3C\/svg%3E)\n    - [Buy now](https:\/\/www.seimaxim.com\/dedicated-servers\/amd-ryzen)\n  - [Managed Services](https:\/\/www.seimaxim.com\/services)\n    - Managed server services and secure data migration. Total security for your mission-critical workloads.\n    - ![managed server](data:image\/svg+xml,%3Csvg%20xmlns='http:\/\/www.w3.org\/2000\/svg'%20width='300'%20height='157'%20viewBox='0%200%20300%20157'%3E%3C\/svg%3E)\n    - [Buy now](https:\/\/www.seimaxim.com\/services)\n  - [Server Setup Services](https:\/\/www.seimaxim.com\/platform-services)\n    - Our experts are ready to work on your server hardware and software setup operations from scratch.\n    - ![server setup datacenter](data:image\/svg+xml,%3Csvg%20xmlns='http:\/\/www.w3.org\/2000\/svg'%20width='300'%20height='157'%20viewBox='0%200%20300%20157'%3E%3C\/svg%3E)\n    - [Buy now](https:\/\/www.seimaxim.com\/platform-services)\n  - [Colocation](https:\/\/www.seimaxim.com\/colocation)\n    - Reduce failure risk by choosing SeiMaxim data center colocation.\n    - ![colocation](data:image\/svg+xml,%3Csvg%20xmlns='http:\/\/www.w3.org\/2000\/svg'%20width='300'%20height='157'%20viewBox='0%200%20300%20157'%3E%3C\/svg%3E)\n    - [Buy now](https:\/\/www.seimaxim.com\/colocation)\n- [Hosting](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat)\n  - [Shared Hosting](https:\/\/www.seimaxim.com\/shared-hosting)\n  - [WordPress Hosting](https:\/\/www.seimaxim.com\/shared-hosting\/wordpress)\n  - [Django Hosting](https:\/\/www.seimaxim.com\/django-hosting)\n  - [Drupal Hosting](https:\/\/www.seimaxim.com\/drupal-hosting)\n- [Domains](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat)\n  - [Domain Names](https:\/\/www.seimaxim.com\/domain-names)\n  - [Domain Transfer](https:\/\/www.seimaxim.com\/domain-names\/transfer)\n  - [Domain Privacy](https:\/\/www.seimaxim.com\/domain-names\/privacy)\n  - [WHOIS Lookup](https:\/\/www.seimaxim.com\/domain-names\/whois)\n- [VPS](https:\/\/www.seimaxim.com\/vps-hosting)\n- [Solutions](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat)\n  - [By Industry](https:\/\/www.seimaxim.com\/solutions)\n  - [E-Commerce](https:\/\/www.seimaxim.com\/solutions\/e-commerce)\n  - [Gaming](https:\/\/www.seimaxim.com\/solutions\/gaming)\n  - [Big Data](https:\/\/www.seimaxim.com\/solutions\/big-data)\n  - [iGaming](https:\/\/www.seimaxim.com\/solutions\/igaming)\n  - [AdTech & MarTech](https:\/\/www.seimaxim.com\/solutions\/adtech-martech)\n  - [DevOps](https:\/\/www.seimaxim.com\/solutions\/devops)\n  - [High Performance Computing](https:\/\/www.seimaxim.com\/solutions\/hpc)\n  - [SaaS](https:\/\/www.seimaxim.com\/solutions\/saas)\n- [Legal](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat)\n  - [Terms and conditions](https:\/\/www.seimaxim.com\/terms)\n  - [Privacy Policy](https:\/\/www.seimaxim.com\/terms\/privacy)\n  - [Accepted Use Policy](https:\/\/www.seimaxim.com\/terms\/aup)\n  - [Refund Policy](https:\/\/www.seimaxim.com\/terms\/refund)\n  - [Abuse prevention](https:\/\/www.seimaxim.com\/terms\/abuse)\n  - [GDPR](https:\/\/www.seimaxim.com\/terms\/gdpr)\n  - [SLA](https:\/\/www.seimaxim.com\/terms\/sla)\n  - [DMCA](https:\/\/www.seimaxim.com\/terms\/dmca)\n  - [Customer verification](https:\/\/www.seimaxim.com\/terms\/customer-verification)\n  - [Customer Commitment](https:\/\/www.seimaxim.com\/about\/customer-commitment)\n  - [About Us](https:\/\/www.seimaxim.com\/about)\n  - [Contact Us](https:\/\/www.seimaxim.com\/contact)\n- [Dashboard](https:\/\/app.seimaxim.com\/login)\n\nTable of Contents\n\n- [Enable or Disable MIG](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat)\n- [List all GPU Instances](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat)\n- [Create GPU instances on MIG-enabled GPU](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat)\n- [Create Compute instances on a MIG-enabled GPU](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat)\n- [View MIG Instances](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat)\n- [List GPU Instances](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat)\n- [List Compute Instances](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat)\n- [Destroy Compute Instances](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat)\n- [Destroy GPU Instances](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat)\n- [Getting MIG Help](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat)\n\n# NVIDIA A100 MIG Cheat Sheat\n[![](data:image\/svg+xml,%3Csvg%20xmlns='http:\/\/www.w3.org\/2000\/svg'%20width='96'%20height='96'%20viewBox='0%200%2096%2096'%3E%3C\/svg%3E)](https:\/\/www.seimaxim.com\/author\/albert)\n\nby [Albert](https:\/\/www.seimaxim.com\/author\/albert)\n\nFebruary 22, 2022\n\n![mig](https:\/\/www.seimaxim.com\/wp-content\/uploads\/2022\/02\/mig-300x87.png)\n\nMIG is only compatible with Linux distributions that support CUDA 11\/R450 or higher. It’s also a good idea to use the NVIDIA Datacenter Linux driver version 450.80.02 or higher. MIG is not supported on any Windows Pro or Server OS.\n\nThe new Multi-Instance GPU (MIG) functionality allows NVIDIA Ampere-based GPUs (such as the [NVIDIA A100](https:\/\/www.seimaxim.com\/dedicated-servers\/gpu)) to be securely partitioned into up to seven independent GPU Instances for CUDA applications, giving different users separate GPU resources for optimal GPU use.\n\nThis functionality is especially useful for workloads that do not completely utilize the GPU’s computing capabilities, and users may want to run many tasks in parallel to get the most out of their GPU.\n\nThe following prerequisites and software versions are highly recommended when using supported GPUs in MIG mode.\n\nOnly the GPUs and systems listed below are compatible with MIG.\n\n- NVIDIA driver 450.80.02 or later is required for CUDA 11.\n- Linux distributions that were supported by CUDA 11\n\nIf you are using Kubernetes or containers, make sure to use;\n\n- Version 2.5.0 or later of the NVIDIA Container Toolkit (nvidia-docker2)\n- v0.7.0 or newer of the NVIDIA K8s Device Plugin\n- Version 0.2.0 or later of NVIDIA gpu-feature-discovery\n\nNVIDIA Management Library (NVML) APIs or the nvidia-smi command-line interface can be used to manage MIG programmatically. Some of the nvidia-smi output in the following examples may be cropped for brevity to highlight the relevant sections of interest.\n\n## Enable or Disable MIG\nTo enable or disable MIG on all GPUs or a certain GPU, enable persistence mode on all GPUs.\n```\nnvidia-smi -pm 1\n\nroot@server:~# nvidia-smi -pm 1\nEnabled persistence mode for GPU 00000000:31:00.0.\nEnabled persistence mode for GPU 00000000:CA:00.0.\nAll done.\n```\nThen enable MIG by using the following command.\n\n`root@server:~# nvidia-smi -mig 1`\n```\nroot@server:~# nvidia-smi\nTue Feb 22 11:47:45 2022       \n+-----------------------------------------------------------------------------+\n| NVIDIA-SMI 510.39.01    Driver Version: 510.39.01    CUDA Version: 11.6     |\n|-------------------------------+----------------------+----------------------+\n| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |\n| Fan  Temp  Perf  Pwr:Usage\/Cap|         Memory-Usage | GPU-Util  Compute M. |\n|                               |                      |               MIG M. |\n|===============================+======================+======================|\n|   0  NVIDIA A100 80G...  On   | 00000000:31:00.0 Off |                   On |\n| N\/A   34C    P0    41W \/ 300W |      0MiB \/ 81920MiB |     N\/A      Default |\n|                               |                      |              Enabled |\n+-------------------------------+----------------------+----------------------+\n|   1  NVIDIA A100 80G...  On   | 00000000:CA:00.0 Off |                   On |\n| N\/A   34C    P0    43W \/ 300W |      0MiB \/ 81920MiB |     N\/A      Default |\n|                               |                      |              Enabled |\n+-------------------------------+----------------------+----------------------+\n\n+-----------------------------------------------------------------------------+\n| MIG devices:                                                                |\n+------------------+----------------------+-----------+-----------------------+\n| GPU  GI  CI  MIG |         Memory-Usage |        Vol|         Shared        |\n|      ID  ID  Dev |           BAR1-Usage | SM     Unc| CE  ENC  DEC  OFA  JPG|\n|                  |                      |        ECC|                       |\n|==================+======================+===========+=======================|\n|  No MIG devices found                                                       |\n+-----------------------------------------------------------------------------+\n\n+-----------------------------------------------------------------------------+\n| Processes:                                                                  |\n|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |\n|        ID   ID                                                   Usage      |\n|=============================================================================|\n|  No running processes found                                                 |\n+-----------------------------------------------------------------------------+\n```\nTo disable MIG use the following command.\n\n`nvidia-smi -mig 0`\n```\nroot@server:~# nvidia-smi -mig 0\nDisabled MIG Mode for GPU 00000000:31:00.0\nDisabled MIG Mode for GPU 00000000:CA:00.0\nAll done.\n```\nTo enable or disable MIG on a specific device.\n\n## List all GPU Instances\n```\nroot@server:~# nvidia-smi mig -lgip\n+-----------------------------------------------------------------------------+\n| GPU instance profiles:                                                      |\n| GPU   Name             ID    Instances   Memory     P2P    SM    DEC   ENC  |\n|                              Free\/Total   GiB              CE    JPEG  OFA  |\n|=============================================================================|\n|   0  MIG 1g.10gb       19     7\/7        9.50       No     14     0     0   |\n|                                                             1     0     0   |\n+-----------------------------------------------------------------------------+\n|   0  MIG 1g.10gb+me    20     1\/1        9.50       No     14     1     0   |\n|                                                             1     1     1   |\n+-----------------------------------------------------------------------------+\n|   0  MIG 2g.20gb       14     3\/3        19.50      No     28     1     0   |\n|                                                             2     0     0   |\n+-----------------------------------------------------------------------------+\n|   0  MIG 3g.40gb        9     2\/2        39.25      No     42     2     0   |\n|                                                             3     0     0   |\n+-----------------------------------------------------------------------------+\n|   0  MIG 4g.40gb        5     1\/1        39.25      No     56     2     0   |\n|                                                             4     0     0   |\n+-----------------------------------------------------------------------------+\n|   0  MIG 7g.80gb        0     1\/1        78.75      No     98     5     0   |\n|                                                             7     1     1   |\n+-----------------------------------------------------------------------------+\n|   1  MIG 1g.10gb       19     7\/7        9.50       No     14     0     0   |\n|                                                             1     0     0   |\n+-----------------------------------------------------------------------------+\n|   1  MIG 1g.10gb+me    20     1\/1        9.50       No     14     1     0   |\n|                                                             1     1     1   |\n+-----------------------------------------------------------------------------+\n|   1  MIG 2g.20gb       14     3\/3        19.50      No     28     1     0   |\n|                                                             2     0     0   |\n+-----------------------------------------------------------------------------+\n|   1  MIG 3g.40gb        9     2\/2        39.25      No     42     2     0   |\n|                                                             3     0     0   |\n+-----------------------------------------------------------------------------+\n|   1  MIG 4g.40gb        5     1\/1        39.25      No     56     2     0   |\n|                                                             4     0     0   |\n+-----------------------------------------------------------------------------+\n|   1  MIG 7g.80gb        0     1\/1        78.75      No     98     5     0   |\n|                                                             7     1     1   |\n+-----------------------------------------------------------------------------+\n```\n## Create GPU instances on MIG-enabled GPU\n```\nroot@server:~# nvidia-smi mig -cgi 19,19,19,19,19,19,19 -i 3\nSuccessfully created GPU instance ID 13 on GPU  0 using profile MIG 1g.5gb (ID 19)\nSuccessfully created GPU instance ID 11 on GPU  0 using profile MIG 1g.5gb (ID 19)\nSuccessfully created GPU instance ID 12 on GPU  0 using profile MIG 1g.5gb (ID 19)\nSuccessfully created GPU instance ID  7 on GPU  0 using profile MIG 1g.5gb (ID 19)\nSuccessfully created GPU instance ID  8 on GPU  0 using profile MIG 1g.5gb (ID 19)\nSuccessfully created GPU instance ID  9 on GPU  0 using profile MIG 1g.5gb (ID 19)\nSuccessfully created GPU instance ID 10 on GPU  0 using profile MIG 1g.5gb (ID 19)\n```\n## Create Compute instances on a MIG-enabled GPU\n```\nroot@server:~# nvidia-smi mig -cci -i 3\nSuccessfully created compute instance ID  0 on GPU  0 GPU instance ID  7 using profile MIG 1g.5gb (ID  0)\nSuccessfully created compute instance ID  0 on GPU  0 GPU instance ID  8 using profile MIG 1g.5gb (ID  0)\nSuccessfully created compute instance ID  0 on GPU  0 GPU instance ID  9 using profile MIG 1g.5gb (ID  0)\nSuccessfully created compute instance ID  0 on GPU  0 GPU instance ID 10 using profile MIG 1g.5gb (ID  0)\nSuccessfully created compute instance ID  0 on GPU  0 GPU instance ID 11 using profile MIG 1g.5gb (ID  0)\nSuccessfully created compute instance ID  0 on GPU  0 GPU instance ID 12 using profile MIG 1g.5gb (ID  0)\nSuccessfully created compute instance ID  0 on GPU  0 GPU instance ID 13 using profile MIG 1g.5gb (ID  0)\n```\n## View MIG Instances\n```\nroot@server:~# nvidia-smi\n\n+-----------------------------------------------------------------------------+\n| MIG devices:                                                                |\n+------------------+----------------------+-----------+-----------------------+\n| GPU  GI  CI  MIG |         Memory-Usage |        Vol|         Shared        |\n|      ID  ID  Dev |           BAR1-Usage | SM     Unc| CE  ENC  DEC  OFA  JPG|\n|                  |                      |        ECC|                       |\n|==================+======================+===========+=======================|\n|  0    7   0   0  |      1MiB \/  4864MiB | 14      0 |  1   0    0    0    0 |\n|                  |      0MiB \/  8191MiB |           |                       |\n+------------------+----------------------+-----------+-----------------------+\n|  0    8   0   1  |      1MiB \/  4864MiB | 14      0 |  1   0    0    0    0 |\n|                  |      0MiB \/  8191MiB |           |                       |\n+------------------+----------------------+-----------+-----------------------+\n|  0    9   0   2  |      1MiB \/  4864MiB | 14      0 |  1   0    0    0    0 |\n|                  |      0MiB \/  8191MiB |           |                       |\n+------------------+----------------------+-----------+-----------------------+\n|  0   10   0   3  |      1MiB \/  4864MiB | 14      0 |  1   0    0    0    0 |\n|                  |      0MiB \/  8191MiB |           |                       |\n+------------------+----------------------+-----------+-----------------------+\n|  0   11   0   4  |      1MiB \/  4864MiB | 14      0 |  1   0    0    0    0 |\n|                  |      0MiB \/  8191MiB |           |                       |\n+------------------+----------------------+-----------+-----------------------+\n|  0   12   0   5  |      1MiB \/  4864MiB | 14      0 |  1   0    0    0    0 |\n|                  |      0MiB \/  8191MiB |           |                       |\n+------------------+----------------------+-----------+-----------------------+\n|  0   13   0   6  |      1MiB \/  4864MiB | 14      0 |  1   0    0    0    0 |\n|                  |      0MiB \/  8191MiB |           |                       |\n+------------------+----------------------+-----------+-----------------------+\n```\n```\nroot@server:~# nvidia-smi -L\nGPU 0: A100-PCIE-40GB (UUID: GPU-0069414c-9f30-41f9-d5d8-87890423f0c4)\n  MIG 1g.5gb Device 0: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4\/7\/0)\n  MIG 1g.5gb Device 1: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4\/8\/0)\n  MIG 1g.5gb Device 2: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4\/9\/0)\n  MIG 1g.5gb Device 3: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4\/10\/0)\n  MIG 1g.5gb Device 4: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4\/11\/0)\n  MIG 1g.5gb Device 5: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4\/12\/0)\n  MIG 1g.5gb Device 6: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4\/13\/0)\n```\n## List GPU Instances\n`root@server:~# nvidia mig -lgi`\n\n## List Compute Instances\n```\nroot@server:~# nvidia mig -lci\n\n+-------------------------------------------------------+\n| Compute instances:                                    |\n| GPU     GPU       Name             Profile   Instance |\n|       Instance                       ID        ID     |\n|         ID                                            |\n|=======================================================|\n|   0      7       MIG 1g.5gb           0         0     |\n+-------------------------------------------------------+\n|   0      8       MIG 1g.5gb           0         0     |\n+-------------------------------------------------------+\n|   0      9       MIG 1g.5gb           0         0     |\n+-------------------------------------------------------+\n|   0     11       MIG 1g.5gb           0         0     |\n+-------------------------------------------------------+\n|   0     12       MIG 1g.5gb           0         0     |\n+-------------------------------------------------------+\n|   0     13       MIG 1g.5gb           0         0     |\n+-------------------------------------------------------+\n|   0     14       MIG 1g.5gb           0         0     |\n+-------------------------------------------------------+\n```\n## Destroy Compute Instances\n```\nroot@server:~# nvidia-smi mig -dci -i 3\nSuccessfully destroyed compute instance ID  0 from GPU  0 GPU instance ID  7\nSuccessfully destroyed compute instance ID  0 from GPU  0 GPU instance ID  8\nSuccessfully destroyed compute instance ID  0 from GPU  0 GPU instance ID  9\nSuccessfully destroyed compute instance ID  0 from GPU  0 GPU instance ID 10\nSuccessfully destroyed compute instance ID  0 from GPU  0 GPU instance ID 11\nSuccessfully destroyed compute instance ID  0 from GPU  0 GPU instance ID 12\nSuccessfully destroyed compute instance ID  0 from GPU  0 GPU instance ID 13\n```\n## Destroy GPU Instances\n```\nroot@server:~# nvidia-smi mig -dgi -i 3\nSuccessfully destroyed GPU instance ID  7 from GPU  0\nSuccessfully destroyed GPU instance ID  8 from GPU  0\nSuccessfully destroyed GPU instance ID  9 from GPU  0\nSuccessfully destroyed GPU instance ID 10 from GPU  0\nSuccessfully destroyed GPU instance ID 11 from GPU  0\nSuccessfully destroyed GPU instance ID 12 from GPU  0\nSuccessfully destroyed GPU instance ID 13 from GPU  0\n```\n## Getting MIG Help\n```\nroot@server:~# nvidia-smi mig -h\n\n    mig -- Multi Instance GPU management.\n\n    Usage: nvidia-smi mig [options]\n\n    Options include:\n    [-h | --help]: Display help information.\n    [-i | --id]: Enumeration index, PCI bus ID or UUID.\n                 Provide comma separated values for more than one device.\n    [-gi | --gpu-instance-id]: GPU instance ID.\n                               Provide comma separated values for more than one GPU instance.\n    [-ci | --compute-instance-id]: Compute instance ID.\n                                   Provide comma separated values for more than one compute \n                                   instance.\n    [-lgip | --list-gpu-instance-profiles]: List supported GPU instance profiles.\n                                            Option -i can be used to restrict the command to\n                                            run on a specific GPU.\n    [-lgipp | --list-gpu-instance-possible-placements]: List possible GPU instance placements\n                                                        in the following format, {Start}:Size.\n                                                        Option -i can be used to restrict the\n                                                        command to run on a specific GPU.\n    [-C | --default-compute-instance]: Create compute instance with the default profile when used\n                                       with the option to create a GPU instance (-cgi).\n    [-cgi | --create-gpu-instance]: Create GPU instances for the given profile tuples. A profile\n                                    tuple consists of a profile name or ID and an optional placement\n                                    specifier, which consists of a colon and a placement start index.\n                                    Provide comma separated values for more than one profile tuple.\n                                    Option -i can be used to restrict the command to run on\n                                    a specific GPU.\n    [-dgi | --destroy-gpu-instance]: Destroy GPU instances.\n                                     Options -i and -gi can be used individually or combined\n                                     to restrict the command to run on a specific GPU or GPU\n                                     instance.\n    [-lgi | --list-gpu-instances]: List GPU instances.\n                                   Option -i can be used to restrict the command to run on a\n                                   specific GPU.\n    [-lcip | --list-compute-instance-profiles]: List supported compute instance profiles.\n                                                Options -i and -gi can be used individually or\n                                                combined to restrict the command to run on a\n                                                specific GPU or GPU instance.\n    [-cci | --create-compute-instance]: Create compute instance for the given profile name or IDs.\n                                        Provide comma separated values for more than one profile.\n                                        If no profile name or ID is given, then the default*\n                                        compute instance profile ID will be used. Options -i and\n                                        -gi can be used individually or combined to restrict the\n                                        command to run on a specific GPU or GPU instance.\n    [-dci | --destroy-compute-instance]: Destroy compute instances.\n                                         Options -i, -gi and -ci can be used individually or\n                                         combined to restrict the command to run on a specific\n                                         GPU or GPU instance or compute instance.\n    [-lci | --list-compute-instances]: List compute instances.\n                                       Options -i and -gi can be used individually or combined\n                                       to restrict the command to run on a specific GPU or GPU\n                                       instance.\n```\n\n- [Articles, How-To, Troubleshooting, and News about GPU](https:\/\/www.seimaxim.com\/kb\/gpu)\n\nPost navigation\n\n[Front End Developer Interview Questions & Answers](https:\/\/www.seimaxim.com\/kb\/front-end-developer-interview-questions-answers)\n\n[![a100 gpu namd simulation](https:\/\/www.seimaxim.com\/wp-content\/uploads\/2022\/02\/3d-patchwork-quilt-featured.jpg)](https:\/\/www.seimaxim.com\/kb\/gpu\/namd-v3-and-nvidia-a100-gpus-can-deliver-up-to-9x-the-throughput)\n\n[NAMD v3 and NVIDIA A100 GPUs can deliver up to 9X the throughput](https:\/\/www.seimaxim.com\/kb\/gpu\/namd-v3-and-nvidia-a100-gpus-can-deliver-up-to-9x-the-throughput)\n\n### 3 comments\n1. ![](data:image\/svg+xml,%3Csvg%20xmlns='http:\/\/www.w3.org\/2000\/svg'%20width='38'%20height='38'%20viewBox='0%200%2038%2038'%3E%3C\/svg%3E)\n   \n   [April 5, 2022 at 11:55 am](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat#comment-646)\n   \n   Rahul\n   \n   says:\n   \n   Do you also have cheatsheet on how MIG works in ESXi..  \n    I am having hard time in making it work on ESXi,  \n    I see VMs doesn’t power on post attaching vGPU GRID profile to it\n   \n   [Log in to Reply](https:\/\/www.seimaxim.com\/wp-login.php?redirect_to=https%3A%2F%2Fwww.seimaxim.com%2Fkb%2Fgpu%2Fnvidia-a100-mig-cheat-sheat)\n   - ![](data:image\/svg+xml,%3Csvg%20xmlns='http:\/\/www.w3.org\/2000\/svg'%20width='38'%20height='38'%20viewBox='0%200%2038%2038'%3E%3C\/svg%3E)\n     \n     [April 5, 2022 at 8:30 pm](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat#comment-647)\n     \n     [admin](https:\/\/www.seimaxim.com\/)\n     \n     says:\n     \n     Hi, Have you installed GRID software in ESXi. Make sure you have Linux based OS like Ubuntu in VM. MIG is not supported in Windows. MIG also need to be enabled in GPU card like A100.\n     \n     [Log in to Reply](https:\/\/www.seimaxim.com\/wp-login.php?redirect_to=https%3A%2F%2Fwww.seimaxim.com%2Fkb%2Fgpu%2Fnvidia-a100-mig-cheat-sheat)\n   - ![](data:image\/svg+xml,%3Csvg%20xmlns='http:\/\/www.w3.org\/2000\/svg'%20width='38'%20height='38'%20viewBox='0%200%2038%2038'%3E%3C\/svg%3E)\n     \n     [April 5, 2022 at 8:33 pm](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat#comment-648)\n     \n     [admin](https:\/\/www.seimaxim.com\/)\n     \n     says:\n     \n     Hi, Secondly MIG cannot be enabled or configured in ESXi. Just enabled MIG compatible GPU and attach it to VM. MIG is enabled in VM using nvidia-smi. Also make sure NVIDIA license is installed in ESXi for using GPU.\n     \n     [Log in to Reply](https:\/\/www.seimaxim.com\/wp-login.php?redirect_to=https%3A%2F%2Fwww.seimaxim.com%2Fkb%2Fgpu%2Fnvidia-a100-mig-cheat-sheat)\n\n### Leave a Reply [Cancel reply](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat#respond)\nYou must be [logged in](https:\/\/www.seimaxim.com\/wp-login.php?redirect_to=https%3A%2F%2Fwww.seimaxim.com%2Fkb%2Fgpu%2Fnvidia-a100-mig-cheat-sheat) to post a comment.\n\n###### Recent Posts\n- [GPU-Accelerated Data Analytics: Best Practices](https:\/\/www.seimaxim.com\/kb\/dedicated-servers\/gpu-accelerated-data-analytics-best-practices) March 26, 2025\n- [GPU Server powered VR: The Future of Simulation](https:\/\/www.seimaxim.com\/kb\/dedicated-servers\/gpu-server-powered-vr-the-future-of-simulation) March 23, 2025\n- [GPU-accelerated Autonomous Driving: Enabling Self-Driving](https:\/\/www.seimaxim.com\/ai\/gpu-accelerated-autonomous-driving-enabling-self-driving) March 14, 2025\n- [Accelerated Cloud Computing using GPUs](https:\/\/www.seimaxim.com\/technology\/accelerated-cloud-computing-using-gpus) March 7, 2025\n- [GPU-Powered Deep-learning applications](https:\/\/www.seimaxim.com\/deep-learning\/gpu-powered-deep-learning-applications) March 2, 2025\n\n###### PRODUCTS\n- [Dedicated Servers](https:\/\/www.seimaxim.com\/dedicated-servers)\n- [Shared Hosting](https:\/\/www.seimaxim.com\/shared-hosting)\n- [Domain Names](https:\/\/www.seimaxim.com\/domain-names)\n- [VPS Hosting](https:\/\/www.seimaxim.com\/vps-hosting)\n- [Proxies](https:\/\/www.seimaxim.com\/?page_id=1987)\n- [Managed Services](https:\/\/www.seimaxim.com\/services)\n- [Server Setup Services](https:\/\/www.seimaxim.com\/platform-services)\n\n![twitter](data:image\/svg+xml,%3Csvg%20xmlns='http:\/\/www.w3.org\/2000\/svg'%20width='25'%20height='25'%20viewBox='0%200%2025%2025'%3E%3C\/svg%3E)  [![twitter](data:image\/svg+xml,%3Csvg%20xmlns='http:\/\/www.w3.org\/2000\/svg'%20width='25'%20height='25'%20viewBox='0%200%2025%2025'%3E%3C\/svg%3E)](https:\/\/x.com\/seimaxim\/)   [![twitter](data:image\/svg+xml,%3Csvg%20xmlns='http:\/\/www.w3.org\/2000\/svg'%20width='25'%20height='25'%20viewBox='0%200%2025%2025'%3E%3C\/svg%3E)](https:\/\/facebook.com\/seimaxim\/)\n\n###### LEGAL\n- [Terms and conditions](https:\/\/www.seimaxim.com\/terms)\n- [GDPR](https:\/\/www.seimaxim.com\/terms\/gdpr)\n- [Abuse prevention](https:\/\/www.seimaxim.com\/terms\/abuse)\n- [SLA](https:\/\/www.seimaxim.com\/terms\/sla)\n- [DMCA](https:\/\/www.seimaxim.com\/terms\/dmca)\n- [Refund Policy](https:\/\/www.seimaxim.com\/terms\/refund)\n- [Accepted Use Policy](https:\/\/www.seimaxim.com\/terms\/aup)\n\n###### ACCOUNT\n- [Dashboard](https:\/\/app.seimaxim.com\/login)\n- [Create Account](https:\/\/app.seimaxim.com\/register.php)\n- [Forgot Password?](https:\/\/app.seimaxim.com\/pwreset.php)\n- [Contact Support](https:\/\/app.seimaxim.com\/submitticket.php)\n- [Knowledgebase](https:\/\/www.seimaxim.com\/kb)\n- [Blog](https:\/\/www.seimaxim.com\/blog)\n- [About us](https:\/\/www.seimaxim.com\/about)\n\n###### RECENT POSTS\n- [GPU-Accelerated Data Analytics: Best Practices](https:\/\/www.seimaxim.com\/kb\/dedicated-servers\/gpu-accelerated-data-analytics-best-practices) March 26, 2025\n- [GPU Server powered VR: The Future of Simulation](https:\/\/www.seimaxim.com\/kb\/dedicated-servers\/gpu-server-powered-vr-the-future-of-simulation) March 23, 2025\n\n![logo nullshock footer](data:image\/svg+xml,%3Csvg%20xmlns='http:\/\/www.w3.org\/2000\/svg'%20width='300'%20height='300'%20viewBox='0%200%20300%20300'%3E%3C\/svg%3E)\n\nWe accept Bitcoins, PayPal, Credit \\| Debit cards, GooglePay, Alipay, iDEAL, Webmoney, POLi, Russia Bank Transfer, Bancontact, Multibanco, and Global Banks transfers.   \n  \nThe entirety of this site is protected by © Copyright 2018 - 2026 \\| SeiMaxim \\| All Rights Reserved. All trademarks and trade names shown are the property of their respective owners and no endorsement or derogation is intended or inferred. Offers subject to change, not combinable with all other offers. SeiMaxim reserves the right to cancel orders arising from pricing or other errors.\n\nTable of Contents\n\n[×](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat)\n\n- [Enable or Disable MIG](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat)\n- [List all GPU Instances](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat)\n- [Create GPU instances on MIG-enabled GPU](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat)\n- [Create Compute instances on a MIG-enabled GPU](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat)\n- [View MIG Instances](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat)\n- [List GPU Instances](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat)\n- [List Compute Instances](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat)\n- [Destroy Compute Instances](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat)\n- [Destroy GPU Instances](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat)\n- [Getting MIG Help](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat)\n\n[→ Index](https:\/\/www.seimaxim.com\/kb\/gpu\/nvidia-a100-mig-cheat-sheat)","attrs_readable_markdown":"MIG is only compatible with Linux distributions that support CUDA 11\/R450 or higher. It’s also a good idea to use the NVIDIA Datacenter Linux driver version 450.80.02 or higher. MIG is not supported on any Windows Pro or Server OS.\n\nThe new Multi-Instance GPU (MIG) functionality allows NVIDIA Ampere-based GPUs (such as the [NVIDIA A100](https:\/\/www.seimaxim.com\/dedicated-servers\/gpu)) to be securely partitioned into up to seven independent GPU Instances for CUDA applications, giving different users separate GPU resources for optimal GPU use.\n\nThis functionality is especially useful for workloads that do not completely utilize the GPU’s computing capabilities, and users may want to run many tasks in parallel to get the most out of their GPU.\n\nThe following prerequisites and software versions are highly recommended when using supported GPUs in MIG mode.\n\nOnly the GPUs and systems listed below are compatible with MIG.\n\n- NVIDIA driver 450.80.02 or later is required for CUDA 11.\n- Linux distributions that were supported by CUDA 11\n\nIf you are using Kubernetes or containers, make sure to use;\n\n- Version 2.5.0 or later of the NVIDIA Container Toolkit (nvidia-docker2)\n- v0.7.0 or newer of the NVIDIA K8s Device Plugin\n- Version 0.2.0 or later of NVIDIA gpu-feature-discovery\n\nNVIDIA Management Library (NVML) APIs or the nvidia-smi command-line interface can be used to manage MIG programmatically. Some of the nvidia-smi output in the following examples may be cropped for brevity to highlight the relevant sections of interest.\n\n## Enable or Disable MIG\nTo enable or disable MIG on all GPUs or a certain GPU, enable persistence mode on all GPUs.\n```\nnvidia-smi -pm 1\n\nroot@server:~# nvidia-smi -pm 1\nEnabled persistence mode for GPU 00000000:31:00.0.\nEnabled persistence mode for GPU 00000000:CA:00.0.\nAll done.\n```\nThen enable MIG by using the following command.\n\n`root@server:~# nvidia-smi -mig 1`\n```\nroot@server:~# nvidia-smi\nTue Feb 22 11:47:45 2022       \n+-----------------------------------------------------------------------------+\n| NVIDIA-SMI 510.39.01    Driver Version: 510.39.01    CUDA Version: 11.6     |\n|-------------------------------+----------------------+----------------------+\n| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |\n| Fan  Temp  Perf  Pwr:Usage\/Cap|         Memory-Usage | GPU-Util  Compute M. |\n|                               |                      |               MIG M. |\n|===============================+======================+======================|\n|   0  NVIDIA A100 80G...  On   | 00000000:31:00.0 Off |                   On |\n| N\/A   34C    P0    41W \/ 300W |      0MiB \/ 81920MiB |     N\/A      Default |\n|                               |                      |              Enabled |\n+-------------------------------+----------------------+----------------------+\n|   1  NVIDIA A100 80G...  On   | 00000000:CA:00.0 Off |                   On |\n| N\/A   34C    P0    43W \/ 300W |      0MiB \/ 81920MiB |     N\/A      Default |\n|                               |                      |              Enabled |\n+-------------------------------+----------------------+----------------------+\n\n+-----------------------------------------------------------------------------+\n| MIG devices:                                                                |\n+------------------+----------------------+-----------+-----------------------+\n| GPU  GI  CI  MIG |         Memory-Usage |        Vol|         Shared        |\n|      ID  ID  Dev |           BAR1-Usage | SM     Unc| CE  ENC  DEC  OFA  JPG|\n|                  |                      |        ECC|                       |\n|==================+======================+===========+=======================|\n|  No MIG devices found                                                       |\n+-----------------------------------------------------------------------------+\n\n+-----------------------------------------------------------------------------+\n| Processes:                                                                  |\n|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |\n|        ID   ID                                                   Usage      |\n|=============================================================================|\n|  No running processes found                                                 |\n+-----------------------------------------------------------------------------+\n```\nTo disable MIG use the following command.\n\n`nvidia-smi -mig 0`\n```\nroot@server:~# nvidia-smi -mig 0\nDisabled MIG Mode for GPU 00000000:31:00.0\nDisabled MIG Mode for GPU 00000000:CA:00.0\nAll done.\n```\nTo enable or disable MIG on a specific device.\n\n## List all GPU Instances\n```\nroot@server:~# nvidia-smi mig -lgip\n+-----------------------------------------------------------------------------+\n| GPU instance profiles:                                                      |\n| GPU   Name             ID    Instances   Memory     P2P    SM    DEC   ENC  |\n|                              Free\/Total   GiB              CE    JPEG  OFA  |\n|=============================================================================|\n|   0  MIG 1g.10gb       19     7\/7        9.50       No     14     0     0   |\n|                                                             1     0     0   |\n+-----------------------------------------------------------------------------+\n|   0  MIG 1g.10gb+me    20     1\/1        9.50       No     14     1     0   |\n|                                                             1     1     1   |\n+-----------------------------------------------------------------------------+\n|   0  MIG 2g.20gb       14     3\/3        19.50      No     28     1     0   |\n|                                                             2     0     0   |\n+-----------------------------------------------------------------------------+\n|   0  MIG 3g.40gb        9     2\/2        39.25      No     42     2     0   |\n|                                                             3     0     0   |\n+-----------------------------------------------------------------------------+\n|   0  MIG 4g.40gb        5     1\/1        39.25      No     56     2     0   |\n|                                                             4     0     0   |\n+-----------------------------------------------------------------------------+\n|   0  MIG 7g.80gb        0     1\/1        78.75      No     98     5     0   |\n|                                                             7     1     1   |\n+-----------------------------------------------------------------------------+\n|   1  MIG 1g.10gb       19     7\/7        9.50       No     14     0     0   |\n|                                                             1     0     0   |\n+-----------------------------------------------------------------------------+\n|   1  MIG 1g.10gb+me    20     1\/1        9.50       No     14     1     0   |\n|                                                             1     1     1   |\n+-----------------------------------------------------------------------------+\n|   1  MIG 2g.20gb       14     3\/3        19.50      No     28     1     0   |\n|                                                             2     0     0   |\n+-----------------------------------------------------------------------------+\n|   1  MIG 3g.40gb        9     2\/2        39.25      No     42     2     0   |\n|                                                             3     0     0   |\n+-----------------------------------------------------------------------------+\n|   1  MIG 4g.40gb        5     1\/1        39.25      No     56     2     0   |\n|                                                             4     0     0   |\n+-----------------------------------------------------------------------------+\n|   1  MIG 7g.80gb        0     1\/1        78.75      No     98     5     0   |\n|                                                             7     1     1   |\n+-----------------------------------------------------------------------------+\n```\n## Create GPU instances on MIG-enabled GPU\n```\nroot@server:~# nvidia-smi mig -cgi 19,19,19,19,19,19,19 -i 3\nSuccessfully created GPU instance ID 13 on GPU  0 using profile MIG 1g.5gb (ID 19)\nSuccessfully created GPU instance ID 11 on GPU  0 using profile MIG 1g.5gb (ID 19)\nSuccessfully created GPU instance ID 12 on GPU  0 using profile MIG 1g.5gb (ID 19)\nSuccessfully created GPU instance ID  7 on GPU  0 using profile MIG 1g.5gb (ID 19)\nSuccessfully created GPU instance ID  8 on GPU  0 using profile MIG 1g.5gb (ID 19)\nSuccessfully created GPU instance ID  9 on GPU  0 using profile MIG 1g.5gb (ID 19)\nSuccessfully created GPU instance ID 10 on GPU  0 using profile MIG 1g.5gb (ID 19)\n```\n## Create Compute instances on a MIG-enabled GPU\n```\nroot@server:~# nvidia-smi mig -cci -i 3\nSuccessfully created compute instance ID  0 on GPU  0 GPU instance ID  7 using profile MIG 1g.5gb (ID  0)\nSuccessfully created compute instance ID  0 on GPU  0 GPU instance ID  8 using profile MIG 1g.5gb (ID  0)\nSuccessfully created compute instance ID  0 on GPU  0 GPU instance ID  9 using profile MIG 1g.5gb (ID  0)\nSuccessfully created compute instance ID  0 on GPU  0 GPU instance ID 10 using profile MIG 1g.5gb (ID  0)\nSuccessfully created compute instance ID  0 on GPU  0 GPU instance ID 11 using profile MIG 1g.5gb (ID  0)\nSuccessfully created compute instance ID  0 on GPU  0 GPU instance ID 12 using profile MIG 1g.5gb (ID  0)\nSuccessfully created compute instance ID  0 on GPU  0 GPU instance ID 13 using profile MIG 1g.5gb (ID  0)\n```\n## View MIG Instances\n```\nroot@server:~# nvidia-smi\n\n+-----------------------------------------------------------------------------+\n| MIG devices:                                                                |\n+------------------+----------------------+-----------+-----------------------+\n| GPU  GI  CI  MIG |         Memory-Usage |        Vol|         Shared        |\n|      ID  ID  Dev |           BAR1-Usage | SM     Unc| CE  ENC  DEC  OFA  JPG|\n|                  |                      |        ECC|                       |\n|==================+======================+===========+=======================|\n|  0    7   0   0  |      1MiB \/  4864MiB | 14      0 |  1   0    0    0    0 |\n|                  |      0MiB \/  8191MiB |           |                       |\n+------------------+----------------------+-----------+-----------------------+\n|  0    8   0   1  |      1MiB \/  4864MiB | 14      0 |  1   0    0    0    0 |\n|                  |      0MiB \/  8191MiB |           |                       |\n+------------------+----------------------+-----------+-----------------------+\n|  0    9   0   2  |      1MiB \/  4864MiB | 14      0 |  1   0    0    0    0 |\n|                  |      0MiB \/  8191MiB |           |                       |\n+------------------+----------------------+-----------+-----------------------+\n|  0   10   0   3  |      1MiB \/  4864MiB | 14      0 |  1   0    0    0    0 |\n|                  |      0MiB \/  8191MiB |           |                       |\n+------------------+----------------------+-----------+-----------------------+\n|  0   11   0   4  |      1MiB \/  4864MiB | 14      0 |  1   0    0    0    0 |\n|                  |      0MiB \/  8191MiB |           |                       |\n+------------------+----------------------+-----------+-----------------------+\n|  0   12   0   5  |      1MiB \/  4864MiB | 14      0 |  1   0    0    0    0 |\n|                  |      0MiB \/  8191MiB |           |                       |\n+------------------+----------------------+-----------+-----------------------+\n|  0   13   0   6  |      1MiB \/  4864MiB | 14      0 |  1   0    0    0    0 |\n|                  |      0MiB \/  8191MiB |           |                       |\n+------------------+----------------------+-----------+-----------------------+\n```\n```\nroot@server:~# nvidia-smi -L\nGPU 0: A100-PCIE-40GB (UUID: GPU-0069414c-9f30-41f9-d5d8-87890423f0c4)\n  MIG 1g.5gb Device 0: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4\/7\/0)\n  MIG 1g.5gb Device 1: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4\/8\/0)\n  MIG 1g.5gb Device 2: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4\/9\/0)\n  MIG 1g.5gb Device 3: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4\/10\/0)\n  MIG 1g.5gb Device 4: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4\/11\/0)\n  MIG 1g.5gb Device 5: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4\/12\/0)\n  MIG 1g.5gb Device 6: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4\/13\/0)\n```\n## List GPU Instances\n`root@server:~# nvidia mig -lgi`\n\n## List Compute Instances\n```\nroot@server:~# nvidia mig -lci\n\n+-------------------------------------------------------+\n| Compute instances:                                    |\n| GPU     GPU       Name             Profile   Instance |\n|       Instance                       ID        ID     |\n|         ID                                            |\n|=======================================================|\n|   0      7       MIG 1g.5gb           0         0     |\n+-------------------------------------------------------+\n|   0      8       MIG 1g.5gb           0         0     |\n+-------------------------------------------------------+\n|   0      9       MIG 1g.5gb           0         0     |\n+-------------------------------------------------------+\n|   0     11       MIG 1g.5gb           0         0     |\n+-------------------------------------------------------+\n|   0     12       MIG 1g.5gb           0         0     |\n+-------------------------------------------------------+\n|   0     13       MIG 1g.5gb           0         0     |\n+-------------------------------------------------------+\n|   0     14       MIG 1g.5gb           0         0     |\n+-------------------------------------------------------+\n```\n## Destroy Compute Instances\n```\nroot@server:~# nvidia-smi mig -dci -i 3\nSuccessfully destroyed compute instance ID  0 from GPU  0 GPU instance ID  7\nSuccessfully destroyed compute instance ID  0 from GPU  0 GPU instance ID  8\nSuccessfully destroyed compute instance ID  0 from GPU  0 GPU instance ID  9\nSuccessfully destroyed compute instance ID  0 from GPU  0 GPU instance ID 10\nSuccessfully destroyed compute instance ID  0 from GPU  0 GPU instance ID 11\nSuccessfully destroyed compute instance ID  0 from GPU  0 GPU instance ID 12\nSuccessfully destroyed compute instance ID  0 from GPU  0 GPU instance ID 13\n```\n## Destroy GPU Instances\n```\nroot@server:~# nvidia-smi mig -dgi -i 3\nSuccessfully destroyed GPU instance ID  7 from GPU  0\nSuccessfully destroyed GPU instance ID  8 from GPU  0\nSuccessfully destroyed GPU instance ID  9 from GPU  0\nSuccessfully destroyed GPU instance ID 10 from GPU  0\nSuccessfully destroyed GPU instance ID 11 from GPU  0\nSuccessfully destroyed GPU instance ID 12 from GPU  0\nSuccessfully destroyed GPU instance ID 13 from GPU  0\n```\n## Getting MIG Help\n```\nroot@server:~# nvidia-smi mig -h\n\n    mig -- Multi Instance GPU management.\n\n    Usage: nvidia-smi mig [options]\n\n    Options include:\n    [-h | --help]: Display help information.\n    [-i | --id]: Enumeration index, PCI bus ID or UUID.\n                 Provide comma separated values for more than one device.\n    [-gi | --gpu-instance-id]: GPU instance ID.\n                               Provide comma separated values for more than one GPU instance.\n    [-ci | --compute-instance-id]: Compute instance ID.\n                                   Provide comma separated values for more than one compute \n                                   instance.\n    [-lgip | --list-gpu-instance-profiles]: List supported GPU instance profiles.\n                                            Option -i can be used to restrict the command to\n                                            run on a specific GPU.\n    [-lgipp | --list-gpu-instance-possible-placements]: List possible GPU instance placements\n                                                        in the following format, {Start}:Size.\n                                                        Option -i can be used to restrict the\n                                                        command to run on a specific GPU.\n    [-C | --default-compute-instance]: Create compute instance with the default profile when used\n                                       with the option to create a GPU instance (-cgi).\n    [-cgi | --create-gpu-instance]: Create GPU instances for the given profile tuples. A profile\n                                    tuple consists of a profile name or ID and an optional placement\n                                    specifier, which consists of a colon and a placement start index.\n                                    Provide comma separated values for more than one profile tuple.\n                                    Option -i can be used to restrict the command to run on\n                                    a specific GPU.\n    [-dgi | --destroy-gpu-instance]: Destroy GPU instances.\n                                     Options -i and -gi can be used individually or combined\n                                     to restrict the command to run on a specific GPU or GPU\n                                     instance.\n    [-lgi | --list-gpu-instances]: List GPU instances.\n                                   Option -i can be used to restrict the command to run on a\n                                   specific GPU.\n    [-lcip | --list-compute-instance-profiles]: List supported compute instance profiles.\n                                                Options -i and -gi can be used individually or\n                                                combined to restrict the command to run on a\n                                                specific GPU or GPU instance.\n    [-cci | --create-compute-instance]: Create compute instance for the given profile name or IDs.\n                                        Provide comma separated values for more than one profile.\n                                        If no profile name or ID is given, then the default*\n                                        compute instance profile ID will be used. Options -i and\n                                        -gi can be used individually or combined to restrict the\n                                        command to run on a specific GPU or GPU instance.\n    [-dci | --destroy-compute-instance]: Destroy compute instances.\n                                         Options -i, -gi and -ci can be used individually or\n                                         combined to restrict the command to run on a specific\n                                         GPU or GPU instance or compute instance.\n    [-lci | --list-compute-instances]: List compute instances.\n                                       Options -i and -gi can be used individually or combined\n                                       to restrict the command to run on a specific GPU or GPU\n                                       instance.\n```","meta_canonical":null}

3. Robots.txt Check

Query:

Response:

4. Spam/Ban Check

Query:

Response:

5. Seen Status Check

ℹ️ Skipped - page is already crawled

📄

INDEXABLE

✅

CRAWLED

29 days ago

🤖

ROBOTS ALLOWED

Page Info Filters

Filter	Status	Condition	Details
HTTP status	PASS	`download_http_code = 200`	HTTP 200
Age cutoff	PASS	`download_stamp > now() - 6 MONTH`	1 months ago
History drop	PASS	`isNull(history_drop_reason)`	No drop reason
Spam/ban	PASS	`fh_dont_index != 1 AND ml_spam_score = 0`	ml_spam_score=0
Canonical	PASS	`meta_canonical IS NULL OR = '' OR = src_unparsed`	Not set

Page Details

Property	Value
URL	https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat
Last Crawled	2026-03-08 17:23:52 (29 days ago)
First Indexed	2022-02-22 16:32:48 (4 years ago)
HTTP Status Code	200
Meta Title	NVIDIA A100 MIG Cheat Sheat – SeiMaxim
Meta Description	MIG is only compatible with Linux distributions that support CUDA 11/R450 or higher. It's also a good idea to use the NVIDIA Datacenter Linux driver version
Meta Canonical	null
Boilerpipe Text	MIG is only compatible with Linux distributions that support CUDA 11/R450 or higher. It’s also a good idea to use the NVIDIA Datacenter Linux driver version 450.80.02 or higher. MIG is not supported on any Windows Pro or Server OS. The new Multi-Instance GPU (MIG) functionality allows NVIDIA Ampere-based GPUs (such as the NVIDIA A100 ) to be securely partitioned into up to seven independent GPU Instances for CUDA applications, giving different users separate GPU resources for optimal GPU use. This functionality is especially useful for workloads that do not completely utilize the GPU’s computing capabilities, and users may want to run many tasks in parallel to get the most out of their GPU. The following prerequisites and software versions are highly recommended when using supported GPUs in MIG mode. Only the GPUs and systems listed below are compatible with MIG. NVIDIA driver 450.80.02 or later is required for CUDA 11. Linux distributions that were supported by CUDA 11 If you are using Kubernetes or containers, make sure to use; Version 2.5.0 or later of the NVIDIA Container Toolkit (nvidia-docker2) v0.7.0 or newer of the NVIDIA K8s Device Plugin Version 0.2.0 or later of NVIDIA gpu-feature-discovery NVIDIA Management Library (NVML) APIs or the nvidia-smi command-line interface can be used to manage MIG programmatically. Some of the nvidia-smi output in the following examples may be cropped for brevity to highlight the relevant sections of interest. Enable or Disable MIG To enable or disable MIG on all GPUs or a certain GPU, enable persistence mode on all GPUs. nvidia-smi -pm 1 root@server:~# nvidia-smi -pm 1 Enabled persistence mode for GPU 00000000:31:00.0. Enabled persistence mode for GPU 00000000:CA:00.0. All done. Then enable MIG by using the following command. root@server:~# nvidia-smi -mig 1 root@server:~# nvidia-smi Tue Feb 22 11:47:45 2022 +-----------------------------------------------------------------------------+ \| NVIDIA-SMI 510.39.01 Driver Version: 510.39.01 CUDA Version: 11.6 \| \|-------------------------------+----------------------+----------------------+ \| GPU Name Persistence-M\| Bus-Id Disp.A \| Volatile Uncorr. ECC \| \| Fan Temp Perf Pwr:Usage/Cap\| Memory-Usage \| GPU-Util Compute M. \| \| \| \| MIG M. \| \|===============================+======================+======================\| \| 0 NVIDIA A100 80G... On \| 00000000:31:00.0 Off \| On \| \| N/A 34C P0 41W / 300W \| 0MiB / 81920MiB \| N/A Default \| \| \| \| Enabled \| +-------------------------------+----------------------+----------------------+ \| 1 NVIDIA A100 80G... On \| 00000000:CA:00.0 Off \| On \| \| N/A 34C P0 43W / 300W \| 0MiB / 81920MiB \| N/A Default \| \| \| \| Enabled \| +-------------------------------+----------------------+----------------------+ +-----------------------------------------------------------------------------+ \| MIG devices: \| +------------------+----------------------+-----------+-----------------------+ \| GPU GI CI MIG \| Memory-Usage \| Vol\| Shared \| \| ID ID Dev \| BAR1-Usage \| SM Unc\| CE ENC DEC OFA JPG\| \| \| \| ECC\| \| \|==================+======================+===========+=======================\| \| No MIG devices found \| +-----------------------------------------------------------------------------+ +-----------------------------------------------------------------------------+ \| Processes: \| \| GPU GI CI PID Type Process name GPU Memory \| \| ID ID Usage \| \|=============================================================================\| \| No running processes found \| +-----------------------------------------------------------------------------+ To disable MIG use the following command. nvidia-smi -mig 0 root@server:~# nvidia-smi -mig 0 Disabled MIG Mode for GPU 00000000:31:00.0 Disabled MIG Mode for GPU 00000000:CA:00.0 All done. To enable or disable MIG on a specific device. nvidia-smi -i 3 -mig 1 nvidia-smi -i 3 -mig 0 List all GPU Instances root@server:~# nvidia-smi mig -lgip +-----------------------------------------------------------------------------+ \| GPU instance profiles: \| \| GPU Name ID Instances Memory P2P SM DEC ENC \| \| Free/Total GiB CE JPEG OFA \| \|=============================================================================\| \| 0 MIG 1g.10gb 19 7/7 9.50 No 14 0 0 \| \| 1 0 0 \| +-----------------------------------------------------------------------------+ \| 0 MIG 1g.10gb+me 20 1/1 9.50 No 14 1 0 \| \| 1 1 1 \| +-----------------------------------------------------------------------------+ \| 0 MIG 2g.20gb 14 3/3 19.50 No 28 1 0 \| \| 2 0 0 \| +-----------------------------------------------------------------------------+ \| 0 MIG 3g.40gb 9 2/2 39.25 No 42 2 0 \| \| 3 0 0 \| +-----------------------------------------------------------------------------+ \| 0 MIG 4g.40gb 5 1/1 39.25 No 56 2 0 \| \| 4 0 0 \| +-----------------------------------------------------------------------------+ \| 0 MIG 7g.80gb 0 1/1 78.75 No 98 5 0 \| \| 7 1 1 \| +-----------------------------------------------------------------------------+ \| 1 MIG 1g.10gb 19 7/7 9.50 No 14 0 0 \| \| 1 0 0 \| +-----------------------------------------------------------------------------+ \| 1 MIG 1g.10gb+me 20 1/1 9.50 No 14 1 0 \| \| 1 1 1 \| +-----------------------------------------------------------------------------+ \| 1 MIG 2g.20gb 14 3/3 19.50 No 28 1 0 \| \| 2 0 0 \| +-----------------------------------------------------------------------------+ \| 1 MIG 3g.40gb 9 2/2 39.25 No 42 2 0 \| \| 3 0 0 \| +-----------------------------------------------------------------------------+ \| 1 MIG 4g.40gb 5 1/1 39.25 No 56 2 0 \| \| 4 0 0 \| +-----------------------------------------------------------------------------+ \| 1 MIG 7g.80gb 0 1/1 78.75 No 98 5 0 \| \| 7 1 1 \| +-----------------------------------------------------------------------------+ Create GPU instances on MIG-enabled GPU root@server:~# nvidia-smi mig -cgi 19,19,19,19,19,19,19 -i 3 Successfully created GPU instance ID 13 on GPU 0 using profile MIG 1g.5gb (ID 19) Successfully created GPU instance ID 11 on GPU 0 using profile MIG 1g.5gb (ID 19) Successfully created GPU instance ID 12 on GPU 0 using profile MIG 1g.5gb (ID 19) Successfully created GPU instance ID 7 on GPU 0 using profile MIG 1g.5gb (ID 19) Successfully created GPU instance ID 8 on GPU 0 using profile MIG 1g.5gb (ID 19) Successfully created GPU instance ID 9 on GPU 0 using profile MIG 1g.5gb (ID 19) Successfully created GPU instance ID 10 on GPU 0 using profile MIG 1g.5gb (ID 19) Create Compute instances on a MIG-enabled GPU root@server:~# nvidia-smi mig -cci -i 3 Successfully created compute instance ID 0 on GPU 0 GPU instance ID 7 using profile MIG 1g.5gb (ID 0) Successfully created compute instance ID 0 on GPU 0 GPU instance ID 8 using profile MIG 1g.5gb (ID 0) Successfully created compute instance ID 0 on GPU 0 GPU instance ID 9 using profile MIG 1g.5gb (ID 0) Successfully created compute instance ID 0 on GPU 0 GPU instance ID 10 using profile MIG 1g.5gb (ID 0) Successfully created compute instance ID 0 on GPU 0 GPU instance ID 11 using profile MIG 1g.5gb (ID 0) Successfully created compute instance ID 0 on GPU 0 GPU instance ID 12 using profile MIG 1g.5gb (ID 0) Successfully created compute instance ID 0 on GPU 0 GPU instance ID 13 using profile MIG 1g.5gb (ID 0) View MIG Instances root@server:~# nvidia-smi +-----------------------------------------------------------------------------+ \| MIG devices: \| +------------------+----------------------+-----------+-----------------------+ \| GPU GI CI MIG \| Memory-Usage \| Vol\| Shared \| \| ID ID Dev \| BAR1-Usage \| SM Unc\| CE ENC DEC OFA JPG\| \| \| \| ECC\| \| \|==================+======================+===========+=======================\| \| 0 7 0 0 \| 1MiB / 4864MiB \| 14 0 \| 1 0 0 0 0 \| \| \| 0MiB / 8191MiB \| \| \| +------------------+----------------------+-----------+-----------------------+ \| 0 8 0 1 \| 1MiB / 4864MiB \| 14 0 \| 1 0 0 0 0 \| \| \| 0MiB / 8191MiB \| \| \| +------------------+----------------------+-----------+-----------------------+ \| 0 9 0 2 \| 1MiB / 4864MiB \| 14 0 \| 1 0 0 0 0 \| \| \| 0MiB / 8191MiB \| \| \| +------------------+----------------------+-----------+-----------------------+ \| 0 10 0 3 \| 1MiB / 4864MiB \| 14 0 \| 1 0 0 0 0 \| \| \| 0MiB / 8191MiB \| \| \| +------------------+----------------------+-----------+-----------------------+ \| 0 11 0 4 \| 1MiB / 4864MiB \| 14 0 \| 1 0 0 0 0 \| \| \| 0MiB / 8191MiB \| \| \| +------------------+----------------------+-----------+-----------------------+ \| 0 12 0 5 \| 1MiB / 4864MiB \| 14 0 \| 1 0 0 0 0 \| \| \| 0MiB / 8191MiB \| \| \| +------------------+----------------------+-----------+-----------------------+ \| 0 13 0 6 \| 1MiB / 4864MiB \| 14 0 \| 1 0 0 0 0 \| \| \| 0MiB / 8191MiB \| \| \| +------------------+----------------------+-----------+-----------------------+ root@server:~# nvidia-smi -L GPU 0: A100-PCIE-40GB (UUID: GPU-0069414c-9f30-41f9-d5d8-87890423f0c4) MIG 1g.5gb Device 0: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4/7/0) MIG 1g.5gb Device 1: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4/8/0) MIG 1g.5gb Device 2: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4/9/0) MIG 1g.5gb Device 3: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4/10/0) MIG 1g.5gb Device 4: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4/11/0) MIG 1g.5gb Device 5: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4/12/0) MIG 1g.5gb Device 6: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4/13/0) List GPU Instances root@server:~# nvidia mig -lgi List Compute Instances root@server:~# nvidia mig -lci +-------------------------------------------------------+ \| Compute instances: \| \| GPU GPU Name Profile Instance \| \| Instance ID ID \| \| ID \| \|=======================================================\| \| 0 7 MIG 1g.5gb 0 0 \| +-------------------------------------------------------+ \| 0 8 MIG 1g.5gb 0 0 \| +-------------------------------------------------------+ \| 0 9 MIG 1g.5gb 0 0 \| +-------------------------------------------------------+ \| 0 11 MIG 1g.5gb 0 0 \| +-------------------------------------------------------+ \| 0 12 MIG 1g.5gb 0 0 \| +-------------------------------------------------------+ \| 0 13 MIG 1g.5gb 0 0 \| +-------------------------------------------------------+ \| 0 14 MIG 1g.5gb 0 0 \| +-------------------------------------------------------+ Destroy Compute Instances root@server:~# nvidia-smi mig -dci -i 3 Successfully destroyed compute instance ID 0 from GPU 0 GPU instance ID 7 Successfully destroyed compute instance ID 0 from GPU 0 GPU instance ID 8 Successfully destroyed compute instance ID 0 from GPU 0 GPU instance ID 9 Successfully destroyed compute instance ID 0 from GPU 0 GPU instance ID 10 Successfully destroyed compute instance ID 0 from GPU 0 GPU instance ID 11 Successfully destroyed compute instance ID 0 from GPU 0 GPU instance ID 12 Successfully destroyed compute instance ID 0 from GPU 0 GPU instance ID 13 Destroy GPU Instances root@server:~# nvidia-smi mig -dgi -i 3 Successfully destroyed GPU instance ID 7 from GPU 0 Successfully destroyed GPU instance ID 8 from GPU 0 Successfully destroyed GPU instance ID 9 from GPU 0 Successfully destroyed GPU instance ID 10 from GPU 0 Successfully destroyed GPU instance ID 11 from GPU 0 Successfully destroyed GPU instance ID 12 from GPU 0 Successfully destroyed GPU instance ID 13 from GPU 0 Getting MIG Help root@server:~# nvidia-smi mig -h mig -- Multi Instance GPU management. Usage: nvidia-smi mig [options] Options include: [-h \| --help]: Display help information. [-i \| --id]: Enumeration index, PCI bus ID or UUID. Provide comma separated values for more than one device. [-gi \| --gpu-instance-id]: GPU instance ID. Provide comma separated values for more than one GPU instance. [-ci \| --compute-instance-id]: Compute instance ID. Provide comma separated values for more than one compute instance. [-lgip \| --list-gpu-instance-profiles]: List supported GPU instance profiles. Option -i can be used to restrict the command to run on a specific GPU. [-lgipp \| --list-gpu-instance-possible-placements]: List possible GPU instance placements in the following format, {Start}:Size. Option -i can be used to restrict the command to run on a specific GPU. [-C \| --default-compute-instance]: Create compute instance with the default profile when used with the option to create a GPU instance (-cgi). [-cgi \| --create-gpu-instance]: Create GPU instances for the given profile tuples. A profile tuple consists of a profile name or ID and an optional placement specifier, which consists of a colon and a placement start index. Provide comma separated values for more than one profile tuple. Option -i can be used to restrict the command to run on a specific GPU. [-dgi \| --destroy-gpu-instance]: Destroy GPU instances. Options -i and -gi can be used individually or combined to restrict the command to run on a specific GPU or GPU instance. [-lgi \| --list-gpu-instances]: List GPU instances. Option -i can be used to restrict the command to run on a specific GPU. [-lcip \| --list-compute-instance-profiles]: List supported compute instance profiles. Options -i and -gi can be used individually or combined to restrict the command to run on a specific GPU or GPU instance. [-cci \| --create-compute-instance]: Create compute instance for the given profile name or IDs. Provide comma separated values for more than one profile. If no profile name or ID is given, then the default* compute instance profile ID will be used. Options -i and -gi can be used individually or combined to restrict the command to run on a specific GPU or GPU instance. [-dci \| --destroy-compute-instance]: Destroy compute instances. Options -i, -gi and -ci can be used individually or combined to restrict the command to run on a specific GPU or GPU instance or compute instance. [-lci \| --list-compute-instances]: List compute instances. Options -i and -gi can be used individually or combined to restrict the command to run on a specific GPU or GPU instance.
Markdown	[Skip to content](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat#site-content) # [seimaxim](https://www.seimaxim.com/) Menu [![dashboard](https://www.seimaxim.com/wp-content/uploads/2025/11/dashboard-seimaxim-1.webp)](https://app.seimaxim.com/login) [![SeiMaxim Logo](https://www.seimaxim.com/wp-content/uploads/2020/12/logo-2.svg)](https://www.seimaxim.com/) - [![SeiMaxim Logo](https://www.seimaxim.com/wp-content/uploads/2020/12/logo-2.svg)](https://www.seimaxim.com/) - [Server](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat) - [Dedicated Servers](https://www.seimaxim.com/dedicated-servers) - Deploy dedicated servers in 10 regions globally at unbeatable prices. - ![datacenter](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20width='300'%20height='157'%20viewBox='0%200%20300%20157'%3E%3C/svg%3E) - [Buy now](https://www.seimaxim.com/dedicated-servers) - [GPU Dedicated Servers](https://www.seimaxim.com/dedicated-servers/gpu) - Dedicated GPU servers with nVIDIA A4, NVIDIA A100 80GB, and RTX A6000 are available. - ![nvidia rtx a6000](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20width='300'%20height='157'%20viewBox='0%200%20300%20157'%3E%3C/svg%3E) - [Buy now](https://www.seimaxim.com/dedicated-servers/gpu) - [Game Dedicated Servers](https://www.seimaxim.com/dedicated-servers/game) - Deliver a seamless multiplayer gaming experience to your players around the world. - ![gaming servers](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20width='300'%20height='157'%20viewBox='0%200%20300%20157'%3E%3C/svg%3E) - [Buy now](https://www.seimaxim.com/dedicated-servers/game) - [AMD Ryzen Servers](https://www.seimaxim.com/dedicated-servers/amd-ryzen) - Efficiently crunch numerical data, play the latest games, and create the most complex design. - ![amd ryzen server](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20width='300'%20height='157'%20viewBox='0%200%20300%20157'%3E%3C/svg%3E) - [Buy now](https://www.seimaxim.com/dedicated-servers/amd-ryzen) - [Managed Services](https://www.seimaxim.com/services) - Managed server services and secure data migration. Total security for your mission-critical workloads. - ![managed server](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20width='300'%20height='157'%20viewBox='0%200%20300%20157'%3E%3C/svg%3E) - [Buy now](https://www.seimaxim.com/services) - [Server Setup Services](https://www.seimaxim.com/platform-services) - Our experts are ready to work on your server hardware and software setup operations from scratch. - ![server setup datacenter](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20width='300'%20height='157'%20viewBox='0%200%20300%20157'%3E%3C/svg%3E) - [Buy now](https://www.seimaxim.com/platform-services) - [Colocation](https://www.seimaxim.com/colocation) - Reduce failure risk by choosing SeiMaxim data center colocation. - ![colocation](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20width='300'%20height='157'%20viewBox='0%200%20300%20157'%3E%3C/svg%3E) - [Buy now](https://www.seimaxim.com/colocation) - [Hosting](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat) - [Shared Hosting](https://www.seimaxim.com/shared-hosting) - [WordPress Hosting](https://www.seimaxim.com/shared-hosting/wordpress) - [Django Hosting](https://www.seimaxim.com/django-hosting) - [Drupal Hosting](https://www.seimaxim.com/drupal-hosting) - [Domains](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat) - [Domain Names](https://www.seimaxim.com/domain-names) - [Domain Transfer](https://www.seimaxim.com/domain-names/transfer) - [Domain Privacy](https://www.seimaxim.com/domain-names/privacy) - [WHOIS Lookup](https://www.seimaxim.com/domain-names/whois) - [VPS](https://www.seimaxim.com/vps-hosting) - [Solutions](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat) - [By Industry](https://www.seimaxim.com/solutions) - [E-Commerce](https://www.seimaxim.com/solutions/e-commerce) - [Gaming](https://www.seimaxim.com/solutions/gaming) - [Big Data](https://www.seimaxim.com/solutions/big-data) - [iGaming](https://www.seimaxim.com/solutions/igaming) - [AdTech & MarTech](https://www.seimaxim.com/solutions/adtech-martech) - [DevOps](https://www.seimaxim.com/solutions/devops) - [High Performance Computing](https://www.seimaxim.com/solutions/hpc) - [SaaS](https://www.seimaxim.com/solutions/saas) - [Legal](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat) - [Terms and conditions](https://www.seimaxim.com/terms) - [Privacy Policy](https://www.seimaxim.com/terms/privacy) - [Accepted Use Policy](https://www.seimaxim.com/terms/aup) - [Refund Policy](https://www.seimaxim.com/terms/refund) - [Abuse prevention](https://www.seimaxim.com/terms/abuse) - [GDPR](https://www.seimaxim.com/terms/gdpr) - [SLA](https://www.seimaxim.com/terms/sla) - [DMCA](https://www.seimaxim.com/terms/dmca) - [Customer verification](https://www.seimaxim.com/terms/customer-verification) - [Customer Commitment](https://www.seimaxim.com/about/customer-commitment) - [About Us](https://www.seimaxim.com/about) - [Contact Us](https://www.seimaxim.com/contact) - [Dashboard](https://app.seimaxim.com/login) Table of Contents - [Enable or Disable MIG](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat) - [List all GPU Instances](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat) - [Create GPU instances on MIG-enabled GPU](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat) - [Create Compute instances on a MIG-enabled GPU](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat) - [View MIG Instances](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat) - [List GPU Instances](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat) - [List Compute Instances](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat) - [Destroy Compute Instances](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat) - [Destroy GPU Instances](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat) - [Getting MIG Help](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat) # NVIDIA A100 MIG Cheat Sheat [![](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20width='96'%20height='96'%20viewBox='0%200%2096%2096'%3E%3C/svg%3E)](https://www.seimaxim.com/author/albert) by [Albert](https://www.seimaxim.com/author/albert) February 22, 2022 ![mig](https://www.seimaxim.com/wp-content/uploads/2022/02/mig-300x87.png) MIG is only compatible with Linux distributions that support CUDA 11/R450 or higher. It’s also a good idea to use the NVIDIA Datacenter Linux driver version 450.80.02 or higher. MIG is not supported on any Windows Pro or Server OS. The new Multi-Instance GPU (MIG) functionality allows NVIDIA Ampere-based GPUs (such as the [NVIDIA A100](https://www.seimaxim.com/dedicated-servers/gpu)) to be securely partitioned into up to seven independent GPU Instances for CUDA applications, giving different users separate GPU resources for optimal GPU use. This functionality is especially useful for workloads that do not completely utilize the GPU’s computing capabilities, and users may want to run many tasks in parallel to get the most out of their GPU. The following prerequisites and software versions are highly recommended when using supported GPUs in MIG mode. Only the GPUs and systems listed below are compatible with MIG. - NVIDIA driver 450.80.02 or later is required for CUDA 11. - Linux distributions that were supported by CUDA 11 If you are using Kubernetes or containers, make sure to use; - Version 2.5.0 or later of the NVIDIA Container Toolkit (nvidia-docker2) - v0.7.0 or newer of the NVIDIA K8s Device Plugin - Version 0.2.0 or later of NVIDIA gpu-feature-discovery NVIDIA Management Library (NVML) APIs or the nvidia-smi command-line interface can be used to manage MIG programmatically. Some of the nvidia-smi output in the following examples may be cropped for brevity to highlight the relevant sections of interest. ## Enable or Disable MIG To enable or disable MIG on all GPUs or a certain GPU, enable persistence mode on all GPUs. ``` nvidia-smi -pm 1 root@server:~# nvidia-smi -pm 1 Enabled persistence mode for GPU 00000000:31:00.0. Enabled persistence mode for GPU 00000000:CA:00.0. All done. ``` Then enable MIG by using the following command. `root@server:~# nvidia-smi -mig 1` ``` root@server:~# nvidia-smi Tue Feb 22 11:47:45 2022 +-----------------------------------------------------------------------------+ \| NVIDIA-SMI 510.39.01 Driver Version: 510.39.01 CUDA Version: 11.6 \| \|-------------------------------+----------------------+----------------------+ \| GPU Name Persistence-M\| Bus-Id Disp.A \| Volatile Uncorr. ECC \| \| Fan Temp Perf Pwr:Usage/Cap\| Memory-Usage \| GPU-Util Compute M. \| \| \| \| MIG M. \| \|===============================+======================+======================\| \| 0 NVIDIA A100 80G... On \| 00000000:31:00.0 Off \| On \| \| N/A 34C P0 41W / 300W \| 0MiB / 81920MiB \| N/A Default \| \| \| \| Enabled \| +-------------------------------+----------------------+----------------------+ \| 1 NVIDIA A100 80G... On \| 00000000:CA:00.0 Off \| On \| \| N/A 34C P0 43W / 300W \| 0MiB / 81920MiB \| N/A Default \| \| \| \| Enabled \| +-------------------------------+----------------------+----------------------+ +-----------------------------------------------------------------------------+ \| MIG devices: \| +------------------+----------------------+-----------+-----------------------+ \| GPU GI CI MIG \| Memory-Usage \| Vol\| Shared \| \| ID ID Dev \| BAR1-Usage \| SM Unc\| CE ENC DEC OFA JPG\| \| \| \| ECC\| \| \|==================+======================+===========+=======================\| \| No MIG devices found \| +-----------------------------------------------------------------------------+ +-----------------------------------------------------------------------------+ \| Processes: \| \| GPU GI CI PID Type Process name GPU Memory \| \| ID ID Usage \| \|=============================================================================\| \| No running processes found \| +-----------------------------------------------------------------------------+ ``` To disable MIG use the following command. `nvidia-smi -mig 0` ``` root@server:~# nvidia-smi -mig 0 Disabled MIG Mode for GPU 00000000:31:00.0 Disabled MIG Mode for GPU 00000000:CA:00.0 All done. ``` To enable or disable MIG on a specific device. ## List all GPU Instances ``` root@server:~# nvidia-smi mig -lgip +-----------------------------------------------------------------------------+ \| GPU instance profiles: \| \| GPU Name ID Instances Memory P2P SM DEC ENC \| \| Free/Total GiB CE JPEG OFA \| \|=============================================================================\| \| 0 MIG 1g.10gb 19 7/7 9.50 No 14 0 0 \| \| 1 0 0 \| +-----------------------------------------------------------------------------+ \| 0 MIG 1g.10gb+me 20 1/1 9.50 No 14 1 0 \| \| 1 1 1 \| +-----------------------------------------------------------------------------+ \| 0 MIG 2g.20gb 14 3/3 19.50 No 28 1 0 \| \| 2 0 0 \| +-----------------------------------------------------------------------------+ \| 0 MIG 3g.40gb 9 2/2 39.25 No 42 2 0 \| \| 3 0 0 \| +-----------------------------------------------------------------------------+ \| 0 MIG 4g.40gb 5 1/1 39.25 No 56 2 0 \| \| 4 0 0 \| +-----------------------------------------------------------------------------+ \| 0 MIG 7g.80gb 0 1/1 78.75 No 98 5 0 \| \| 7 1 1 \| +-----------------------------------------------------------------------------+ \| 1 MIG 1g.10gb 19 7/7 9.50 No 14 0 0 \| \| 1 0 0 \| +-----------------------------------------------------------------------------+ \| 1 MIG 1g.10gb+me 20 1/1 9.50 No 14 1 0 \| \| 1 1 1 \| +-----------------------------------------------------------------------------+ \| 1 MIG 2g.20gb 14 3/3 19.50 No 28 1 0 \| \| 2 0 0 \| +-----------------------------------------------------------------------------+ \| 1 MIG 3g.40gb 9 2/2 39.25 No 42 2 0 \| \| 3 0 0 \| +-----------------------------------------------------------------------------+ \| 1 MIG 4g.40gb 5 1/1 39.25 No 56 2 0 \| \| 4 0 0 \| +-----------------------------------------------------------------------------+ \| 1 MIG 7g.80gb 0 1/1 78.75 No 98 5 0 \| \| 7 1 1 \| +-----------------------------------------------------------------------------+ ``` ## Create GPU instances on MIG-enabled GPU ``` root@server:~# nvidia-smi mig -cgi 19,19,19,19,19,19,19 -i 3 Successfully created GPU instance ID 13 on GPU 0 using profile MIG 1g.5gb (ID 19) Successfully created GPU instance ID 11 on GPU 0 using profile MIG 1g.5gb (ID 19) Successfully created GPU instance ID 12 on GPU 0 using profile MIG 1g.5gb (ID 19) Successfully created GPU instance ID 7 on GPU 0 using profile MIG 1g.5gb (ID 19) Successfully created GPU instance ID 8 on GPU 0 using profile MIG 1g.5gb (ID 19) Successfully created GPU instance ID 9 on GPU 0 using profile MIG 1g.5gb (ID 19) Successfully created GPU instance ID 10 on GPU 0 using profile MIG 1g.5gb (ID 19) ``` ## Create Compute instances on a MIG-enabled GPU ``` root@server:~# nvidia-smi mig -cci -i 3 Successfully created compute instance ID 0 on GPU 0 GPU instance ID 7 using profile MIG 1g.5gb (ID 0) Successfully created compute instance ID 0 on GPU 0 GPU instance ID 8 using profile MIG 1g.5gb (ID 0) Successfully created compute instance ID 0 on GPU 0 GPU instance ID 9 using profile MIG 1g.5gb (ID 0) Successfully created compute instance ID 0 on GPU 0 GPU instance ID 10 using profile MIG 1g.5gb (ID 0) Successfully created compute instance ID 0 on GPU 0 GPU instance ID 11 using profile MIG 1g.5gb (ID 0) Successfully created compute instance ID 0 on GPU 0 GPU instance ID 12 using profile MIG 1g.5gb (ID 0) Successfully created compute instance ID 0 on GPU 0 GPU instance ID 13 using profile MIG 1g.5gb (ID 0) ``` ## View MIG Instances ``` root@server:~# nvidia-smi +-----------------------------------------------------------------------------+ \| MIG devices: \| +------------------+----------------------+-----------+-----------------------+ \| GPU GI CI MIG \| Memory-Usage \| Vol\| Shared \| \| ID ID Dev \| BAR1-Usage \| SM Unc\| CE ENC DEC OFA JPG\| \| \| \| ECC\| \| \|==================+======================+===========+=======================\| \| 0 7 0 0 \| 1MiB / 4864MiB \| 14 0 \| 1 0 0 0 0 \| \| \| 0MiB / 8191MiB \| \| \| +------------------+----------------------+-----------+-----------------------+ \| 0 8 0 1 \| 1MiB / 4864MiB \| 14 0 \| 1 0 0 0 0 \| \| \| 0MiB / 8191MiB \| \| \| +------------------+----------------------+-----------+-----------------------+ \| 0 9 0 2 \| 1MiB / 4864MiB \| 14 0 \| 1 0 0 0 0 \| \| \| 0MiB / 8191MiB \| \| \| +------------------+----------------------+-----------+-----------------------+ \| 0 10 0 3 \| 1MiB / 4864MiB \| 14 0 \| 1 0 0 0 0 \| \| \| 0MiB / 8191MiB \| \| \| +------------------+----------------------+-----------+-----------------------+ \| 0 11 0 4 \| 1MiB / 4864MiB \| 14 0 \| 1 0 0 0 0 \| \| \| 0MiB / 8191MiB \| \| \| +------------------+----------------------+-----------+-----------------------+ \| 0 12 0 5 \| 1MiB / 4864MiB \| 14 0 \| 1 0 0 0 0 \| \| \| 0MiB / 8191MiB \| \| \| +------------------+----------------------+-----------+-----------------------+ \| 0 13 0 6 \| 1MiB / 4864MiB \| 14 0 \| 1 0 0 0 0 \| \| \| 0MiB / 8191MiB \| \| \| +------------------+----------------------+-----------+-----------------------+ ``` ``` root@server:~# nvidia-smi -L GPU 0: A100-PCIE-40GB (UUID: GPU-0069414c-9f30-41f9-d5d8-87890423f0c4) MIG 1g.5gb Device 0: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4/7/0) MIG 1g.5gb Device 1: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4/8/0) MIG 1g.5gb Device 2: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4/9/0) MIG 1g.5gb Device 3: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4/10/0) MIG 1g.5gb Device 4: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4/11/0) MIG 1g.5gb Device 5: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4/12/0) MIG 1g.5gb Device 6: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4/13/0) ``` ## List GPU Instances `root@server:~# nvidia mig -lgi` ## List Compute Instances ``` root@server:~# nvidia mig -lci +-------------------------------------------------------+ \| Compute instances: \| \| GPU GPU Name Profile Instance \| \| Instance ID ID \| \| ID \| \|=======================================================\| \| 0 7 MIG 1g.5gb 0 0 \| +-------------------------------------------------------+ \| 0 8 MIG 1g.5gb 0 0 \| +-------------------------------------------------------+ \| 0 9 MIG 1g.5gb 0 0 \| +-------------------------------------------------------+ \| 0 11 MIG 1g.5gb 0 0 \| +-------------------------------------------------------+ \| 0 12 MIG 1g.5gb 0 0 \| +-------------------------------------------------------+ \| 0 13 MIG 1g.5gb 0 0 \| +-------------------------------------------------------+ \| 0 14 MIG 1g.5gb 0 0 \| +-------------------------------------------------------+ ``` ## Destroy Compute Instances ``` root@server:~# nvidia-smi mig -dci -i 3 Successfully destroyed compute instance ID 0 from GPU 0 GPU instance ID 7 Successfully destroyed compute instance ID 0 from GPU 0 GPU instance ID 8 Successfully destroyed compute instance ID 0 from GPU 0 GPU instance ID 9 Successfully destroyed compute instance ID 0 from GPU 0 GPU instance ID 10 Successfully destroyed compute instance ID 0 from GPU 0 GPU instance ID 11 Successfully destroyed compute instance ID 0 from GPU 0 GPU instance ID 12 Successfully destroyed compute instance ID 0 from GPU 0 GPU instance ID 13 ``` ## Destroy GPU Instances ``` root@server:~# nvidia-smi mig -dgi -i 3 Successfully destroyed GPU instance ID 7 from GPU 0 Successfully destroyed GPU instance ID 8 from GPU 0 Successfully destroyed GPU instance ID 9 from GPU 0 Successfully destroyed GPU instance ID 10 from GPU 0 Successfully destroyed GPU instance ID 11 from GPU 0 Successfully destroyed GPU instance ID 12 from GPU 0 Successfully destroyed GPU instance ID 13 from GPU 0 ``` ## Getting MIG Help ``` root@server:~# nvidia-smi mig -h mig -- Multi Instance GPU management. Usage: nvidia-smi mig [options] Options include: [-h \| --help]: Display help information. [-i \| --id]: Enumeration index, PCI bus ID or UUID. Provide comma separated values for more than one device. [-gi \| --gpu-instance-id]: GPU instance ID. Provide comma separated values for more than one GPU instance. [-ci \| --compute-instance-id]: Compute instance ID. Provide comma separated values for more than one compute instance. [-lgip \| --list-gpu-instance-profiles]: List supported GPU instance profiles. Option -i can be used to restrict the command to run on a specific GPU. [-lgipp \| --list-gpu-instance-possible-placements]: List possible GPU instance placements in the following format, {Start}:Size. Option -i can be used to restrict the command to run on a specific GPU. [-C \| --default-compute-instance]: Create compute instance with the default profile when used with the option to create a GPU instance (-cgi). [-cgi \| --create-gpu-instance]: Create GPU instances for the given profile tuples. A profile tuple consists of a profile name or ID and an optional placement specifier, which consists of a colon and a placement start index. Provide comma separated values for more than one profile tuple. Option -i can be used to restrict the command to run on a specific GPU. [-dgi \| --destroy-gpu-instance]: Destroy GPU instances. Options -i and -gi can be used individually or combined to restrict the command to run on a specific GPU or GPU instance. [-lgi \| --list-gpu-instances]: List GPU instances. Option -i can be used to restrict the command to run on a specific GPU. [-lcip \| --list-compute-instance-profiles]: List supported compute instance profiles. Options -i and -gi can be used individually or combined to restrict the command to run on a specific GPU or GPU instance. [-cci \| --create-compute-instance]: Create compute instance for the given profile name or IDs. Provide comma separated values for more than one profile. If no profile name or ID is given, then the default* compute instance profile ID will be used. Options -i and -gi can be used individually or combined to restrict the command to run on a specific GPU or GPU instance. [-dci \| --destroy-compute-instance]: Destroy compute instances. Options -i, -gi and -ci can be used individually or combined to restrict the command to run on a specific GPU or GPU instance or compute instance. [-lci \| --list-compute-instances]: List compute instances. Options -i and -gi can be used individually or combined to restrict the command to run on a specific GPU or GPU instance. ``` - [Articles, How-To, Troubleshooting, and News about GPU](https://www.seimaxim.com/kb/gpu) Post navigation [Front End Developer Interview Questions & Answers](https://www.seimaxim.com/kb/front-end-developer-interview-questions-answers) [![a100 gpu namd simulation](https://www.seimaxim.com/wp-content/uploads/2022/02/3d-patchwork-quilt-featured.jpg)](https://www.seimaxim.com/kb/gpu/namd-v3-and-nvidia-a100-gpus-can-deliver-up-to-9x-the-throughput) [NAMD v3 and NVIDIA A100 GPUs can deliver up to 9X the throughput](https://www.seimaxim.com/kb/gpu/namd-v3-and-nvidia-a100-gpus-can-deliver-up-to-9x-the-throughput) ### 3 comments 1. ![](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20width='38'%20height='38'%20viewBox='0%200%2038%2038'%3E%3C/svg%3E) [April 5, 2022 at 11:55 am](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat#comment-646) Rahul says: Do you also have cheatsheet on how MIG works in ESXi.. I am having hard time in making it work on ESXi, I see VMs doesn’t power on post attaching vGPU GRID profile to it [Log in to Reply](https://www.seimaxim.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.seimaxim.com%2Fkb%2Fgpu%2Fnvidia-a100-mig-cheat-sheat) - ![](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20width='38'%20height='38'%20viewBox='0%200%2038%2038'%3E%3C/svg%3E) [April 5, 2022 at 8:30 pm](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat#comment-647) [admin](https://www.seimaxim.com/) says: Hi, Have you installed GRID software in ESXi. Make sure you have Linux based OS like Ubuntu in VM. MIG is not supported in Windows. MIG also need to be enabled in GPU card like A100. [Log in to Reply](https://www.seimaxim.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.seimaxim.com%2Fkb%2Fgpu%2Fnvidia-a100-mig-cheat-sheat) - ![](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20width='38'%20height='38'%20viewBox='0%200%2038%2038'%3E%3C/svg%3E) [April 5, 2022 at 8:33 pm](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat#comment-648) [admin](https://www.seimaxim.com/) says: Hi, Secondly MIG cannot be enabled or configured in ESXi. Just enabled MIG compatible GPU and attach it to VM. MIG is enabled in VM using nvidia-smi. Also make sure NVIDIA license is installed in ESXi for using GPU. [Log in to Reply](https://www.seimaxim.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.seimaxim.com%2Fkb%2Fgpu%2Fnvidia-a100-mig-cheat-sheat) ### Leave a Reply [Cancel reply](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat#respond) You must be [logged in](https://www.seimaxim.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.seimaxim.com%2Fkb%2Fgpu%2Fnvidia-a100-mig-cheat-sheat) to post a comment. ###### Recent Posts - [GPU-Accelerated Data Analytics: Best Practices](https://www.seimaxim.com/kb/dedicated-servers/gpu-accelerated-data-analytics-best-practices) March 26, 2025 - [GPU Server powered VR: The Future of Simulation](https://www.seimaxim.com/kb/dedicated-servers/gpu-server-powered-vr-the-future-of-simulation) March 23, 2025 - [GPU-accelerated Autonomous Driving: Enabling Self-Driving](https://www.seimaxim.com/ai/gpu-accelerated-autonomous-driving-enabling-self-driving) March 14, 2025 - [Accelerated Cloud Computing using GPUs](https://www.seimaxim.com/technology/accelerated-cloud-computing-using-gpus) March 7, 2025 - [GPU-Powered Deep-learning applications](https://www.seimaxim.com/deep-learning/gpu-powered-deep-learning-applications) March 2, 2025 ###### PRODUCTS - [Dedicated Servers](https://www.seimaxim.com/dedicated-servers) - [Shared Hosting](https://www.seimaxim.com/shared-hosting) - [Domain Names](https://www.seimaxim.com/domain-names) - [VPS Hosting](https://www.seimaxim.com/vps-hosting) - [Proxies](https://www.seimaxim.com/?page_id=1987) - [Managed Services](https://www.seimaxim.com/services) - [Server Setup Services](https://www.seimaxim.com/platform-services) ![twitter](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20width='25'%20height='25'%20viewBox='0%200%2025%2025'%3E%3C/svg%3E) [![twitter](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20width='25'%20height='25'%20viewBox='0%200%2025%2025'%3E%3C/svg%3E)](https://x.com/seimaxim/) [![twitter](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20width='25'%20height='25'%20viewBox='0%200%2025%2025'%3E%3C/svg%3E)](https://facebook.com/seimaxim/) ###### LEGAL - [Terms and conditions](https://www.seimaxim.com/terms) - [GDPR](https://www.seimaxim.com/terms/gdpr) - [Abuse prevention](https://www.seimaxim.com/terms/abuse) - [SLA](https://www.seimaxim.com/terms/sla) - [DMCA](https://www.seimaxim.com/terms/dmca) - [Refund Policy](https://www.seimaxim.com/terms/refund) - [Accepted Use Policy](https://www.seimaxim.com/terms/aup) ###### ACCOUNT - [Dashboard](https://app.seimaxim.com/login) - [Create Account](https://app.seimaxim.com/register.php) - [Forgot Password?](https://app.seimaxim.com/pwreset.php) - [Contact Support](https://app.seimaxim.com/submitticket.php) - [Knowledgebase](https://www.seimaxim.com/kb) - [Blog](https://www.seimaxim.com/blog) - [About us](https://www.seimaxim.com/about) ###### RECENT POSTS - [GPU-Accelerated Data Analytics: Best Practices](https://www.seimaxim.com/kb/dedicated-servers/gpu-accelerated-data-analytics-best-practices) March 26, 2025 - [GPU Server powered VR: The Future of Simulation](https://www.seimaxim.com/kb/dedicated-servers/gpu-server-powered-vr-the-future-of-simulation) March 23, 2025 ![logo nullshock footer](data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20width='300'%20height='300'%20viewBox='0%200%20300%20300'%3E%3C/svg%3E) We accept Bitcoins, PayPal, Credit \\| Debit cards, GooglePay, Alipay, iDEAL, Webmoney, POLi, Russia Bank Transfer, Bancontact, Multibanco, and Global Banks transfers. The entirety of this site is protected by © Copyright 2018 - 2026 \\| SeiMaxim \\| All Rights Reserved. All trademarks and trade names shown are the property of their respective owners and no endorsement or derogation is intended or inferred. Offers subject to change, not combinable with all other offers. SeiMaxim reserves the right to cancel orders arising from pricing or other errors. Table of Contents [×](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat) - [Enable or Disable MIG](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat) - [List all GPU Instances](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat) - [Create GPU instances on MIG-enabled GPU](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat) - [Create Compute instances on a MIG-enabled GPU](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat) - [View MIG Instances](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat) - [List GPU Instances](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat) - [List Compute Instances](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat) - [Destroy Compute Instances](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat) - [Destroy GPU Instances](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat) - [Getting MIG Help](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat) [→ Index](https://www.seimaxim.com/kb/gpu/nvidia-a100-mig-cheat-sheat)
Readable Markdown	MIG is only compatible with Linux distributions that support CUDA 11/R450 or higher. It’s also a good idea to use the NVIDIA Datacenter Linux driver version 450.80.02 or higher. MIG is not supported on any Windows Pro or Server OS. The new Multi-Instance GPU (MIG) functionality allows NVIDIA Ampere-based GPUs (such as the [NVIDIA A100](https://www.seimaxim.com/dedicated-servers/gpu)) to be securely partitioned into up to seven independent GPU Instances for CUDA applications, giving different users separate GPU resources for optimal GPU use. This functionality is especially useful for workloads that do not completely utilize the GPU’s computing capabilities, and users may want to run many tasks in parallel to get the most out of their GPU. The following prerequisites and software versions are highly recommended when using supported GPUs in MIG mode. Only the GPUs and systems listed below are compatible with MIG. - NVIDIA driver 450.80.02 or later is required for CUDA 11. - Linux distributions that were supported by CUDA 11 If you are using Kubernetes or containers, make sure to use; - Version 2.5.0 or later of the NVIDIA Container Toolkit (nvidia-docker2) - v0.7.0 or newer of the NVIDIA K8s Device Plugin - Version 0.2.0 or later of NVIDIA gpu-feature-discovery NVIDIA Management Library (NVML) APIs or the nvidia-smi command-line interface can be used to manage MIG programmatically. Some of the nvidia-smi output in the following examples may be cropped for brevity to highlight the relevant sections of interest. ## Enable or Disable MIG To enable or disable MIG on all GPUs or a certain GPU, enable persistence mode on all GPUs. ``` nvidia-smi -pm 1 root@server:~# nvidia-smi -pm 1 Enabled persistence mode for GPU 00000000:31:00.0. Enabled persistence mode for GPU 00000000:CA:00.0. All done. ``` Then enable MIG by using the following command. `root@server:~# nvidia-smi -mig 1` ``` root@server:~# nvidia-smi Tue Feb 22 11:47:45 2022 +-----------------------------------------------------------------------------+ \| NVIDIA-SMI 510.39.01 Driver Version: 510.39.01 CUDA Version: 11.6 \| \|-------------------------------+----------------------+----------------------+ \| GPU Name Persistence-M\| Bus-Id Disp.A \| Volatile Uncorr. ECC \| \| Fan Temp Perf Pwr:Usage/Cap\| Memory-Usage \| GPU-Util Compute M. \| \| \| \| MIG M. \| \|===============================+======================+======================\| \| 0 NVIDIA A100 80G... On \| 00000000:31:00.0 Off \| On \| \| N/A 34C P0 41W / 300W \| 0MiB / 81920MiB \| N/A Default \| \| \| \| Enabled \| +-------------------------------+----------------------+----------------------+ \| 1 NVIDIA A100 80G... On \| 00000000:CA:00.0 Off \| On \| \| N/A 34C P0 43W / 300W \| 0MiB / 81920MiB \| N/A Default \| \| \| \| Enabled \| +-------------------------------+----------------------+----------------------+ +-----------------------------------------------------------------------------+ \| MIG devices: \| +------------------+----------------------+-----------+-----------------------+ \| GPU GI CI MIG \| Memory-Usage \| Vol\| Shared \| \| ID ID Dev \| BAR1-Usage \| SM Unc\| CE ENC DEC OFA JPG\| \| \| \| ECC\| \| \|==================+======================+===========+=======================\| \| No MIG devices found \| +-----------------------------------------------------------------------------+ +-----------------------------------------------------------------------------+ \| Processes: \| \| GPU GI CI PID Type Process name GPU Memory \| \| ID ID Usage \| \|=============================================================================\| \| No running processes found \| +-----------------------------------------------------------------------------+ ``` To disable MIG use the following command. `nvidia-smi -mig 0` ``` root@server:~# nvidia-smi -mig 0 Disabled MIG Mode for GPU 00000000:31:00.0 Disabled MIG Mode for GPU 00000000:CA:00.0 All done. ``` To enable or disable MIG on a specific device. ## List all GPU Instances ``` root@server:~# nvidia-smi mig -lgip +-----------------------------------------------------------------------------+ \| GPU instance profiles: \| \| GPU Name ID Instances Memory P2P SM DEC ENC \| \| Free/Total GiB CE JPEG OFA \| \|=============================================================================\| \| 0 MIG 1g.10gb 19 7/7 9.50 No 14 0 0 \| \| 1 0 0 \| +-----------------------------------------------------------------------------+ \| 0 MIG 1g.10gb+me 20 1/1 9.50 No 14 1 0 \| \| 1 1 1 \| +-----------------------------------------------------------------------------+ \| 0 MIG 2g.20gb 14 3/3 19.50 No 28 1 0 \| \| 2 0 0 \| +-----------------------------------------------------------------------------+ \| 0 MIG 3g.40gb 9 2/2 39.25 No 42 2 0 \| \| 3 0 0 \| +-----------------------------------------------------------------------------+ \| 0 MIG 4g.40gb 5 1/1 39.25 No 56 2 0 \| \| 4 0 0 \| +-----------------------------------------------------------------------------+ \| 0 MIG 7g.80gb 0 1/1 78.75 No 98 5 0 \| \| 7 1 1 \| +-----------------------------------------------------------------------------+ \| 1 MIG 1g.10gb 19 7/7 9.50 No 14 0 0 \| \| 1 0 0 \| +-----------------------------------------------------------------------------+ \| 1 MIG 1g.10gb+me 20 1/1 9.50 No 14 1 0 \| \| 1 1 1 \| +-----------------------------------------------------------------------------+ \| 1 MIG 2g.20gb 14 3/3 19.50 No 28 1 0 \| \| 2 0 0 \| +-----------------------------------------------------------------------------+ \| 1 MIG 3g.40gb 9 2/2 39.25 No 42 2 0 \| \| 3 0 0 \| +-----------------------------------------------------------------------------+ \| 1 MIG 4g.40gb 5 1/1 39.25 No 56 2 0 \| \| 4 0 0 \| +-----------------------------------------------------------------------------+ \| 1 MIG 7g.80gb 0 1/1 78.75 No 98 5 0 \| \| 7 1 1 \| +-----------------------------------------------------------------------------+ ``` ## Create GPU instances on MIG-enabled GPU ``` root@server:~# nvidia-smi mig -cgi 19,19,19,19,19,19,19 -i 3 Successfully created GPU instance ID 13 on GPU 0 using profile MIG 1g.5gb (ID 19) Successfully created GPU instance ID 11 on GPU 0 using profile MIG 1g.5gb (ID 19) Successfully created GPU instance ID 12 on GPU 0 using profile MIG 1g.5gb (ID 19) Successfully created GPU instance ID 7 on GPU 0 using profile MIG 1g.5gb (ID 19) Successfully created GPU instance ID 8 on GPU 0 using profile MIG 1g.5gb (ID 19) Successfully created GPU instance ID 9 on GPU 0 using profile MIG 1g.5gb (ID 19) Successfully created GPU instance ID 10 on GPU 0 using profile MIG 1g.5gb (ID 19) ``` ## Create Compute instances on a MIG-enabled GPU ``` root@server:~# nvidia-smi mig -cci -i 3 Successfully created compute instance ID 0 on GPU 0 GPU instance ID 7 using profile MIG 1g.5gb (ID 0) Successfully created compute instance ID 0 on GPU 0 GPU instance ID 8 using profile MIG 1g.5gb (ID 0) Successfully created compute instance ID 0 on GPU 0 GPU instance ID 9 using profile MIG 1g.5gb (ID 0) Successfully created compute instance ID 0 on GPU 0 GPU instance ID 10 using profile MIG 1g.5gb (ID 0) Successfully created compute instance ID 0 on GPU 0 GPU instance ID 11 using profile MIG 1g.5gb (ID 0) Successfully created compute instance ID 0 on GPU 0 GPU instance ID 12 using profile MIG 1g.5gb (ID 0) Successfully created compute instance ID 0 on GPU 0 GPU instance ID 13 using profile MIG 1g.5gb (ID 0) ``` ## View MIG Instances ``` root@server:~# nvidia-smi +-----------------------------------------------------------------------------+ \| MIG devices: \| +------------------+----------------------+-----------+-----------------------+ \| GPU GI CI MIG \| Memory-Usage \| Vol\| Shared \| \| ID ID Dev \| BAR1-Usage \| SM Unc\| CE ENC DEC OFA JPG\| \| \| \| ECC\| \| \|==================+======================+===========+=======================\| \| 0 7 0 0 \| 1MiB / 4864MiB \| 14 0 \| 1 0 0 0 0 \| \| \| 0MiB / 8191MiB \| \| \| +------------------+----------------------+-----------+-----------------------+ \| 0 8 0 1 \| 1MiB / 4864MiB \| 14 0 \| 1 0 0 0 0 \| \| \| 0MiB / 8191MiB \| \| \| +------------------+----------------------+-----------+-----------------------+ \| 0 9 0 2 \| 1MiB / 4864MiB \| 14 0 \| 1 0 0 0 0 \| \| \| 0MiB / 8191MiB \| \| \| +------------------+----------------------+-----------+-----------------------+ \| 0 10 0 3 \| 1MiB / 4864MiB \| 14 0 \| 1 0 0 0 0 \| \| \| 0MiB / 8191MiB \| \| \| +------------------+----------------------+-----------+-----------------------+ \| 0 11 0 4 \| 1MiB / 4864MiB \| 14 0 \| 1 0 0 0 0 \| \| \| 0MiB / 8191MiB \| \| \| +------------------+----------------------+-----------+-----------------------+ \| 0 12 0 5 \| 1MiB / 4864MiB \| 14 0 \| 1 0 0 0 0 \| \| \| 0MiB / 8191MiB \| \| \| +------------------+----------------------+-----------+-----------------------+ \| 0 13 0 6 \| 1MiB / 4864MiB \| 14 0 \| 1 0 0 0 0 \| \| \| 0MiB / 8191MiB \| \| \| +------------------+----------------------+-----------+-----------------------+ ``` ``` root@server:~# nvidia-smi -L GPU 0: A100-PCIE-40GB (UUID: GPU-0069414c-9f30-41f9-d5d8-87890423f0c4) MIG 1g.5gb Device 0: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4/7/0) MIG 1g.5gb Device 1: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4/8/0) MIG 1g.5gb Device 2: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4/9/0) MIG 1g.5gb Device 3: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4/10/0) MIG 1g.5gb Device 4: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4/11/0) MIG 1g.5gb Device 5: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4/12/0) MIG 1g.5gb Device 6: (UUID: MIG-GPU-0069414c-9f30-41f9-d5d8-87890423f0c4/13/0) ``` ## List GPU Instances `root@server:~# nvidia mig -lgi` ## List Compute Instances ``` root@server:~# nvidia mig -lci +-------------------------------------------------------+ \| Compute instances: \| \| GPU GPU Name Profile Instance \| \| Instance ID ID \| \| ID \| \|=======================================================\| \| 0 7 MIG 1g.5gb 0 0 \| +-------------------------------------------------------+ \| 0 8 MIG 1g.5gb 0 0 \| +-------------------------------------------------------+ \| 0 9 MIG 1g.5gb 0 0 \| +-------------------------------------------------------+ \| 0 11 MIG 1g.5gb 0 0 \| +-------------------------------------------------------+ \| 0 12 MIG 1g.5gb 0 0 \| +-------------------------------------------------------+ \| 0 13 MIG 1g.5gb 0 0 \| +-------------------------------------------------------+ \| 0 14 MIG 1g.5gb 0 0 \| +-------------------------------------------------------+ ``` ## Destroy Compute Instances ``` root@server:~# nvidia-smi mig -dci -i 3 Successfully destroyed compute instance ID 0 from GPU 0 GPU instance ID 7 Successfully destroyed compute instance ID 0 from GPU 0 GPU instance ID 8 Successfully destroyed compute instance ID 0 from GPU 0 GPU instance ID 9 Successfully destroyed compute instance ID 0 from GPU 0 GPU instance ID 10 Successfully destroyed compute instance ID 0 from GPU 0 GPU instance ID 11 Successfully destroyed compute instance ID 0 from GPU 0 GPU instance ID 12 Successfully destroyed compute instance ID 0 from GPU 0 GPU instance ID 13 ``` ## Destroy GPU Instances ``` root@server:~# nvidia-smi mig -dgi -i 3 Successfully destroyed GPU instance ID 7 from GPU 0 Successfully destroyed GPU instance ID 8 from GPU 0 Successfully destroyed GPU instance ID 9 from GPU 0 Successfully destroyed GPU instance ID 10 from GPU 0 Successfully destroyed GPU instance ID 11 from GPU 0 Successfully destroyed GPU instance ID 12 from GPU 0 Successfully destroyed GPU instance ID 13 from GPU 0 ``` ## Getting MIG Help ``` root@server:~# nvidia-smi mig -h mig -- Multi Instance GPU management. Usage: nvidia-smi mig [options] Options include: [-h \| --help]: Display help information. [-i \| --id]: Enumeration index, PCI bus ID or UUID. Provide comma separated values for more than one device. [-gi \| --gpu-instance-id]: GPU instance ID. Provide comma separated values for more than one GPU instance. [-ci \| --compute-instance-id]: Compute instance ID. Provide comma separated values for more than one compute instance. [-lgip \| --list-gpu-instance-profiles]: List supported GPU instance profiles. Option -i can be used to restrict the command to run on a specific GPU. [-lgipp \| --list-gpu-instance-possible-placements]: List possible GPU instance placements in the following format, {Start}:Size. Option -i can be used to restrict the command to run on a specific GPU. [-C \| --default-compute-instance]: Create compute instance with the default profile when used with the option to create a GPU instance (-cgi). [-cgi \| --create-gpu-instance]: Create GPU instances for the given profile tuples. A profile tuple consists of a profile name or ID and an optional placement specifier, which consists of a colon and a placement start index. Provide comma separated values for more than one profile tuple. Option -i can be used to restrict the command to run on a specific GPU. [-dgi \| --destroy-gpu-instance]: Destroy GPU instances. Options -i and -gi can be used individually or combined to restrict the command to run on a specific GPU or GPU instance. [-lgi \| --list-gpu-instances]: List GPU instances. Option -i can be used to restrict the command to run on a specific GPU. [-lcip \| --list-compute-instance-profiles]: List supported compute instance profiles. Options -i and -gi can be used individually or combined to restrict the command to run on a specific GPU or GPU instance. [-cci \| --create-compute-instance]: Create compute instance for the given profile name or IDs. Provide comma separated values for more than one profile. If no profile name or ID is given, then the default* compute instance profile ID will be used. Options -i and -gi can be used individually or combined to restrict the command to run on a specific GPU or GPU instance. [-dci \| --destroy-compute-instance]: Destroy compute instances. Options -i, -gi and -ci can be used individually or combined to restrict the command to run on a specific GPU or GPU instance or compute instance. [-lci \| --list-compute-instances]: List compute instances. Options -i and -gi can be used individually or combined to restrict the command to run on a specific GPU or GPU instance. ```
Shard	122 (laksa)
Root Hash	17739919741563513922
Unparsed URL	com,seimaxim!www,/kb/gpu/nvidia-a100-mig-cheat-sheat s443