All Products
Search
Document Center

Elastic GPU Service:Install the GRID driver on a vGPU-accelerated Linux instance

Last Updated:Nov 21, 2025

GPU-accelerated instances installed with the NVIDIA GRID driver can deliver high-performance computing capabilities or provide smoother graphics display effects in specific scenarios. The scenarios include general-purpose computing scenarios such as AI scenarios, and graphics acceleration scenarios such as Open Graphics Library (OpenGL), Direct3D, and cloud gaming scenarios. This topic describes how to install the GRID driver on a vGPU-accelerated Linux instance using Cloud Assistant.

Note

Before you use Cloud Assistant to install the GRID driver, we recommend that you familiarize yourself with the concepts of Cloud Assistant. For more information, see Cloud Assistant overview. The system automatically installs Cloud Assistant plug-ins when you create GPU-accelerated instances.

Supported instances

You can use Cloud Assistant to install the GRID driver only on vGPU-accelerated Linux instances that belong to the sgn8ia, vgn6i-vws, vgn7i-vws, and sgn7i-vws instance families. For more information, see vGPU-accelerated instance families (vgn and sgn series). The following table lists the GRID driver versions and CUDA versions that can be installed on the instances.

Instance family

Public image version

NVIDIA GRID driver version

CUDA version

sgn8ia

  • Alibaba Cloud Linux 2 and Alibaba Cloud Linux 3

  • Ubuntu 22.04, Ubuntu 20.04, and Ubuntu 18.04

  • CentOS 8.x and CentOS 7.x

535.183.06

12.2

vgn6i-vws,

vgn7i-vws, and sgn7i-vws

  • Alibaba Cloud Linux 2 and Alibaba Cloud Linux 3

  • Ubuntu 22.04, Ubuntu 20.04, and Ubuntu 18.04

  • CentOS 8.x and CentOS 7.x

470.256.03

11.4

Important

GPU-accelerated compute-optimized Linux instances such as gn7i, gn6i, ebmgn7i, and ebmgn6i instances support graphics acceleration using official NVIDIA drivers. You do not need to install the GRID driver on the instances. For more information, see GPU-accelerated compute-optimized instance families (gn, ebm, and scc series).

Procedure

  1. Log on to the ECS console.

  2. In the left-side navigation pane, choose Maintenance & Monitoring > Cloud Assistant.

  3. In the top navigation bar, select the region where the desired instance resides.

    地域.png

  4. On the ECS Instances tab, find the desired instance and click Run Command in the Actions column.

    linux.png

  5. In the Create Command panel, configure parameters in the Command Information section.

    The following section describes the main parameters. Use default values for other parameters. For more information, see Create a command in the ECS console.

    Important

    Configure the parameters based on the values that are provided in the following section. Otherwise, Cloud Assistant may fail to run the command.

    linux命令.png

    • Command Type: Select the command type. In this example, Shell is selected.

    • Command content: Paste the following command. For more information about sample shell commands, see View the system configurations of ECS instances.

      • Cloud Assistant command for a sgn8ia instance:

        if acs-plugin-manager --list --local | grep gpu_grid_driver_install > /dev/null 2>&1
        then
            acs-plugin-manager --remove --plugin gpu_grid_driver_install
        fi
        
        acs-plugin-manager --exec --plugin gpu_grid_driver_install
      • Cloud Assistant command for a vgn6i-vws, vgn7i-vws, or sgn7i-vws instance:

        if acs-plugin-manager --list --local | grep grid_driver_install > /dev/null 2>&1
        then
            acs-plugin-manager --remove --plugin grid_driver_install
        fi
        
        acs-plugin-manager --exec --plugin grid_driver_install
    • Timeout: Specify the timeout period for running the command. When the command execution times out, Cloud Assistant forcefully stops the execution process. In this example, the value is set to 600.

      Note

      The value of the Timeout parameter must be a positive integer from 10 to 86,400. Unit: seconds. 86,400 seconds is equal to 24 hours.

  6. Click Run to run the Cloud Assistant command to install the GRID driver.

    Wait until the command execution is complete. Then, view the execution result on the Instances tab in the execution details panel.

    Important

    If another GRID driver version is already installed on the instance, Cloud Assistant automatically uninstalls the GRID driver version and installs the latest GRID driver version.

    linux安装成功.png

  7. Connect to the GPU-accelerated instance.

    For more information, see Use Workbench to log on to a Linux instance.

  8. Run the following command to check whether the GRID driver is installed:

    nvidia-smi

    If the following command output is displayed, the GRID driver is upgraded or installed.

    SMI.jpg

Test and verify

This section provides an example on how to use an OpenGL Extension to the X Window System (GLX) test program to verify the graphics acceleration effect on an instance that has the GRID driver installed. In this example, an instance that runs Ubuntu 18.04 64-bit is used.

  1. Prepare an environment that is used to test the graphics acceleration effect.

    1. Run the following command to install x11vnc:

      apt-get install x11vnc
    2. Run the lspci | grep NVIDIA command to query the GPU BusID.

      In this example, the GPU BusID is 00:07.0.

    3. Configure the X Server environment and restart the system.

      1. Run the nvidia-xconfig --enable-all-gpus --separate-x-screens command.

      2. Edit /etc/X11/xorg.conf. In the Section "Device" segment, add the GPU BusID. For example, add BusID "PCI:0:7:0".重启.png

      3. Run the reboot command to restart the system.

  2. Run the following command to install the GLX test program:

    apt-get install mesa-utils                    
  3. Run the startx command to start X Server.

    • If the startx command is not available, run the apt-get install xinit command to install it.

    • When you run the startx command, the message hostname: Name or service not known may be displayed. This message does not affect the X Server startup. To resolve this, run the hostname command to obtain the hostname, and then edit the /etc/hosts file. Replace the hostname value after 127.0.0.1 with the local hostname.启动.png

  4. Start an SSH terminal session on a client and run the following command to start x11vnc:

    x11vnc -display :1

    If the following command output is displayed, x11vnc is started. In this case, you can connect to the instance using a Virtual Network Computing (VNC) remote access application, such as VNC Viewer.连接.png

  5. Log on to the ECS console and configure a security group rule that allows inbound traffic on TCP port 5900 for the instance.

    For more information, see Add a security group rule.

  6. On your local host, use a VNC remote connection application, such as VNC Viewer, to connect to the instance at <Public IP address of the instance>:5900. After you connect, the KDE desktop is displayed.

  7. Use the glxinfo command to view the configurations supported by the current GRID driver.

    1. Start a new terminal session on the SSH client.

    2. Run the export DISPLAY=:1 command.

    3. Run the glxinfo -t command to list the configurations supported by the current GRID driver.

  8. Test the GRID driver using the glxgears command.

    1. On the KDE desktop, right-click the desktop and select Run Command.

    2. Run the glxgears command to start the gear graphics test program.

      If the following window appears, the GRID driver works as expected.驱动正常.png

References