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 Machine performance charts for CPU Usage metrics in VM's displays a different value in than in Guest OS (74865)

Last Updated: 4/14/2020Categories: InformationalTotal Views: 7666Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

Virtual Machine performance charts for CPU Usage metrics in VM's displays a different value in than in Guest Operating System

For example a VM will show CPU Usage MHz @ 70%  however inside vm CPU Usage in MHZ will be @ 40%.

Purpose

This KB explains how the CPU values are calculated from point of view of the Hypervisor.

Cause

This difference will appear when the VM have additional entries added in the virtual machines configuration file. (vmx)
ethernetX.ctxPerDev = "1"
sched.cpu.latencySensitivity.sysContexts = "<no of threads>"

Hypervisor will spawn  multiple worldID in behalf of the VM .Most of the worldID's are not CPU intensive and they will not reflect CPU usage.

However the worldID like sysContext and CtxPerDev are processes that help the Hypervisor to accelerate the packet handling.

For Example:
2x VCPU with 2x Nics

VCPU 1 usage is  40%  and  VCPU 2 usage 40% = 40 + 40 = 80%
Nic1 usage is 40% and Nic 2 is 20% = 40 + 20 = 60%
Total  CPU usage = 140 / 2(vcpus)

Impact / Risks

This can trigger an alarm as the value can rise over 100%

Resolution

VMware Engineering are aware of this and the behaviour will be modified in a future release. A new counter will be added in future release to include a new CPU counter that sums vCPU and does not include VMX CPU usage, effectively excluding the CPU overhead.

Workaround

Use esxtop to determine the correct values.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

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)

KB
•
[解決済み] BINXA-8906：VMware Workspace ONE Boxer で複数の受信者を含む E メールに対して [全員に返信] を実行すると、無効なアドレスを示すダイアログが表示される (2961462)

KB
•
[解決済み] UAG-4036：TLS ポート共有を使用している場合、vpnd サービスを再起動するとポート 8443 ではなくポート 443 でリッスンが開始される (Hyper-V 展開のみ) (2961506)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

VMware vSphere ESXi 6.5

Take Our Survey

Support Assistant