1-800-691-1991 | 9am - 8pm ET
EN

High guest OS resource utilization

KB ID: 1678
Product: Veeam ONE
Version: All
Published: 2013-03-29
Last Modified: 2020-08-13
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

Performance metrics within a Virtual Machine's Guest OS are different (higher or lower) than the same metrics reported by Veeam ONE.
 

Cause

The process used by vSphere to allocate and distribute system resources differs from the methods used by Windows and other operating systems for a physical machine. As Veeam ONE collects its performance data directly from vSphere, the metrics you see in Veeam ONE reflect those found in vSphere rather than VM’s guest OS. The guest OS can only view and analyze performance from within the virtual machine, whereas vSphere uses an overall view of all virtual machines and resources to calculate and analyze performance.
 
There are several reasons why the metric values may differ:
  1. Virtual machine’s guest OS is unaware of hypervisor resource overheads. This occurs because the guest OS is only permitted to view a certain portion of all available resources as determined by hypervisor’s scheduler.

  2. Resource overheads often change based on workloads.

  3. There may be a time difference between performance data displayed at the guest and hypervisor level. Additionally, the time intervals at which performance data is recorded and displayed may differ between the guest OS’s resource monitor and the hypervisor’s resource monitor.

  4. Because a virtual machine’s guest OS is unaware of its hypervisor’s resource distributions, it is therefore unaware of being “de-scheduled” while idle.
     

Solution

As a general rule of thumb, the performance metrics reported by Veeam ONE, and in turn vSphere, should be taken into consideration rather than guest OS’s performance metrics. If there is any doubt of the accuracy of Veeam ONE’s performance data, verify first that the data matches the corresponding data in vSphere.
Click here to send feedback regarding this KB, or suggest content for a new KB.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you for your interest in Veeam products!
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.