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 b6830bb0 Update GPU docs (#542)
b6830bb0 is described below
commit b6830bb0057b80445891630e7312e9ac6f5322bd
Author: Vishesh <vishes...@gmail.com>
AuthorDate: Mon Aug 18 16:33:28 2025 +0530
Update GPU docs (#542)
---
source/adminguide/hosts.rst | 4 ++--
source/adminguide/service_offerings.rst | 4 +++-
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/source/adminguide/hosts.rst b/source/adminguide/hosts.rst
index f1754b20..f5aa868a 100644
--- a/source/adminguide/hosts.rst
+++ b/source/adminguide/hosts.rst
@@ -246,7 +246,7 @@ devices on a KVM host. The script is located in the
``/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.
+``lspci`` & ``xmlstarlet`` should be installed on the host.
.. parsed-literal::
@@ -266,7 +266,7 @@ and their status on the host. So, for the discovery to be
successful, the
=============================== ==================
=======================
Legacy: SR-IOV not supported `mdev` Yes
SR-IOV supported `mdev` Yes
- SR-IOV supported `Vendor specific` No
+ SR-IOV supported `Vendor specific` Yes
Multi Instance GPU No
=============================== ==================
=======================
diff --git a/source/adminguide/service_offerings.rst
b/source/adminguide/service_offerings.rst
index 87ede814..bd76e31c 100644
--- a/source/adminguide/service_offerings.rst
+++ b/source/adminguide/service_offerings.rst
@@ -306,7 +306,9 @@ To create a new compute offering:
- **GPU Display**: Whether to use the GPU device attached to the guest
instance for display.
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.
+ use CPVM for display. To set the ``video.hardware`` setting, navigate to
+ the instance's details page in the CloudStack UI, click on the
+ "Settings" tab, and add/or update the ``video.hardware`` setting to
``none``.
- **Public**: Indicate whether the compute offering should be
available to all domains or only some domains. Choose Yes to make it
