This is an automated email from the ASF dual-hosted git repository.

sureshanaparti pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/cloudstack-documentation.git


The following commit(s) were added to refs/heads/main by this push:
     new 29bb051a Update GPU related docs (#538)
29bb051a is described below

commit 29bb051a4ad6515f9d5edb099a9545b4538e1351
Author: Vishesh <vishes...@gmail.com>
AuthorDate: Thu Aug 14 19:06:14 2025 +0530

    Update GPU related docs (#538)
---
 source/adminguide/hosts.rst             | 28 ++++++++++++++++++++++++++--
 source/adminguide/service_offerings.rst |  4 +++-
 2 files changed, 29 insertions(+), 3 deletions(-)

diff --git a/source/adminguide/hosts.rst b/source/adminguide/hosts.rst
index 4e73a636..f1754b20 100644
--- a/source/adminguide/hosts.rst
+++ b/source/adminguide/hosts.rst
@@ -243,10 +243,34 @@ the host.
 
 The cloudstack agent uses the ``gpudiscovery.sh`` script to discover the GPU
 devices on a KVM host. The script is located in the
-``/usr/share/cloudstack-common/scripts/vm/`` directory on the host.
+``/usr/share/cloudstack-common/scripts/vm/`` directory on the host. The script
+relies on the ``lspci`` & ``xmlstarlet`` command to discover the GPU devices
+and their status on the host. So, for the discovery to be successful, the
+``lspci`` & ``xmlstarlet`` commands needs to be installed on the host.
+
+   .. parsed-literal::
+
+      dnf install pciutils xmlstarlet
+
+   .. parsed-literal::
+
+      sudo apt install pciutils xmlstarlet
 
 .. note::
-   The script can be run manually to debug the discovery of the GPU devices on 
a host.
+   The following table shows the compatibility matrix for NVIDIA vGPU types 
with CloudStack:
+
+   .. cssclass:: table-striped table-bordered table-hover
+
+   ===============================   ==================   
=======================
+   NVIDIA vGPU Type                  VFIO Framework       Supported in 
CloudStack
+   ===============================   ==================   
=======================
+   Legacy: SR-IOV not supported      `mdev`                 Yes
+   SR-IOV supported                  `mdev`                 Yes
+   SR-IOV supported                  `Vendor specific`      No
+   Multi Instance GPU                                       No
+   ===============================   ==================   
=======================
+
+   The script can also be run manually to debug the discovery of the GPU 
devices on a host.
 
    .. parsed-literal::
 
diff --git a/source/adminguide/service_offerings.rst 
b/source/adminguide/service_offerings.rst
index 4f7d1eb8..87ede814 100644
--- a/source/adminguide/service_offerings.rst
+++ b/source/adminguide/service_offerings.rst
@@ -304,7 +304,9 @@ To create a new compute offering:
       This is applicable only for KVM hypervisor.
 
    -  **GPU Display**: Whether to use the GPU device attached to the guest 
instance for display.
-      This is applicable only for KVM hypervisor.
+      This is applicable only for KVM hypervisor. Depending on the OS and 
display configuration,
+      the user might need to set ``video.hardware`` to ``none`` in the 
instance's settings to
+      use CPVM for display.
 
    -  **Public**: Indicate whether the compute offering should be
       available to all domains or only some domains. Choose Yes to make it

Reply via email to