Skip to main content

vSphere 6.5 vNVMe

NVMe:

NVM Express (NVMe) or Non-Volatile Memory Host Controller Interface (NVMHCI) is a logical device interface specification for accessing non-volatile storage media attached via a PCI Express (PCIe) bus in real and virtual hardware.

The acronym NVM stands for non-volatile memory, commonly flash memory that comes in the form of solid-state drives (SSDs). NVM Express, as a logical device interface, has been designed from the ground up to capitalise on the low latency and internal parallelism of flash-based storage devices, mirroring the parallelism of contemporary CPUs, platforms and applications.

 NVM Express allows host hardware and software to fully exploit the possible parallelism in modern SSDs. As a result, NVM Express reduces I/O overhead and brings various performance improvements in comparison to previous logical-device interfaces, including multiple, long command queues, and reduced latency. 

vSphere and NVMe:

NVM Express (NVMe) controller is available with ESXi 6.5 and Hardware Version 13. With Hardware Version 13, you can use NVMe, SATA, SCSI, and IDE controllers in a virtual machine.
Virtual NVMe (vNVMe):
Virtual NVMe Device has lower IO overhead and scalable IO for all-flash SAN/vSAN storages. Hardware NVMe SSDs has significant advantage over old SATA/SAS based Flash devices.
The main benefit of NVMe interface over SCSI is that it reduces the amount of overhead, and so consumes fewer CPU cycles. Also, there is a reduction of IO latency for your VMs. 

 Each virtual machine can support 4 NVMe controllers and up to 15 devices per controller. 
Driver Architecture:


  • Native Model: Register/unregister driver and bring up device
  • VMKLinux Model: Deprecated
  • OS Libs: Provide OS related resource, such as heap, lock, interrupt.
  • Mgmt: Management interface to pass through admin command
  • SCSI Emulation Layer: The storage stack of ESXi is SCSI based, responsible for translating SCSI to NVMe command
  • NVMe Core: NVMe related stuff, such as queue construction, command issue, register read/write


Supported guest operating systems:

Not all operating systems are supported with vNVMe. Make sure that your OS is supported and also verify that the guest OS has a driver installed to use the NVMe controller.
  • Windows 7 and 2008 R2 (hot fix required: https://support.microsoft.com/en-us/kb/2990941) 
  • Windows 8.1, 2012 R2, 10, 2016 
  • RHEL, CentOS, NeoKylin 6.5 and later 
  • Oracle Linux 6.5 and later 
  • Ubuntu 13.10 and later 
  • SLE 11 SP4 and later 
  • Solaris 11.3 and later 
  • FreeBSD 10.1 and later 
  • Mac OS X 10.10.3 and later 
  • Debian 8.0 and later
Labels:

Comments

Post a Comment

Popular posts from this blog

Dell EMC VxRail – VMware Virtual SAN Stretched Cluster

Logical Diagram of VMware vSAN Stretched Cluster Physical Diagram of VMware vSAN Stretched Cluster Last week I deployed a test environment of VMware vSAN Stretched Cluster which is running on Dell EMC VxRail Appliance. In this post we will describe how to setup VMware vSAN Stretched Cluster on Dell EMC VxRail Appliance. Above figure is the high level of physical system diagram. In site A/B there are six VxRail Appliances and two 10GB Network Switch which are interconnected by two 10GB links, and each VxRail Appliance has one 10GB uplink connects to each Network Switch. In site C, there are one vSAN Witness host and one 10GB Network Switch. For the details of configuration of each hardware equipment in this environment, you can reference the followings. Site A (Preferred Site) 3 x VxRail E460 Appliance Each node includes 1 x SSD and 3 x SAS HDD, 2 x 10GB SFP+ ports 1 x 10GB Network switch Site B (Secondary Site) 3 x VxRail E460 Appliance Each node includes 1 x SSD and...
1 comment
Read more

UEFI Secure Boot with ESXi 6.5

UEFI Secure Boot: UEFI, or Unified Extensible Firmware Interface, is a replacement for the traditional BIOS firmware. In UEFI, Secure Boot is a “protocol” of the UEFI firmware. UEFI Secure boot ensures that the boot loaders are not compromised by validating their digital signature against a digital certificate in the firmware. UEFI can store whitelisted digital certificates in a signature database (DB). There is also a blacklist of forbidden certificates (DBX), a Key Exchange Keys (KEK) database and a platform key. These digital certificates are used by the UEFI firmware to validate the boot loader.  Boot loaders are typically cryptographically signed and their digital signature chains to the certificate in the firmware.The default digital certificate in almost every implementation of UEFI firmware is a x509 Microsoft UEFI Public CA cert. Most of the UEFI implementations also allows the installation of additional certificate in the UEFI firmware and UE...
Post a Comment
Read more

VxRail 4.0 – Scale Out

The above is the physical diagram of VxRail Cluster (3 nodes). In this post I will show how to add one VxRail Appliance into this VxRail Cluster (From 3 nodes to 4 nodes). NOTE: The model of each VxRail Appliance is E460. Before the node expansion, you need to verify each Appliance is running in health in dashboard of VxRail Manager. The above is the final physical diagram of VxRail Cluster after scale out. Now we start the node expansion. You have just mounted a new VxRail Appliance (E460) and cabled it up to the top of each rack switch. When you power it on you can see a notification appear in the top left corner of VxRail dashboard. Click “ Add Node “. When you initially configured your VxRail Appliance, you specified an IP pool for ESXi, vMotion and vSAN. You can see that there available IP addresses in these pools, so the only additional action is to set an ESXi password. Click the scroll bar, then click the “ ESXi Password “. Enter the  ESXi  and ...
1 comment
Read more