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

Virtual Machines with preallocated memory might be placed NUMA remote at random power-ons (76362)

Last Updated: 7/6/2020Categories: InformationalTotal Views: 7723Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

You might notice a seemingly random difference in performance whenever powering on virtual machines with at least one of these options:

PCI passthrough devices (DirectPath IO or SR-IOV)

Fault Tolerance (FT) enabled

Latency Sensitivity set to High

vGPU enabled

Affected virtual machines will have either 0% or very little NUMA local memory.

In esxtop's memory (m) view and with the fields (f) for NUMA STATS (g) enabled, you can confirm this by monitoring "N%L":

9:43:04am up 5 days 36 min, 538 worlds, 1 VMs, 4 vCPUs; MEM overcommit avg: 0.00, 0.00, 0.00
PMEM /MB: 131026 total: 2160 vmk,1185 other, 127680 free
VMKMEM/MB: 130640 managed: 1920 minfree, 7048 rsvd, 123592 ursvd, high statej
NUMA /MB: 65488 (63845), 65536 (63450)
PSHARE/MB: 27 shared, 27 common: 0 saving
SWAP /MB: 0 curr, 0 rclmtgt: 0.00 r/s, 0.00 w/s
ZIP /MB: 0 zipped, 0 saved
MEMCTL/MB: 0 curr, 0 target, 0 max

GID NAME NHN NMIG NRMEM NLMEM N%L GST_ND0 OVD_ND0 GST_ND1 OVD_ND1
7656943 VMNAME 0 0 1024.00 0.00 0 0.00 12.09 1024.00 1.49
(...)

Alternatively on the ESXi CLI, use "sched-stats". Here look for the "currLocal%" and "cummLocal%" columns, the later being the cumulative percentage of memory locality since power on:

# sched-stats -t numa-clients

groupName groupID clientID homeNode affinity nWorlds vmmWorlds localMem remoteMem currLocal% cummLocal%
vm.1194167 7656943 0 0 0xf 6 6 0 33554432 0 0
(...)

In most cases, you will either see none or very little NUMA migrations for the affected VMs (*Mig columns)

# sched-stats -t numa-migration

groupName groupID clientID balanceMig loadMig localityMig longTermMig monitorMig pageMigRate
vm.1194167 7656943 0 0 0 0 0 0 0
(...)

To map the groupID to the virtual machine's display name, either use esxtop (GID and NAME column) or "esxcli vm process list" and match "VMX Cartel ID:" to "groupName" without the "vm.".

Cause

This is caused by an issue where the virtual machine memory can be pinned before the NUMA locality is decided in the initial placement and power-on phase.

Resolution

This issue is resolved in ESXi 6.5 U3

Workaround

To workaround this issue you can use "numa.NodeAffinity" to force locality. Note that you have to be at least on ESXi 6.5 U1.

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
•
从 6.5 或 6.7 迁移到更高版本时报错：导出 VMware vCenter 身份验证框架时出现内部错误 (78605)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

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 6.5

Take Our Survey

Support Assistant