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: azure-stack/user/gpu-vms-about.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,9 +15,9 @@ ms.lastreviewed: 4/28/2021
15
15
16
16
# Graphics processing unit (GPU) virtual machine (VM) on Azure Stack Hub
17
17
18
-
This article describes which graphics processing unit (GPU) models are supported on an Azure Stack Hub integrated system. You can also find instructions on installing the drivers used with the GPUs. GPU support in Azure Stack Hub enables solutions such as artificial intelligence, training, inference, and data visualization. The AMD Radeon Instinct MI25 can be used to support graphic-intensive applications such as Autodesk AutoCAD.
18
+
This article describes which graphics processing unit (GPU) models are supported on an Azure Stack Hub integrated system. The article also contains instructions on installing the drivers used with the GPUs. GPU support in Azure Stack Hub enables solutions such as artificial intelligence, training, inference, and data visualization. The AMD Radeon Instinct MI25 can be used to support graphic-intensive applications such as Autodesk AutoCAD.
19
19
20
-
You can choose from three GPU models. They are available in NVIDIA V100, NVIDIA T4 and AMD MI25 GPUs. These physical GPUs align with the following Azure N-Series virtual machine (VM) types as follows:
20
+
You can choose from three GPU models. They are available in NVIDIA V100, NVIDIA T4, and AMD MI25 GPUs. These physical GPUs align with the following Azure N-Series virtual machine (VM) types as follows:
@@ -30,7 +30,7 @@ You can choose from three GPU models. They are available in NVIDIA V100, NVIDIA
30
30
31
31
## NCv3
32
32
33
-
NCv3-series VMs are powered by NVIDIA Tesla V100 GPUs. Customers can take advantage of these updated GPUs for traditional HPC workloads such as reservoir modeling, DNA sequencing, protein analysis, Monte Carlo simulations, and others.
33
+
NCv3-series VMs are powered by NVIDIA Tesla V100 GPUs. Customers can take advantage of these updated GPUs for traditional HPC workloads such as reservoir modeling, DNA sequencing, protein analysis, Monte Carlo simulations, and others.
34
34
35
35
| Size | vCPU | Memory: GiB | Temp storage (SSD) GiB | GPU | GPU memory: GiB | Max data disks | Max NICs |
36
36
|---|---|---|---|---|---|---|---|
@@ -40,7 +40,7 @@ NCv3-series VMs are powered by NVIDIA Tesla V100 GPUs. Customers can take advant
40
40
41
41
## NVv4
42
42
43
-
The NVv4-series virtual machines are powered by AMD Radeon Instinct MI25 GPUs. With NVv4-series Azure Stack Hub is introducing virtual machines with partial GPUs. This size can be used for GPU accelerated graphics applications and virtual desktops. NVv4 virtual machines currently support only Windows guest operating system.
43
+
The NVv4-series virtual machines are powered by AMD Radeon Instinct MI25 GPUs. With the NVv4-series, Azure Stack Hub introduces virtual machines with partial GPUs. This size can be used for GPU accelerated graphics applications and virtual desktops. NVv4 virtual machines currently support only the Windows guest operating system.
44
44
45
45
| Size | vCPU | Memory: GiB | Temp storage (SSD) GiB | GPU | GPU memory: GiB | Max data disks | Max NICs |
46
46
| --- | --- | --- | --- | --- | --- | --- | --- |
@@ -77,20 +77,20 @@ The NC_A100 series VMs are powered by NVIDIA Ampere A100 GPUs, the successor of
77
77
78
78
## Capacity planning
79
79
80
-
The Azure Stack Hub capacity planner has been updated to support GPU configurations. It is accessible on https://aka.ms/azstackcapacityplanner.
80
+
The Azure Stack Hub capacity planner was updated to support GPU configurations. [It's accessible here](https://aka.ms/azstackcapacityplanner).
81
81
82
82
## Adding GPUs on an existing Azure Stack Hub
83
83
84
-
Azure Stack Hub now supports adding GPUs to any existing system. To do this, execute stop-azurestack, run through the procedure of stop-azurestack, add GPUs, and then run **start-azurestack** until completion. If the system already had GPUs, then any previously created GPU VMs must be **stop-deallocated** and then **restarted**.
84
+
Azure Stack Hub now supports adding GPUs to any existing system. To add a GPU, run `stop-azurestack`, run through the procedure of `stop-azurestack`, add GPUs, and then run `start-azurestack` until completion. If the system already had GPUs, then any previously created GPU VMs must be `stop-deallocated` and then restarted.
85
85
86
-
## Patch and update, FRU behavior of VMs
86
+
## Patch and update, FRU behavior of VMs
87
87
88
88
GPU VMs undergo downtime during operations such as patch and update (PnU) and hardware replacement (FRU) of Azure Stack Hub. The following table covers the state of the VM as observed during these activities and the manual action you can do to make these VMs available after the operation.
| VM state | Unavailable during update. Can be made available with manual operation. VM is automatically online post update. | Unavailable during FRU. Can be made available with manual operation. VM needs to be brought back up after FRU|
93
-
| Manual operation | If the VM needs to be made available during the update, if there are available GPU partitions, the VM can be restarted from the portal by clicking the **Restart** button. VM automatically comes back up post update. | VM is not available during FRU. If there are available GPUs, VM may be stop-deallocated and restarted during FRU. Post FRU completion, VM needs to be stop-deallocated using the **Stop** button and started back up using the **Start** button.|
93
+
| Manual operation | If the VM needs to be made available during the update, if there are available GPU partitions, the VM can be restarted from the portal by clicking the **Restart** button. VM automatically comes back up post update. | VM is not available during FRU. If there are available GPUs, VM may be stop-deallocated and restarted during FRU. Post FRU completion, the VM must be `stop-deallocated` using the **Stop** button, then restarted using the **Start** button.|
94
94
95
95
## Guest driver installation
96
96
@@ -134,7 +134,7 @@ Use the PowerShell script in the previous section with the appropriate driver ty
134
134
135
135
#### Disconnected
136
136
137
-
Since the extension pulls the driver from a location on the internet, a VM that is disconnected from the external network cannot access it. You can [download the driver from the previous table](#amd-mi25) and upload to a storage account in your local network that's accessible to the VM.
137
+
Since the extension pulls the driver from a location on the internet, a VM that is disconnected from the external network can't access it. You can [download the driver from the previous table](#amd-mi25) and upload to a storage account in your local network that's accessible to the VM.
138
138
139
139
Add the AMD driver to a storage account and specify the URL to that account in `Settings`. These settings must be used in the **Set-AzureRMVMExtension** cmdlet. For example:
140
140
@@ -161,7 +161,7 @@ $Settings = @{
161
161
162
162
### Use case: compute/CUDA - Connected
163
163
164
-
CUDA drivers do not need a license server and do not need modified settings.
164
+
CUDA drivers don't need a license server and don't need modified settings.
165
165
166
166
### Use case: compute/CUDA - Disconnected
167
167
@@ -184,8 +184,8 @@ You must reference some URLs for your settings:
184
184
185
185
| URL | Notes |
186
186
| --- | --- |
187
-
| PUBKEY_URL | The PUBKEY_URL is the public key for the Nvidia driver repository not for the Linux VM. It is used to install driver for Ubuntu. |
188
-
| DRIVER_URL | DRIVER_URL is the URL to download the Nvidia driver's repository information and it is added to the Linux VM's list of repos. |
187
+
| PUBKEY_URL | The PUBKEY_URL is the public key for the Nvidia driver repository not for the Linux VM. It's used to install driver for Ubuntu. |
188
+
| DRIVER_URL | DRIVER_URL is the URL to download the Nvidia driver's repository information and is added to the Linux VM's list of repos. |
0 commit comments