Skip to content

Commit bcb3de1

Browse files
committed
Azure Arc rebranding: non-Arc VMs
1 parent 9d0bcdd commit bcb3de1

File tree

5 files changed

+16
-16
lines changed

5 files changed

+16
-16
lines changed
Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
author: alkohli
33
ms.topic: include
4-
ms.date: 01/08/2025
4+
ms.date: 03/17/2025
55
ms.author: alkohli
66

77
---
88

99
> [!NOTE]
10-
> The recommended way to create and manage VMs on Azure Local is using the [Azure Arc control plane](../manage/azure-arc-vm-management-overview.md). However, since the functionality described in this article is not yet provided by Azure Arc, you can use Windows Admin Center or PowerShell as described below. Note that VMs created this way aren't Arc-enabled VMs. They have limited manageability from the Azure Arc control plane and fewer Azure Hybrid Benefits, such as no free use of Azure Update Manager.
10+
> The recommended way to create and manage VMs on Azure Local is using [Azure Local VM management](../manage/azure-arc-vm-management-overview.md). However, since the functionality described in this article isn't yet provided by Azure Local VM management, you can use Windows Admin Center or PowerShell as described below. Note however that Azure Local VMs created this way aren't enabled by Azure Arc. They have limited manageability from the Azure Local VM management plane and fewer Azure Hybrid Benefits, such as no free use of Azure Update Manager.

azure-local/includes/hci-arc-vm.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
---
22
author: alkohli
33
ms.topic: include
4-
ms.date: 01/08/2025
4+
ms.date: 03/17/2025
55
ms.author: alkohli
66

77
---
88

99
<!--- Link must remain site-relative to prevent build issues with incoming includes from the windowsserverdocs repo --->
1010

1111
> [!NOTE]
12-
> The recommended way to create and manage VMs on Azure Local is using the [Azure Arc control plane](/azure-stack/hci/manage/azure-arc-vm-management-overview). Use the mechanism described below to manage your VMs only if you need functionality that is not available in Azure Arc VMs.
12+
> The recommended way to create and manage VMs on Azure Local is using [Azure Local VM management](/azure-stack/hci/manage/azure-arc-vm-management-overview). Use the mechanism described below to manage your VMs only if you need functionality that is not available in Azure Local VMs enabled by Azure Arc.

azure-local/manage/attach-gpu-to-linux-vm.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: alkohli
66
ms.topic: how-to
77
ms.service: azure-local
88
ms.custom: linux-related-content
9-
ms.date: 10/23/2024
9+
ms.date: 03/17/2025
1010
---
1111

1212
# Attaching a GPU to an Ubuntu Linux VM on Azure Local

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -5,14 +5,14 @@ author: alkohli
55
ms.author: alkohli
66
ms.topic: how-to
77
ms.service: azure-local
8-
ms.date: 10/21/2024
8+
ms.date: 03/17/2025
99
---
1010

1111
# Manage GPUs via Discrete Device Assignment (preview)
1212

1313
[!INCLUDE [applies-to](../includes/hci-applies-to-23h2.md)]
1414

15-
This article describes how to manage GPU DDA with Arc virtual machines (VMs) on Azure Local. For GPU DDA management on AKS enabled by Azure Arc, see [Use GPUs for compute-intensive workloads](/azure/aks/hybrid/deploy-gpu-node-pool#create-a-new-workload-cluster-with-a-gpu-enabled-node-pool).
15+
This article describes how to manage GPU DDA with Azure Local virtual machines (VMs) enabled by Azure Arc. For GPU DDA management on Azure Kubernetes Service (AKS) enabled by Azure Arc, see [Use GPUs for compute-intensive workloads](/azure/aks/hybrid/deploy-gpu-node-pool#create-a-new-workload-cluster-with-a-gpu-enabled-node-pool).
1616

1717
Discrete Device Assignment (DDA) allows you to dedicate a physical graphical processing unit (GPU) to your workload. In a DDA deployment, virtualized workloads run on the native driver and typically have full access to the GPU's functionality. DDA offers the highest level of app compatibility and potential performance.
1818

@@ -24,17 +24,17 @@ Discrete Device Assignment (DDA) allows you to dedicate a physical graphical pro
2424

2525
Before you begin, satisfy the following prerequisites:
2626

27-
- Follow the setup instructions found at [Prepare GPUs for Azure Local](./gpu-manage-via-device.md) to prepare your Azure Local and Arc VMs, and to ensure that your GPUs are prepared for DDA.
27+
- Follow the setup instructions found at [Prepare GPUs for Azure Local](./gpu-manage-via-device.md) to prepare your Azure Local VMs, and to ensure that your GPUs are prepared for DDA.
2828

29-
## Attach a GPU during Arc VM creation
29+
## Attach a GPU during Azure Local VM creation
3030

31-
Follow the steps outlined in [Create Arc virtual machines on Azure Local](create-arc-virtual-machines.md?tabs=azurecli) and utilize the additional hardware profile details to add GPU to your create process.
31+
Follow the steps outlined in [Create virtual machines on Azure Local](create-arc-virtual-machines.md?tabs=azurecli) and utilize the additional hardware profile details to add GPU to your create process.
3232

3333
```azurecli
3434
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 GpuDDA
3535
```
3636

37-
## Attach a GPU after Arc VM creation
37+
## Attach a GPU after VM creation
3838

3939
Use the following CLI command to attach the GPU:
4040

azure-local/manage/gpu-preparation.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,15 +4,15 @@ description: Learn how to prepare GPUs for an Azure Local instance.
44
author: alkohli
55
ms.author: alkohli
66
ms.topic: how-to
7-
ms.date: 03/03/2025
7+
ms.date: 03/17/2025
88
ms.service: azure-local
99
---
1010

1111
# Prepare GPUs for Azure Local
1212

1313
[!INCLUDE [applies-to](../includes/hci-applies-to-23h2.md)]
1414

15-
This article describes how to prepare graphical processing units (GPUs) on your Azure Local instance for computation-intensive workloads running on Arc virtual machines (VMs) and AKS enabled by Azure Arc. GPUs are used for computation-intensive workloads such as machine learning and deep learning.
15+
This article describes how to prepare graphical processing units (GPUs) on your Azure Local instance for computation-intensive workloads running on Azure Local virtual machines (VMs) enabled by Azure Arc and Azure Kubernetes Service (AKS) enabled by Azure Arc. GPUs are used for computation-intensive workloads such as machine learning and deep learning.
1616

1717

1818
## Attaching GPUs on Azure Local
@@ -41,12 +41,12 @@ NVIDIA supports their workloads separately with their virtual GPU software. For
4141

4242
For AKS workloads, see [GPUs for AKS for Arc](/azure/aks/hybrid/deploy-gpu-node-pool#supported-gpu-models).
4343

44-
The following GPU models are supported using both DDA and GPU-P for Arc VM workloads:
44+
The following GPU models are supported using both DDA and GPU-P for Azure Local VM workloads:
4545

4646
- NVIDIA A2
4747
- NVIDIA A16
4848

49-
These additional GPU models are supported using GPU-P (only) for Arc VM workloads:
49+
These additional GPU models are supported using GPU-P (only) for VM workloads:
5050

5151
- NVIDIA A10
5252
- NVIDIA A40
@@ -263,7 +263,7 @@ Follow these steps to configure the GPU partition count in PowerShell:
263263
264264
## Guest requirements
265265
266-
GPU management is supported for the following Arc VM workloads:
266+
GPU management is supported for the following VM workloads:
267267
268268
- Generation 2 VMs
269269

0 commit comments

Comments
 (0)