{"id":4251,"date":"2013-01-27T00:01:00","date_gmt":"2013-01-27T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2013\/01\/27\/weekend-scripter-use-powershell-to-meter-resources-on-hyper-v-windows-server-2012\/"},"modified":"2013-01-27T00:01:00","modified_gmt":"2013-01-27T00:01:00","slug":"weekend-scripter-use-powershell-to-meter-resources-on-hyper-v-windows-server-2012","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/weekend-scripter-use-powershell-to-meter-resources-on-hyper-v-windows-server-2012\/","title":{"rendered":"Weekend Scripter: Use PowerShell to Meter Resources on Hyper-V Windows Server 2012"},"content":{"rendered":"

Summary:<\/strong> Microsoft Scripting Guy, Ed Wilson, talks about using Windows PowerShell 3.0 to do Hyper-V Resource Metering on Windows Server 2012.<\/p>\n

Microsoft Scripting Guy, Ed Wilson, is here. Well, Charlotte looked like someone had taken a huge can of polyurethane and sprayed the entire city—multiple times. Ok, so it is sort of pretty the way the city glistens in the sun with a thick layer of ice encapsulating the city, but dude, it is dangerous. So, the Scripting Wife and I headed out to the beach. I am sitting in one of those funky coffee houses near the beach, writing my blog posting for today, watching the waves, the surf, and the sand with a nearly unobscured view.<\/p>\n

Yes, the Carolina beaches are great in the winter—when there are very few tourists to clutter things. Some restaurants close for the “off season,” but Teresa and I have discovered those types of restaurants are not the sort that we like to eat in anyway. We prefer the small, family-owned restaurants that have been in business for 50 years, and because of the quality of their food, and their loyal customer base, they do just fine year round.<\/p>\n

Checking on status of Resource Metering<\/h2>\n

Now, it is possible to use performance counters to see how a virtual machine performs. It is also possible to use performance counters to see how the host (the server that hosts the virtual machines) performs. In fact, I wrote an entire series of articles<\/a> talking about using performance counters with Windows PowerShell (in fact, one of my talks at the PowerShell Summit<\/a> will be on what I call PoshMon). What was missing was a way to view the resource consumption of the virtual machine related to the host. The Introduction to Resource Metering<\/a> <\/em>blog post written by Lalithra Fernando on the Virtualization Blog is an excellent place to start. Lalithra also wrote a blog post called How to Use Resource Metering with PowerShell<\/a>, <\/em>which is also a good introduction.<\/p>\n

Exam note<\/strong>   One of the objectives on the Exam 70-140: Installing and Configuring Windows Server 2012<\/a> <\/em>is configure Resource Metering, <\/em>and so if you are working on your new MCSE for Server Infrastructure<\/em><\/a>, you will want to know this material. Of course, if you are running or thinking about running Hyper-V on Windows Server 2012, you will want to know this information as well. <\/em>Like I said yesterday, I like the MCSE exams because they help me to come up to speed quickly on a new product by forcing me to learn about the new features.<\/p>\n

So, the first thing I need to do is to check on the status of Resource Metering on my Hyper-V server. To do this, I use the Get-VM<\/strong> cmdlet from the Hyper-V module to return virtual machine objects, and I pipe these to the Select-Object<\/strong> cmdlet, and I choose the name<\/strong> and the ResourceMeteringEnabled<\/strong> <\/em>properties. This command is shown here along with the associated output from the command.<\/p>\n

Note<\/strong>   Keep in mind that the Get-VM<\/strong> and other cmdlets from the Hyper-V require admin rights to run, and therefore, if you are doing this on Windows 8, you will need to start Windows PowerShell with admin rights.<\/p>\n

14:34 C:\\> get-vm | select name, resourcemeteringenabled<\/p>\n

Name                                                         ResourceMeteringEnabled<\/p>\n

—-                                                         ———————–<\/p>\n

c1                                                                             False<\/p>\n

C2                                                                             False<\/p>\n

DC1                                                                            False<\/p>\n

sql1                                                                           False<\/p>\n

Enabling Resource Metering<\/h2>\n

Well, the next thing I need to do is to enable Resource Metering. To do this, I use the Enable-VMResourceMetering<\/strong> cmdlet. I can enable Resource Metering for a specific machine, such as for SQL1, by specifying the –VMName<\/strong> parameter. The command to do this is shown here (keep in mind that nothing returns from this command).<\/p>\n

Enable-VMResourceMetering -VMName sql1<\/p>\n

Exam ALERT<\/strong>   The default parameter set for the Enable-VMResourceMetering<\/strong> is VMName<\/strong>, and therefore, you can simply supply the name of the virtual machine Enable-VMResourceMetering<\/strong> SQL1. But, there are three parameter sets: VMName<\/strong>, VM<\/strong>, and ResourcePoolName<\/strong>. To make matters worse, ResourcePoolName<\/strong> has an alias of Name<\/strong>. Keep in mind, VMName<\/strong> is the name of the virtual machine, VM<\/strong> is a virtual machine object (such as returned by Get-VM<\/strong>) and ResourcePoolName<\/strong> and Name<\/strong> are the names of virtual machine resource pools. There is no alias for VMName<\/strong> or VM<\/strong>. The following illustrates available parameter aliases.<\/p>\n

15:31 C:\\> gcm Enable-VMResourceMetering | select -expand parameters | % {$_.values} |<\/p>\n

? aliases | select name, aliases<\/p>\n

Name                                       Aliases<\/p>\n

—-                                       ——-<\/p>\n

ResourcePoolName                 {Name}<\/p>\n

Verbose                                    {vb}<\/p>\n

Debug                                      {db}<\/p>\n

ErrorAction                                {ea}<\/p>\n

WarningAction                           {wa}<\/p>\n

ErrorVariable                              {ev}<\/p>\n

WarningVariable                         {wv}<\/p>\n

OutVariable                                {ov}<\/p>\n

OutBuffer                                  {ob}<\/p>\n

 <\/p>\n

If I want to, I can enable Resource Metering on all of the virtual machines by piping the results from Get-VM<\/strong> to the Enable-VMResourceMetering<\/strong> cmdlet, as shown here.<\/p>\n

get-vm | Enable-VMResourceMetering<\/p>\n

Getting the Resource Metering report<\/h2>\n

To get the report of metered resources, use the Measure-VM<\/strong> cmdlet. The default parameter set is VMName<\/strong>, and therefore, the parameter can be left out. The VMName<\/strong> parameter accepts an array, and therefore, I can obtain information from more than one virtual machine at a given time.<\/p>\n

The following illustrates obtaining Resource Metering reports from one and from two virtual machines. The syntax is shown here.<\/p>\n

Measure-VM dc1<\/p>\n

Note<\/strong>   When a virtual machine is offline, it reports 0.<\/p>\n

The following image illustrates using this command, as well as the command to measure two virtual machines.<\/p>\n

\"Image<\/a><\/p>\n

Getting a metering report for all virtual machines<\/h2>\n

I can use the Get-VM<\/strong> cmdlet and pipe the returned VirtualMachine<\/strong> objects to the Measure-VM<\/strong> cmdlet to obtain a report on all of my virtual machines. The command is shown here.<\/p>\n

get-vm | Measure-VM<\/p>\n

The command and its output associated used to measure all virtual machines are shown in the image that follows.<\/p>\n

\"Image<\/a><\/p>\n

But realize this IS Windows PowerShell, and therefore, everything is an object. This means I am not limited to the output appearing above. I use the Get-Member<\/strong> cmdlet (gm<\/strong> is an alias) to see what my options are. The command and its output are shown here.<\/p>\n

16:02 C:\\> get-vm | Measure-VM | gm -MemberType *property <\/p>\n

TypeName: Microsoft.HyperV.PowerShell.VMMeteringReportForVirtualMachine <\/p>\n

Name                        MemberType    Definition<\/p>\n

—-                        ———-    ———-<\/p>\n

AvgCPU                      AliasProperty AvgCPU = AverageProcessorUsage<\/p>\n

AvgRAM                      AliasProperty AvgRAM = AverageMemoryUsage<\/p>\n

MaxRAM                      AliasProperty MaxRAM = MaximumMemoryUsage<\/p>\n

MinRAM                      AliasProperty MinRAM = MinimumMemoryUsage<\/p>\n

TotalDisk                   AliasProperty TotalDisk = TotalDiskAllocation<\/p>\n

AverageMemoryUsage          Property      System.Nullable[int] AverageMemoryUsage…<\/p>\n

AverageProcessorUsage       Property      System.Nullable[int] AverageProcessorUs…<\/p>\n

ComputerName                Property      string ComputerName {get;}<\/p>\n

MaximumMemoryUsage          Property      System.Nullable[int] MaximumMemoryUsage…<\/p>\n

MeteringDuration            Property      System.Nullable[timespan] MeteringDurat…<\/p>\n

MinimumMemoryUsage          Property      System.Nullable[int] MinimumMemoryUsage…<\/p>\n

NetworkMeteredTrafficReport Property      Microsoft.HyperV.PowerShell.VMPortAclMe…<\/p>\n

TotalDiskAllocation         Property      System.Nullable[int] TotalDiskAllocatio…<\/p>\n

VMId                        Property      guid VMId {get;}<\/p>\n

VMName                      Property      string VMName {get;}<\/p>\n

Sorting the output<\/h2>\n

I am not too impressed with the random order of the output. What I am concerned with is the amount of CPU utilization. So, I sort the output by AvgCPU (I know I can do this because of the output from the Get-Member<\/strong> cmdlet). Here is the command I use to sort the output by average CPU usage.<\/p>\n

get-vm | Measure-VM | sort avgCPU -Descending<\/p>\n

The command and its associated output are shown here.<\/p>\n

\"Image<\/a><\/p>\n

Well, that is about it for now. I want to head down to the beach and take a few pictures before it gets too late. Join me tomorrow<\/a> when I will continue this discussion about Hyper-V on Windows Server 2012.<\/p>\n

I invite you to follow me on Twitter<\/a> and Facebook<\/a>. If you have any questions, send email to me at scripter@microsoft.com<\/a>, or post your questions on the Official Scripting Guys Forum<\/a>. See you tomorrow. Until then, peace.<\/p>\n

Ed Wilson, Microsoft Scripting Guy<\/strong> <\/p>\n","protected":false},"excerpt":{"rendered":"

Summary: Microsoft Scripting Guy, Ed Wilson, talks about using Windows PowerShell 3.0 to do Hyper-V Resource Metering on Windows Server 2012. Microsoft Scripting Guy, Ed Wilson, is here. Well, Charlotte looked like someone had taken a huge can of polyurethane and sprayed the entire city—multiple times. Ok, so it is sort of pretty the way the city […]<\/p>\n","protected":false},"author":596,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[271,362,3,61,45,368],"class_list":["post-4251","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-hyper-v","tag-powershell-3","tag-scripting-guy","tag-weekend-scripter","tag-windows-powershell","tag-windows-server-2012"],"acf":[],"blog_post_summary":"

Summary: Microsoft Scripting Guy, Ed Wilson, talks about using Windows PowerShell 3.0 to do Hyper-V Resource Metering on Windows Server 2012. Microsoft Scripting Guy, Ed Wilson, is here. Well, Charlotte looked like someone had taken a huge can of polyurethane and sprayed the entire city—multiple times. Ok, so it is sort of pretty the way the city […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/4251","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/596"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=4251"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/4251\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=4251"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=4251"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=4251"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}