You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update Intel TDX processor generation and VM sizes
Updated Intel TDX technology reference from 4th Gen to 5th Gen Intel® Xeon® processors. Adjusted VM size references from v5 to v6 series for Intel-based Confidential VMs.
Copy file name to clipboardExpand all lines: articles/confidential-computing/virtual-machine-options.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ ms.date: 11/15/2023
15
15
16
16
Azure offers a choice of Trusted Execution Environment (TEE) options from both AMD and Intel. These TEEs allow you to create Confidential VM environments with excellent price-to-performance ratios, all without requiring any code changes.
17
17
18
-
For AMD-based Confidential VMs, the technology used is [AMD SEV-SNP](https://www.amd.com/system/files/TechDocs/SEV-SNP-strengthening-vm-isolation-with-integrity-protection-and-more.pdf), which was introduced with 3rd Gen AMD EPYC™ processors. On the other hand, Intel-based Confidential VMs utilize [Intel TDX](https://cdrdv2-public.intel.com/690419/TDX-Whitepaper-February2022.pdf), a technology introduced with 4th Gen Intel® Xeon® processors. Both technologies have different implementations, however both provide similar protections from the cloud infrastructure stack.
18
+
For AMD-based Confidential VMs, the technology used is [AMD SEV-SNP](https://www.amd.com/system/files/TechDocs/SEV-SNP-strengthening-vm-isolation-with-integrity-protection-and-more.pdf), which was introduced with 3rd Gen AMD EPYC™ processors. On the other hand, Intel-based Confidential VMs utilize [Intel TDX](https://cdrdv2-public.intel.com/690419/TDX-Whitepaper-February2022.pdf), a technology introduced with 5th Gen Intel® Xeon® processors. Both technologies have different implementations, however both provide similar protections from the cloud infrastructure stack.
19
19
20
20
## Sizes
21
21
@@ -31,10 +31,10 @@ We offer the following VM sizes:
31
31
|**DCadsv6-series**| AMD SEV-SNP | General purpose CVM with local temporary disk. |
32
32
|**ECasv6-series**| AMD SEV-SNP | Memory-optimized CVM with remote storage. No local temporary disk. |
33
33
|**ECadsv6-series**| AMD SEV-SNP | Memory-optimized CVM with local temporary disk. |
34
-
|**DCesv5-series**| Intel TDX | General purpose CVM with remote storage. No local temporary disk. |
35
-
|**DCedsv5-series**| Intel TDX | General purpose CVM with local temporary disk. |
36
-
|**ECesv5-series**| Intel TDX | Memory-optimized CVM with remote storage. No local temporary disk. |
37
-
|**ECedsv5-series**| Intel TDX | Memory-optimized CVM with local temporary disk. |
34
+
|**DCesv6-series**| Intel TDX | General purpose CVM with remote storage. No local temporary disk. |
35
+
|**DCedsv6-series**| Intel TDX | General purpose CVM with local temporary disk. |
36
+
|**ECesv6-series**| Intel TDX | Memory-optimized CVM with remote storage. No local temporary disk. |
37
+
|**ECedsv6-series**| Intel TDX | Memory-optimized CVM with local temporary disk. |
38
38
|**NCCadsH100v5-series**| AMD SEV-SNP and NVIDIA H100 Tensor Core GPUs | CVM with Confidential GPU. |
39
39
40
40
> [!NOTE]
@@ -88,7 +88,7 @@ For availability information, see which [VM products are available by Azure regi
88
88
89
89
### Resizing
90
90
91
-
Confidential VMs run on specialized hardware, so you can only [resize confidential VM instances](confidential-vm-faq.yml#can-i-convert-a-dcasv5-ecasv5-cvm-into-a-dcesv5-ecesv5-cvm-or-a-dcesv5-ecesv5-cvm-into-a-dcasv5-ecasv5-cvm-) to other confidential sizes in the same region. For example, if you have a DCasv5-series VM, you can resize to another DCasv5-series instance or a DCesv5-series instance.
91
+
Confidential VMs run on specialized hardware, so you can only [resize confidential VM instances](confidential-vm-faq.yml#can-i-convert-a-dcasv5-ecasv5-cvm-into-a-dcesv5-ecesv5-cvm-or-a-dcesv5-ecesv5-cvm-into-a-dcasv5-ecasv5-cvm-) to other confidential sizes in the same region. For example, if you have a DCasv5-series VM, you can resize to another DCasv5-series instance or a DCesv6-series instance.
92
92
93
93
It's not possible to resize a non-confidential VM to a confidential VM.
0 commit comments