Skip to content

Commit e2dcc09

Browse files
committed
added suggestions
1 parent 5aeba4d commit e2dcc09

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/openshift/howto-gpu-workloads.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: johnmarc
66
ms.service: azure-redhat-openshift
77
keywords: aro, gpu, openshift, red hat
88
ms.topic: how-to
9-
ms.date: 12/15/2023
9+
ms.date: 29/11/2024
1010
ms.custom: template-how-to
1111
---
1212

@@ -190,16 +190,16 @@ ARO uses Kubernetes MachineSet to create machine sets. The procedure below expla
190190

191191
#### Ensure the correct SKU is set
192192

193-
Depending on the image used for the machine set, both values for `image.sku` and `image.version` must be set accordingly. This is to ensure if generation 1 or 2 virtual machine for Hyper-V will be used. More details [here](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/plan/should-i-create-a-generation-1-or-2-virtual-machine-in-hyper-v).
193+
Depending on the image used for the machine set, both values for `image.sku` and `image.version` must be set accordingly. This is to ensure if generation 1 or 2 virtual machine for Hyper-V will be used. See [here](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/plan/should-i-create-a-generation-1-or-2-virtual-machine-in-hyper-v) for more information.
194194

195195
Example:
196196

197-
If using `Standard_NC4as_T4_v3` it is supported both versions, as mentioned at [Feature support](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/gpu-accelerated/ncast4v3-series?tabs=sizebasic#feature-support). So no changes is required.
197+
If using `Standard_NC4as_T4_v3`, both versions are supported. As mentioned in [Feature support](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/gpu-accelerated/ncast4v3-series?tabs=sizebasic#feature-support). In this case, no changes are required.
198198

199199
If using `Standard_NC24ads_A100_v4`, only **Generation 2 VM** is [supported](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/gpu-accelerated/nca100v4-series?tabs=sizebasic#feature-support).
200200
In this case, the `image.sku` value must follow the equivalent `v2` version of the image that corresponds to the cluster's original `image.sku`. For this example, the value will be `v410-v2`.
201201
202-
This can be found using below command:
202+
This can be found using the following command:
203203
204204
```bash
205205
az vm image list --architecture x64 -o table --all --offer aro4 --publisher azureopenshift
@@ -214,7 +214,7 @@ v410-v2 410.84.20220125
214214
aro_410 410.84.20220125
215215
```
216216
217-
If the cluster was created with the base SKU image `aro_410`, and the same value is kept in the machine set it will fail with error below:
217+
If the cluster was created with the base SKU image `aro_410`, and the same value is kept in the machine set, it will fail with the following error:
218218
```
219219
failure sending request for machine myworkernode: cannot create vm: compute.VirtualMachinesClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="BadRequest" Message="The selected VM size 'Standard_NC24ads_A100_v4' cannot boot Hypervisor Generation '1'.
220220
```

0 commit comments

Comments
 (0)