Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Supported scenarios of NVME hot plug/removal in ESXi (78297)

Last Updated: 6/2/2021Categories: Best PracticesTotal Views: 5716Language:
Chinese (Simplified)JapaneseEnglish

7 like this article

Subscribe to get an email
newsletter with new updates

7 people found this helpful Please provide article feedback:

Details

ESXi supports PCIE hot plug for NVMe devices.
There are two kinds of hot-plug scenarios supported by ESXi:

Orderly/Planned hot-plug: hot-plug operation is initiated via notification of hardware or software after all of required proprietary steps, such as unmounting datastore, unclaiming device, etc. are done.

Surprise hot-plug: Operation is initiated without prior notification. Such as hot-unplug device manually.

Note:

ESXi supports hot-plug for only NVMe device which is in normal mode, i.e. the device isn't configured as RDM, PCI passthrough, or used as OS installation volume.

It is recommended to do orderly hot-plug whenever as possible. Supporting surprise hot-plug is precaution against incorrect user operation.

Solution

Best practices

Choose a hot-plug capable slot and then insert NVMe device. Wait for power indicator being on, if the platform supports driver power control.

Issue esxcli hardware PCI list and check if target nvme device is listed. Output is similar to following:

0000:86:00.0

Address: 0000:86:00.0

Segment: 0x0000

Bus: 0x86

Slot: 0x00

Function: 0x0

VMkernel Name: vmhba3

Vendor Name: xxxxxxxxx

Device Name: xxxxxxxx PCIe SSD Controller

Configured Owner: VMkernel

Current Owner: VMkernel

Vendor ID:

. . .

Check readiness of SCSI devices for the NVMe device: run esxcli storage core device list. Output is similar to following:

(t10.NVMe____Dell_Express_Flash_NVMe_PM1725_1.6TB_SFFB25C007192382500

Display Name: Local NVMe Disk (t10.NVMe____Dell_Express_Flash_NVMe_PM1725_1.6TB_SFFB25C007192382500)

Has Settable Display Name: true

Size: 1526185

Device Type: Direct-Access

Multipath Plugin: NMP

Devfs Path: /vmfs/devices/disks/t10.NVMe____Dell_Express_Flash_NVMe_PM1725_1.6TB_SFFB25C007192382500

Vendor: NVMe

Model: Dell Express Fla

...

If NVMe device contains VMFS datastores, these datastores will be mounted automatically. Run 'esxcli storage filesystem list' to list all datastores claimed.

Removal

Make sure no IO is running on the NVME device to be removed before starting hot-plug, no matter orderly or surprise.

On orderly hot-unplug scenario,  user needs to run proprietary steps before unplugging. They are:

Power off VMs, if any.

Unmount VMFS and detach devices. For more information see vSphere support for hot-swap of local disks.

In surprise hot-unplug scenario, user stop IOs running on NVMe device and then plug device out immediately not running the above steps.

Hot-unplug device. Check that the device is removed from the system device listing:

Issue "esxcli storage core device list", check that the device is not listed.

Issue "esxcli storage nmp path list", check that there is no path for this device.

Plug in the device, check that the device becomes available. Steps are:

If the device was hot-unplugged orderly, it needs to re-enable device being detected during rescan via command "esxcli storage core claiming autoclaim --enabled=True".

Issue "esxcli hardware pci list|grep -w <vmhba>", check that new adapter is listed.

Issue "esxcli storage core device list", check that the device is listed.

Issue "esxcli storage nmp path list", check that the path to device is listed.

Steps to remount VMFS volumes:

Mount VMFS volume: esxcli storage filesystem mount -l <datastore>

List all VMFS volumes: esxcli storage filesystem list

Note: Do not perform hot-plug frequently, as they might lead to potential problems and corner case issues.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 8.0.x

VMware vSphere ESXi 7.0.0

Take Our Survey

Support Assistant