CloudStack assumes that the operator has configured the GPU devices correctly on the host. The role of CloudStack is just to discover the devices on the host and assign/unassign them to the Instance.
Admins will need to build custom templates with GPU tools/drivers installed to have their users effectively use Instances with GPUs.
Apart from this, the following Instance operations for GPUs, are unsupported (as of now):
- Instance snapshot with memory for GPU enabled Instance is not supported.
- Live Migration of GPU enabled VM Instance is not supported. However, cold VM Instance migration would be possible by stoping stopping the VMInstance, optionally migrating its disks and starting it on another compatible GPU-enabled host. We have added framework level support for live migration of VMs Instances with vGPUs, but we are unable to verify due to unavailability of hardware.
- Dynamic scaling of VMs Instances with GPU attached

High-Level Overview

...

The configuration settings changes below, are incorporated.

Configuration	Description	Default Value	Scope
gpu.detach.on.stop	Whether to detach GPU devices from

VM

Instance on stop or keep them allocated	false	Domain
max.account.gpus	The default maximum number of GPU devices that can be used for an account	20	Global
max.domain.gpus	The default maximum number of GPU devices that can be used for a domain	20	Global
max.project.gpus	The default maximum number of GPU devices that can be used for a project	20	Global

Usage Instructions

As part of the GPU integration, we need to configure the GPU on the host and install or upgrade the CloudStack packages with GPU support.

...