Your network contains an Active Directory domain named contoso.com. The domain contains a
member server named Server1. Server1 runs Windows Server 2012 R2 and has the Hyper-V server
role installed.
Server1 hosts 10 virtual machines. A virtual machine named VM1 runs Windows Server 2012 R2 and
hosts a processor-intensive application named App1.
Users report that App1 responds more slowly than expected.
You need to monitor the processor usage on VM1 to identify whether changes must be made to the
hardware settings of VM1.
Which performance object should you monitor on Server1?
A.
Processor
B.
Hyper-V Hypervisor Virtual Processor
C.
Hyper-V Hypervisor Logical Processor
D.
Hyper-V Hypervisor Root Virtual Processor
E.
Process
Explanation:
In the simplest way of thinking the virtual processor time is cycled across the available logical
processors in a round-robin type of fashion. Thus all the processing power gets used over time, and
technically nothing ever sits idle.To accurately measure the processor utilization of a guest operating system, use the “\Hyper-V
Hypervisor Logical Processor (Total)\% Total Run Time” performance monitor counter on the HyperV host operating system.
It is the Virtual Processor… The logical is for the total amount of VM machines using the processor. The Virtual is for that specifici VM.
0
0
One concurs, the correct answer is B
0
0
according to this article it’s C
https://msdn.microsoft.com/en-us/library/cc768535%28v=bts.10%29.aspx?f=255&MSPPError=-2147217396
0
0
That article makes a convincing argument for C
0
0
This article is not convincing enough for me – it says that Hyper-V Logical Processor/Total cpu time measures overall HV processor performance; we’ve been asked to measure preciously “VM1” and only way to measure single VMguest is by HV Virtual Processor counter. Of course this article presents whole case – countermeasure Logical Vs Virtual Processors but this is not a part of a question. I’ll pick B.
1
0
Answer=C Logical processor
To accurately measure the processor utilization of a guest operating system, use the “\Hyper-V Hypervisor Logical Processor(_Total)\% Total Run Time” performance monitor counter on the Hyper-V host operating system
0
0
I must concur with “B”. The last paragraph of the article referenced states:
To measure total physical processor utilization of the host operating system and all guest operating systems, use the “\Hyper-V Hypervisor Logical Processor(_Total)\% Total Run Time” performance monitor counter. This counter measures the total percentage of time spent by the processor running the both the host operating system and all guest operating systems.
0
0
The correct answer is B (Hyper-V Hypervisor Virtual Processor).
A hyper-V Hypervisor Virtual Processor is assigned to a specific VM, while the Hyper-V Logical Processor represents the total number of processors on a host system (in this case Server1) that are managed by Hyper-V. In other words, Logical processors are not assigned to a specific VM, but to Hyper-V.
The following article http://windowsitpro.com/blog/perfmon-hyper-v-hypervisor-virtual-processor-versus-hyper-v-hypervisor-logical-processor states:
For a Hyper-V VM, you cannot view the traditional % Processor Time metric to get a good understanding of that VM’s processing. Instead, the counter you’ll want to monitor is Hyper-V Hypervisor Virtual Processor \ % Guest Run Time (InstanceName). This counter can be considered to be equivalent to % Processor Time, but for a specific VM as defined by its instance name.
While similar in name, this counter is different than Hyper-V Hypervisor Logical Processor. Whereas Hyper-V considers a “Virtual Processor” to be one that has been assigned as part of a VM’s configuration, a “Logical Processor” represents the total number of processors on a host system that are managed by Hyper-V.
The resulting Hyper-V Hypervisor Local Processor identifies utilization on a per logical processor basis. So, using it, you can determine the individual utilization of each of your logical processors as they’re being consumed by Hyper-V workloads.
0
0
“B” is correct
0
0
To complicate things a bit more, I guess you need them both 🙂
———- from article above——————–
To troubleshoot processor performance of guest operating systems on a Hyper-V environment, it is best to strive for a balance between the values reported by the host operating system for “\Hyper-V Hypervisor Logical Processor(_Total)\% Total Run Time” (LPTR) and “\Hyper-V Hypervisor Virtual Processor(_Total)\% Total Run Time” (VPTR). If LPTR is high and VPTR is low then verify that there are not more processors allocated to virtual machines than are physically available on the physical computer. Use the “\Hyper-V Hypervisor Virtual Processor(*)\%Guest Run Time” counters to determine which virtual Processors are consuming CPU and de-allocate virtual processors from virtual machines as appropriate to configure a one to one mapping of virtual processors to logical processors. For more information about configuring a one to one mapping of virtual processors to logical processors see the “Optmizing Processor Performance” section in Optimizing Performance on Hyper-V. If VPTR is high and LPTR is low then consider allocating additional processors to virtual machines if there are available logical processors and if additional processors are supported by the guest operating system. In the case where VPTR is high, LPTR is low, there are available logical processors to allocate, but additional processors are not supported by the guest operating system, consider scaling out by adding additional virtual machines to the physical computer and allocating available processors to these virtual machines. In the case where both VPTR and LPTR are high, the configuration is pushing the limits of the physical computer and should consider scaling out by adding another physical computer and additional Hyper-V virtual machines to the environment. The flowchart below describes the process that should be used when troubleshooting processor performance in a Hyper-V environment.
————————————
But to answer this question I would go with C since you can’t rely only on the Virtual Processor in case a VM has more virtual processor assigned to it than there are physical available, check this part in specific out:
“If LPTR is high and VPTR is low then verify that there are not more processors allocated to virtual machines than are physically available on the physical computer.”
0
0
Answer : (B) Hyper-V Hypervisor Virtual Processor
0
0
The answer is B!
You need to monitor the virtual CPU because the question state assune that the slowness coming from app1 (softwore issue, not hatdware).
If the problem was hardware – I would say C…
0
0
ANSWER B – Hyper-V Hypervisor Virtual Processor
Explanation:
The more useful counter is “Hyper-V Hypervisor Virtual Processor(*)\%Guest Run Time: it’s a useful counter to see processor utilization of virtual machines. This is far batter than monitoring a processor within virtual machine because clock calculation drift can affect the processor utilization information.
The less useful counter is “Hyper-V Hypervisor Logical Processor(*)\%Total Run Time: This is a best way to see overall utilization of the processors, including Hyper-V Host and virtual machines. the processor in Task manager on the Hyper-V host shows only CPU use from the root partition.
2
0