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
Copy file name to clipboardExpand all lines: articles/virtual-machines/enable-nvme-faqs.yml
+24-17Lines changed: 24 additions & 17 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
### YamlMime:FAQ
2
2
metadata:
3
3
title: NVMe - General FAQ
4
-
description: Provides answers to some of the common questions about enabling NVMe interface on virtual machines
4
+
description: Get answers to some of the common questions about enabling the NVMe interface on virtual machines.
5
5
ms.service: virtual-machines
6
6
ms.topic: faq
7
7
ms.custom: references_regions
@@ -17,38 +17,45 @@ sections:
17
17
- question: |
18
18
What is NVMe?
19
19
answer: |
20
-
NVMe stands for nonvolatile memory express, a communication protocol that facilitates faster and more efficient data transfer between servers and storage systems. With NVMe, data can be transferred at the highest throughput and with the fastest response times.
21
-
NVMe offers higher IOPS (Input/Output Operations Per Second) and throughput (MB/s), which can significantly improve the performance of both temp (local) and remote NVMe disk storage with [Azure managed disks](/azure/virtual-machines/managed-disks-overview). Higher performance is especially beneficial for IO-intensive workloads that require fast data transfer to the Azure managed disks.
20
+
NVM Express (NVMe) is a communication protocol that facilitates faster and more efficient data transfer between servers and storage systems by using nonvolatile memory (NVM). With NVMe, data can be transferred at the highest throughput and with the fastest response times.
21
+
22
+
NVMe offers higher input/output operations per second (IOPS) and throughput in megabytes per second (MBps), which can significantly improve the performance of both temporary (local) and remote NVMe disk storage with [Azure managed disks](/azure/virtual-machines/managed-disks-overview). Higher performance is especially beneficial for I/O-intensive workloads that require fast data transfer to the Azure managed disks.
22
23
- question: |
23
-
Which types of storage interfaces are supported in Azure’s VM families?
24
+
Which types of storage interfaces are supported in Azure VM families?
24
25
answer: |
25
-
In Azure, there are two types of storage interfaces that we support, SCSI (Small Computer System Interface) and NVMe (Non-Volatile Memory express). The SCSI interface is a legacy standard that provides physical connectivity and data transfer between computers and peripheral devices. NVMe is similar to SCSI in that it provides connectivity and data transfer, but NVMe is a significantly faster and more efficient interface for data transfer between servers and storage systems.
26
+
Azure virtual machines (VMs) support two types of storage interfaces: Small Computer System Interface (SCSI) and NVMe. The SCSI interface is a legacy standard that provides physical connectivity and data transfer between computers and peripheral devices. NVMe is similar to SCSI in that it provides connectivity and data transfer, but NVMe is a significantly faster and more efficient interface for data transfer between servers and storage systems.
26
27
- question: |
27
28
How do Azure Boost and NVMe improve the performance of the VMs that Azure offers?
28
29
answer: |
29
-
Azure Boost is a system designed by Microsoft that offloads server virtualization processes traditionally performed by the hypervisor and host OS onto purpose-built software and hardware, enabling faster storage and networking performance for Azure VM customers. One of the primary advantages of Azure Boost is its ability to enhance the throughput of Azure Managed Disks and local storage. This enhancement is enabled by offloading the storage processing tasks to Azure Boost’s dedicated hardware. Furthermore, Azure Boost optimizes performance by utilizing the industry standard NVMe interface, which capitalizes on the low latency and internal parallelism of solid-state storage drives. Refer to the [Microsoft Azure Boost General Availability Blog](https://techcommunity.microsoft.com/t5/azure-infrastructure-blog/announcing-the-general-availability-of-azure-boost/ba-p/3981384) for details on the performance offered.
30
+
Azure Boost is a Microsoft-designed system that offloads server virtualization processes traditionally performed by the hypervisor and host OS onto purpose-built software and hardware. Offloading these processes enables faster storage and networking performance for Azure VM customers.
31
+
32
+
One of the primary advantages of Azure Boost is its ability to enhance the throughput of Azure managed disks and local storage. This enhancement is enabled by offloading the storage processing tasks to dedicated hardware for Azure Boost.
33
+
34
+
Azure Boost also optimizes performance by using the industry-standard NVMe interface, which capitalizes on the low latency and internal parallelism of solid-state storage drives. For details on the performance that Azure Boost offers, see the [Microsoft blog post that announced general availability of Azure Boost](https://techcommunity.microsoft.com/t5/azure-infrastructure-blog/announcing-the-general-availability-of-azure-boost/ba-p/3981384).
30
35
- question: |
31
36
Will Azure continue to support SCSI interface VMs?
32
37
answer: |
33
-
Yes, Azure will continue to support the SCSI interface on the versions of VM offerings which offer SCSI storage, but not all new VM series will have SCSI storage as an option going forward.
34
-
- name: NVMe Supportability
38
+
Yes. Azure will continue to support the SCSI interface on the versions of VM offerings that offer SCSI storage. However, not all new VM series will have SCSI storage as an option going forward.
39
+
- name: NVMe supportability
35
40
questions:
36
41
- question: |
37
-
Which VM generations support NVMe Disks?
42
+
Which VM generations support NVMe disks?
38
43
answer: |
39
-
Typically, the older generations of General Purpose, Memory Optimized, and Compute Optimized VMs (i.e. D/Ev5 or Fv2 and older) support SCSI, whereas the newer generations (e.g. Da/Ea/Fav6 or after) support only the NVMe storage interface. However, Ebsv5/Ebdsv5 and Lsv2/Lsv3/Lasv3 VMs have introduced NVMe as an option for temp disk.
40
-
Always check the [detailed product pages for specifics](/azure/virtual-machines/sizes) about which VM generations support which storage types.
44
+
Typically, the older generations of general purpose, memory optimized, and compute optimized VMs (that is, D/Ev5 or Fv2 and older) support SCSI. The newer generations (that is, Da/Ea/Fav6 and newer) support only the NVMe storage interface. However, Ebsv5/Ebdsv5 and Lsv2/Lsv3/Lasv3 VMs introduced NVMe as an option for temporary disks.
45
+
46
+
For specifics about which VM generations support which storage types, check the [documentation about VM sizes in Azure](/azure/virtual-machines/sizes).
41
47
- question: |
42
-
Will Gen 1 VMs be supported with NVMe disks?
48
+
Will Generation 1 VMs be supported with NVMe disks?
43
49
answer: |
44
-
No, there are no plans to support NVMe disks on Gen 1 VMs. If you think your workload benefits from NVMe performance, you must switch to the Gen 2 VMs. Refer to the steps to [create a new Gen 2 VM](/azure/virtual-machines/generation-2). If you attempt to use a Gen 1 VM image, you'll either not be able to select an NVMecapable VM or receive an error message that reads: "The selected image isn't supported for NVMe. See supported VM images".
50
+
No, there are no plans to support NVMe disks on Generation 1 VMs. If you think your workload benefits from NVMe performance, you must switch to the Generation 2 VMs. To create a Generation 2 VM, follow the [documented steps](azure/virtual-machines/generation-2#creating-a-generation-2-vm). If you try to use a Generation 1 VM image, either you won't be able to select an NVMe-capable VM, or you'll get this error message: "The selected image isn't supported for NVMe. See supported VM images".
45
51
- question: |
46
-
What happens if the OS I use is not tagged as NVMe supported?
52
+
What happens if the OS that I use is not tagged as NVMe supported?
47
53
answer: |
48
-
An NVMe VM can only be created using an image (Platform Image Repository (PIR) & [Azure Compute Gallery](/azure/virtual-machines/shared-image-galleries?tabs=azure-cli)) that has been tagged as NVMe. If an untagged image is used, a SCSI VM is created, and the VM may not perform as you had intended. Make sure to follow all instructions listed [here](/azure/virtual-machines/enable-nvme-interface).
49
-
To launch VMs with an NVMe interface, it's essential to choose one of the [supported OS images](/azure/virtual-machines/enable-nvme-interface) tagged as NVMe. If your current OS image is not supported for NVMe, you'll see an error message that reads: "The selected image isn't supported for NVMe. See supported VM images".
54
+
You can create an NVMe-supported VM only by using an image (Platform Image Repository and [Azure Compute Gallery](/azure/virtual-machines/shared-image-galleries?tabs=azure-cli)) that's tagged as NVMe. If you use an untagged image, a SCSI VM is created, and the VM might not perform as you intended. Be sure to follow all the [instructions](/azure/virtual-machines/enable-nvme-interface).
55
+
56
+
To create VMs with an NVMe interface, it's essential to choose one of the [supported OS images](/azure/virtual-machines/enable-nvme-interface) tagged as NVMe. If your current OS image is not supported for NVMe, you'll get this error message: "The selected image isn't supported for NVMe. See supported VM images".
50
57
51
-
:::image type="content" source="./media/enable-nvme/nvme-faq-2.png" alt-text="Screenshot of example of choosing one of the supported OS images on NVMe":::
58
+
:::image type="content" source="./media/enable-nvme/nvme-faq-2.png" alt-text="Screenshot of an example of choosing one of the supported OS images on NVMe.":::
52
59
- question: |
53
60
When will NVMe support be added to the OS image I currently use?
0 commit comments