Skip to content

Commit b2cf3ad

Browse files
author
Manika Dhiman
committed
acrolinx fixes
1 parent cc3b7c1 commit b2cf3ad

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

azure-local/manage/gpu-manage-via-partitioning.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ Consider the following limitations when using the GPU-P feature:
3333

3434
- Partitions are autoassigned to the VMs. You can't choose a specific partition for a specific VM.
3535

36-
- GPU partitioning on Azure Local supports live migration. However, the host and VMs must be on NVIDIA virtual GPU software version 18 and later. For more details, see [Microsoft Azure Local - NVIDIA Docs](https://docs.nvidia.com/vgpu/18.0/grid-vgpu-release-notes-microsoft-azure-stack-hci/index.html).
36+
- GPU partitioning on Azure Local supports live migration. However, the host and VMs must be on NVIDIA virtual GPU software version 18 and later. For more information, see [Microsoft Azure Local - NVIDIA Docs](https://docs.nvidia.com/vgpu/18.0/grid-vgpu-release-notes-microsoft-azure-stack-hci/index.html).
3737

3838
- You can partition your GPU using Azure Command-Line Interface (CLI). We recommend that you use Azure CLI to configure and assign GPU partitions. You must manually ensure that the homogeneous configuration is maintained for GPUs across all the machines in your system.
3939

@@ -43,7 +43,7 @@ Consider the following limitations when using the GPU-P feature:
4343

4444
## Attach a GPU during Azure Local VM creation
4545

46-
Follow the steps outlined in [Create Azure Local virtual machines](create-arc-virtual-machines.md?tabs=azurecli) and utilize the additional hardware profile details to add GPU to your create process. Run the following:
46+
Follow the steps outlined in [Create Azure Local virtual machines](create-arc-virtual-machines.md?tabs=azurecli) and utilize the extra hardware profile details to add GPU to your create process. Run the following:
4747

4848
```azurecli
4949
az stack-hci-vm create --name $vmName --resource-group $resource_group --admin-username $userName --admin-password $password --computer-name $computerName --image $imageName --location $location --authentication-type all --nics $nicName --custom-location $customLocationID --hardware-profile memory-mb="8192" processors="4" --storage-path-id $storagePathId --gpus GpuP
@@ -65,7 +65,7 @@ You can specify the partition size in the command, as shown below. Partition siz
6565
az stack-hci-vm gpu attach --resource-group "test-rg" --custom-location "test-location" --vm-name "test-vm" --gpus GpuP
6666
```
6767

68-
After attaching the GPU partition, the output will show the full VM details. You can confirm the GPUs were attached by reviewing the hardware profile `virtualMachineGPUs` section. The output will look as follows:
68+
After attaching the GPU partition, the output shows the full VM details. You can confirm the GPUs were attached by reviewing the hardware profile `virtualMachineGPUs` section. The output looks as follows:
6969

7070
```azurecli
7171
"properties":{
@@ -89,7 +89,7 @@ Use the following CLI command to detach the GPU:
8989
az stack-hci-vm gpu detach --resource-group "test-rg" --custom-location "test-location" --vm-name "test-vm" --gpus GpuP
9090
```
9191

92-
After detaching the GPU partition, the output will show the full VM details. You can confirm the GPUs were detached by reviewing the hardware profile `virtualMachineGPUs`. The output will look as follows:
92+
After detaching the GPU partition, the output shows the full VM details. You can confirm the GPUs were detached by reviewing the hardware profile `virtualMachineGPUs`. The output looks as follows:
9393

9494
```azurecli
9595
"properties":{

0 commit comments

Comments
 (0)