Skip to content

Commit a226e5a

Browse files
LouisBernerLouisBerner
committed
Updates for supported nics in a VM
1 parent 47053e7 commit a226e5a

File tree

3 files changed

+10
-10
lines changed

3 files changed

+10
-10
lines changed

‎articles/databox-online/azure-stack-edge-gpu-create-virtual-machine-image.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: alkohli
77
ms.service: databox
88
ms.subservice: edge
99
ms.topic: how-to
10-
ms.date: 05/19/2022
10+
ms.date: 08/09/2022
1111
ms.author: alkohli
1212
#Customer intent: As an IT admin, I need to understand how to create Azure VM images that I can use to deploy virtual machines on my Azure Stack Edge Pro GPU device.
1313
---
@@ -18,7 +18,7 @@ ms.author: alkohli
1818

1919
To deploy VMs on your Azure Stack Edge Pro GPU device, you need to be able to create custom VM images that you can use to create VMs in Azure. This article describes the steps to create custom VM images in Azure for Windows and Linux VMs and download or copy those images to an Azure Storage account.
2020

21-
There's a required workflow for preparing a custom VM image. For the image source, you need to use a fixed VHD from a Gen1 VM of any size that Azure supports. For VM size options, see [Supported VM sizes](azure-stack-edge-gpu-virtual-machine-sizes.md#supported-vm-sizes).
21+
There's a required workflow for preparing a custom VM image. For the image source, you need to use a fixed VHD from any size that Azure supports. For VM size options, see [Supported VM sizes](azure-stack-edge-gpu-virtual-machine-sizes.md#supported-vm-sizes).
2222

2323
## Prerequisites
2424

@@ -41,7 +41,7 @@ Do the following steps to create a Windows VM image:
4141

4242
The virtual machine can be a Generation 1 or Generation 2 VM. The OS disk that you use to create your VM image must be a fixed-size VHD of any size that Azure supports. For VM size options, see [Supported VM sizes](azure-stack-edge-gpu-virtual-machine-sizes.md#supported-vm-sizes).
4343

44-
You can use any Windows Gen1 or Gen2 VM with a fixed-size VHD in Azure Marketplace. For a list Azure Marketplace images that could work, see [Commonly used Azure Marketplace images for Azure Stack Edge](azure-stack-edge-gpu-create-virtual-machine-marketplace-image.md#commonly-used-marketplace-images).
44+
You can use any Windows Gen1 or Gen2 VM with a fixed-size VHD in Azure Marketplace. For a of list Azure Marketplace images that could work, see [Commonly used Azure Marketplace images for Azure Stack Edge](azure-stack-edge-gpu-create-virtual-machine-marketplace-image.md#commonly-used-marketplace-images).
4545

4646
2. Generalize the virtual machine. To generalize the VM, [connect to the virtual machine](azure-stack-edge-gpu-deploy-virtual-machine-powershell.md#connect-to-a-windows-vm), open a command prompt, and run the following `sysprep` command:
4747

@@ -78,11 +78,11 @@ Do the following steps to create a Linux VM image:
7878
7979
### Using RHEL BYOS images
8080
81-
If using Red Hat Enterprise Linux (RHEL) images, only the Red Hat Enterprise Linux Bring Your Own Subscription (RHEL BYOS) images, also known as the Red Hat gold images, are supported and can be used to create your VM image. The standard pay-as-you-go RHEL images on Azure Marketplace are not supported on Azure Stack Edge.
81+
If using Red Hat Enterprise Linux (RHEL) images, only the Red Hat Enterprise Linux Bring Your Own Subscription (RHEL BYOS) images, also known as the Red Hat gold images, are supported and can be used to create your VM image. The standard pay-as-you-go RHEL images on Azure Marketplace aren't supported on Azure Stack Edge.
8282

8383
To create a VM image using the RHEL BYOS image, follow these steps:
8484

85-
1. Log in to [Red Hat Subscription Management](https://access.redhat.com/management). Navigate to the [Cloud Access Dashboard](https://access.redhat.com/management/cloud) from the top menu bar.
85+
1. Sign in to [Red Hat Subscription Management](https://access.redhat.com/management). Navigate to the [Cloud Access Dashboard](https://access.redhat.com/management/cloud) from the top menu bar.
8686
1. Enable your Azure subscription. See [detailed instructions](https://access.redhat.com/documentation/en-us/red_hat_subscription_management/1/html/red_hat_cloud_access_reference_guide/getting-started-with-ca_cloud-access). Enabling the subscription will allow you to access the Red Hat Gold Images.
8787

8888
1. Accept the Azure terms of use (only once per Azure Subscription, per image) and provision a VM. See [instructions](https://access.redhat.com/documentation/en-us/red_hat_subscription_management/1/html/red_hat_cloud_access_reference_guide/understanding-gold-images_cloud-access).

‎articles/databox-online/azure-stack-edge-gpu-virtual-machine-sizes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: alkohli
77
ms.service: databox
88
ms.subservice: edge
99
ms.topic: conceptual
10-
ms.date: 03/29/2022
10+
ms.date: 08/09/2022
1111
ms.author: alkohli
1212
#Customer intent: As an IT admin, I need to understand how to create and manage virtual machines (VMs) on my Azure Stack Edge Pro device by using APIs, so that I can efficiently manage my VMs.
1313
---

‎includes/azure-stack-edge-gateway-supported-vm-sizes.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
author: alkohli
33
ms.service: databox
44
ms.topic: include
5-
ms.date: 06/24/2022
5+
ms.date: 08/09/2022
66
ms.author: alkohli
77
---
88

@@ -29,7 +29,7 @@ The following VMs are supported for creation on your Azure Stack Edge device.
2929
| Size  | vCPU  | Memory (GiB)  | Temp storage (GiB)  | Max OS disk throughput (IOPS)  | Max temp storage throughput (IOPS)  | Max data disk throughput (IOPS)  | Max data disks  | Max NICs  |
3030
|-------------------|-------|---------------|---------------------|--------------------------------|-------------------------------------|----------------------------------|-----------------|-----------|
3131
| **Standard_DS1_v2**  | 1  | 3.5  | 7  | 2000  | 4000  | 2300  | 4  | 2  |
32-
| **Standard_DS2_v2**  | 2  | 7  | 14  | 2000  | 8000  | 2300  | 8  | 4  |
32+
| **Standard_DS2_v2**  | 2  | 7  | 14  | 2000  | 8000  | 2300  | 8  | 2  |
3333
| **Standard_DS3_v2**  | 4  | 14  | 28  | 2000  | 16000  | 2300  | 16  | 4  |
3434
| **Standard_DS4_v2**  | 8  | 28  | 56  | 2000  | 32000  | 2300  | 32  | 8  |
3535
| **Standard_DS5_v2**  | 16  | 56  | 112  | 2000  | 64000  | 2300  | 64  | 8  |
@@ -44,7 +44,7 @@ For more information, see [Dv2 and DSv2-series](../articles/virtual-machines/dv2
4444

4545
### N-series GPU optimized
4646

47-
These sizes are supported for GPU VMs on your device and are optimized for compute-intensive GPU-accelerated applications, for example, inferencing workloads The GPU VM that you deploy should match the GPU type on your Azure Stack Edge device.
47+
These sizes are supported for GPU VMs on your device and are optimized for compute-intensive GPU-accelerated applications, for example, inferencing workloads. The GPU VM that you deploy should match the GPU type on your Azure Stack Edge device.
4848

4949
#### For Nvidia's Tesla T4 GPU.
5050

@@ -94,7 +94,7 @@ The high-performance network (HPN) virtual machines are tailored for workloads t
9494

9595
| Size  | vCPU  | Memory (GiB)  | Temp storage (GiB)  | Max OS disk throughput (IOPS)  | Max temp storage throughput (IOPS)  | Max data disk throughput (IOPS)  | Max data disks  | Max NICs  |
9696
|-------------------|-------|---------------|---------------------|--------------------------------|-------------------------------------|----------------------------------|-----------------|-----------|
97-
| **Standard_DS2_v2_HPN**  | 2  | 7  | 14  | 2000  | 8000  | 2300  | 8  | 4  |
97+
| **Standard_DS2_v2_HPN**  | 2  | 7  | 14  | 2000  | 8000  | 2300  | 8  | 2  |
9898
| **Standard_DS3_v2_HPN**  | 4  | 14  | 28  | 2000  | 16000  | 2300  | 16  | 4  |
9999
| **Standard_DS4_v2_HPN**  | 8  | 28  | 56  | 2000  | 32000  | 2300  | 32  | 8  |
100100

0 commit comments

Comments
 (0)