Skip to content

Commit 1489732

Browse files
vikancha-MSFT-zzvikancha-MSFT-zz
authored
Create hpccompute-amd-gpu-windows
1 parent 31d3ee6 commit 1489732

File tree

1 file changed

+175
-0
lines changed

1 file changed

+175
-0
lines changed

‎articles/virtual-machines/extensions/hpccompute-amd-gpu-windows

Lines changed: 175 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,175 @@
1+
---
2+
title: AMD GPU Driver Extension - Azure Windows VMs
3+
description: Microsoft Azure extension for installing AMD GPU Drivers on NVv4-series VMs running Windows.
4+
services: virtual-machines-windows
5+
documentationcenter: ''
6+
author: vikancha
7+
manager: jkabat
8+
editor: ''
9+
10+
ms.assetid:
11+
ms.service: virtual-machines-windows
12+
ms.topic: article
13+
ms.tgt_pltfrm: vm-windows
14+
ms.workload: infrastructure-services
15+
ms.date: 01/09/2019
16+
ms.author: akjosh
17+
18+
---
19+
# AMD GPU Driver Extension for Windows
20+
21+
## Overview
22+
23+
This extension installs AMD GPU drivers on Windows NVv4-series VMs. When you install AMD drivers using this extension, you are accepting and agreeing to the terms of the [AMD End-User License Agreement](www.amd.com/radeonsoftwarems). During the installation process, the VM may reboot to complete the driver setup.
24+
25+
Instructions on manual installation of the drivers and the current supported versions are available [here](https://docs.microsoft.com/azure/virtual-machines/windows/n-series-amd-driver-setup).
26+
27+
## Prerequisites
28+
29+
### Operating system
30+
31+
This extension supports the following OSs:
32+
33+
| Distribution | Version |
34+
|---|---|
35+
| Windows 10 EMS | Build 1903 |
36+
| Windows 10 | Build 1809 |
37+
| Windows Server 2016 | Core |
38+
| Windows Server 2019 | Core |
39+
40+
### Internet connectivity
41+
42+
The Microsoft Azure Extension for NVIDIA GPU Drivers requires that the target VM is connected to the internet and have access.
43+
44+
## Extension schema
45+
46+
The following JSON shows the schema for the extension.
47+
48+
```json
49+
{
50+
"name": "<myExtensionName>",
51+
"type": "extensions",
52+
"apiVersion": "2015-06-15",
53+
"location": "<location>",
54+
"dependsOn": [
55+
"[concat('Microsoft.Compute/virtualMachines/', <myVM>)]"
56+
],
57+
"properties": {
58+
"publisher": "Microsoft.HpcCompute.Edp",
59+
"type": "NvidiaGpuDriverWindows",
60+
"typeHandlerVersion": "1.2",
61+
"autoUpgradeMinorVersion": true,
62+
"settings": {
63+
}
64+
}
65+
}
66+
```
67+
68+
### Properties
69+
70+
| Name | Value / Example | Data Type |
71+
| ---- | ---- | ---- |
72+
| apiVersion | 2015-06-15 | date |
73+
| publisher | Microsoft.HpcCompute | string |
74+
| type | NvidiaGpuDriverWindows | string |
75+
| typeHandlerVersion | 1.2 | int |
76+
77+
78+
## Deployment
79+
80+
### Azure Resource Manager Template
81+
82+
Azure VM extensions can be deployed with Azure Resource Manager templates. Templates are ideal when deploying one or more virtual machines that require post deployment configuration.
83+
84+
The JSON configuration for a virtual machine extension can be nested inside the virtual machine resource, or placed at the root or top level of a Resource Manager JSON template. The placement of the JSON configuration affects the value of the resource name and type. For more information, see [Set name and type for child resources](../../azure-resource-manager/resource-manager-template-child-resource.md).
85+
86+
The following example assumes the extension is nested inside the virtual machine resource. When nesting the extension resource, the JSON is placed in the `"resources": []` object of the virtual machine.
87+
88+
```json
89+
{
90+
"name": "myExtensionName",
91+
"type": "extensions",
92+
"location": "[resourceGroup().location]",
93+
"apiVersion": "2015-06-15",
94+
"dependsOn": [
95+
"[concat('Microsoft.Compute/virtualMachines/', myVM)]"
96+
],
97+
"properties": {
98+
"publisher": "Microsoft.HpcCompute",
99+
"type": "AmdGpuDriverWindows",
100+
"typeHandlerVersion": "1.0",
101+
"autoUpgradeMinorVersion": true,
102+
"settings": {
103+
}
104+
}
105+
}
106+
```
107+
108+
### PowerShell
109+
110+
```powershell
111+
Set-AzVMExtension
112+
-ResourceGroupName "myResourceGroup" `
113+
-VMName "myVM" `
114+
-Location "southcentralus" `
115+
-Publisher "Microsoft.HpcCompute.Edp" `
116+
-ExtensionName "AmdGpuDriverWindows" `
117+
-ExtensionType "AmdGpuDriverWindows" `
118+
-TypeHandlerVersion 1.0 `
119+
-SettingString '{ `
120+
}'
121+
```
122+
123+
### Azure CLI
124+
125+
```azurecli
126+
az vm extension set `
127+
--resource-group myResourceGroup `
128+
--vm-name myVM `
129+
--name AmdGpuDriverWindows `
130+
--publisher Microsoft.HpcCompute.Edp `
131+
--version 1.0 `
132+
--settings '{ `
133+
}'
134+
```
135+
136+
## Troubleshoot and support
137+
138+
### Troubleshoot
139+
140+
Data about the state of extension deployments can be retrieved from the Azure portal, and by using Azure PowerShell and Azure CLI. To see the deployment state of extensions for a given VM, run the following command.
141+
142+
```powershell
143+
Get-AzVMExtension -ResourceGroupName myResourceGroup -VMName myVM -Name myExtensionName
144+
```
145+
146+
```azurecli
147+
az vm extension list --resource-group myResourceGroup --vm-name myVM -o table
148+
```
149+
150+
Extension execution output is logged to the following directory:
151+
152+
```cmd
153+
C:\WindowsAzure\Logs\Plugins\Microsoft.HpcCompute.NvidiaGpuDriverMicrosoft\
154+
```
155+
156+
### Error codes
157+
158+
| Error Code | Meaning | Possible Action |
159+
| :---: | --- | --- |
160+
| 0 | Operation successful |
161+
| 1 | Operation successful. Reboot required. |
162+
| 100 | Operation not supported or could not be completed. | Possible causes: PowerShell version not supported, VM size is not an N-series VM, Failure downloading data. Check the log files to determine cause of error. |
163+
| 240, 840 | Operation timeout. | Retry operation. |
164+
| -1 | Exception occurred. | Check the log files to determine cause of exception. |
165+
| -5x | Operation interrupted due to pending reboot. | Reboot VM. Installation will continue after reboot. Uninstall should be invoked manually. |
166+
167+
168+
### Support
169+
170+
If you need more help at any point in this article, you can contact the Azure experts on the [MSDN Azure and Stack Overflow forums](https://azure.microsoft.com/support/community/). Alternatively, you can file an Azure support incident. Go to the [Azure support site](https://azure.microsoft.com/support/options/) and select Get support. For information about using Azure Support, read the [Microsoft Azure support FAQ](https://azure.microsoft.com/support/faq/).
171+
172+
## Next steps
173+
For more information about extensions, see [Virtual machine extensions and features for Windows](features-windows.md).
174+
175+
For more information about N-series VMs, see [GPU optimized virtual machine sizes](../windows/sizes-gpu.md).

0 commit comments

Comments
 (0)