Skip to content

Commit d5d00f1

Browse files
committed
Fixes
1 parent 8e7cc61 commit d5d00f1

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

azure-stack/operator/manage-gpu-capacity.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to add GPUs to an existing Azure Stack Hub system.
44
author: sethmanheim
55
ms.author: sethm
66
ms.topic: how-to
7-
ms.date: 05/17/2021
7+
ms.date: 04/21/2025
88
ms.custom: template-how-to
99
---
1010

@@ -23,7 +23,7 @@ The following flow shows the general process to add memory to each scale unit no
2323

2424
:::image type="content" source="media/manage-gpu-capacity/add-memory-process.png" alt-text="Add GPU capacity flow":::
2525

26-
Each GPU VM can only use GPUs from a single node, and GPU VMs are not automatically load balanced. For example, you have 4 nodes and 2 GPUs on each node, and you create 4 VMs with 1 GPU for each VM. Each VM can exist on a different node. If that happens, any single node will only have 1 available GPU left. From the portal, you can see that there are 4 GPUs available. However, if you try to create a VM with 2 GPUs, it fails with insufficient GPU capacity, because no single node has 2 GPUs available. The solution is to create the VMs with 2 GPUs first.
26+
Each GPU VM can only use GPUs from a single node, and GPU VMs are not automatically load balanced. For example, you have 4 nodes and 2 GPUs on each node, and you create 4 VMs with 1 GPU for each VM. Each VM can exist on a different node. If that happens, any single node only has 1 available GPU left. From the portal, you can see that there are 4 GPUs available. However, if you try to create a VM with 2 GPUs, it fails with insufficient GPU capacity, because no single node has 2 GPUs available. The solution is to create the VMs with 2 GPUs first.
2727

2828
## Upgrade GPUs or add to an existing node
2929

@@ -38,9 +38,9 @@ The following section provides a high-level overview of the process to add a GPU
3838

3939
## Change GPU partition size
4040

41-
Azure Stack Hub supports GPU partitioning for the AMD MI25. With GPU partitioning, you can increase the density of virtual machines using a virtual GPU instance. You can change the partition size to meet specific workload requirements. By default, Azure Stack Hub uses the largest partition size (1/8) to provide the highest possible density with a 2 GB frame buffer. This is useful for workloads that require accelerated graphics applications and virtual desktops.
41+
Azure Stack Hub supports GPU partitioning for the AMD MI25. With GPU partitioning, you can increase the density of virtual machines using a virtual GPU instance. You can change the partition size to meet specific workload requirements. By default, Azure Stack Hub uses the largest partition size (1/8) to provide the highest possible density with a 2 GB frame buffer. This partitioning is useful for workloads that require accelerated graphics applications and virtual desktops.
4242

43-
To change the partition size, do the following:
43+
To change the partition size, perform the following steps:
4444

4545
1. Deallocate all VMs that are currently using a GPU.
4646
1. Ensure that the [PowerShell Az module](powershell-install-az-module.md) for Azure Stack Hub is installed.

azure-stack/user/gpu-vms-about.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -126,7 +126,7 @@ Set-AzVMExtension -Location $Location `
126126
-Verbose
127127
```
128128

129-
Depending on the OS, type and connectivity of your Azure Stack Hub GPU VM, you must replace these values with the settings below.
129+
Depending on the OS, type, and connectivity of your Azure Stack Hub GPU VM, you must replace these values with the following settings.
130130

131131
### AMD MI25
132132

0 commit comments

Comments
 (0)