You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/adminguide/virtual_machines.rst
+42-1Lines changed: 42 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1345,7 +1345,40 @@ CloudStack follows the below sequence of operations to provide GPU/vGPU support
1345
1345
GPU resources are released automatically when you stop a VM. Once the destroy VM is successful, CloudStack will make a resource call to the host to get the remaining GPU capacity in the card and update the database accordingly.
1346
1346
1347
1347
1348
-
1348
+
1349
+
VM Instance Settings
1350
+
~~~~~~~~~~~~~~~~~~~~
1351
+
1352
+
Each user VM has a set of "details" associated with it (as visible via listVirtualMachine API call) - those "details" are shown on the "Settings" tab of the VM in the GUI (words "setting(s)" and "detail(s)" are here used interchangeably).
1353
+
1354
+
The Settings tab is always present/visible, but settings can be changed only when the VM is in a Stopped state.
1355
+
Some VM details/settings can be hidden via "user.vm.blacklisted.details" global setting (you can find below the list of those hidden by default).
1356
+
1357
+
When adding a new setting or modifying the existing ones, setting names are shown/offered in a drop-down list, as well as their possible values (with the exception of boolean or numerical values).
1358
+
1359
+
Read-only details/settings that are hidden by default:
1360
+
1361
+
- rootdisksize
1362
+
- cpuOvercommitRatio
1363
+
- memoryOvercommitRatio
1364
+
- Message.ReservedCapacityFreed.Flag
1365
+
1366
+
An example list of settings as well as their possible values are shown on the images below:
0 commit comments