Now that I believe I've resolved my hardware issues with my VMware server, I'm expecting to use it much more. I'm also continuing my exploration of the PowerCLI tool set which allows me to manage my virtual infrastructure from a Windows PowerShell session. One task that I frequently need is to identify which virtual machines are running, and especially the guest host name. Last week I tweeted a PowerShell one-liner.
\n[cc lang=\"powerShell\"]
\nget-vm | where {$_.powerstate -match \"on\"} | get-vmguest | select State,VMName,Hostname,OSFullname,IPAddress
\n[\/cc]
\nThis finds all virtual machines that are powered on then pipes that object to the Get-VMGuest cmdlet which returns the information I'm really after. Here's a sample result.
\n[cc lang=\"Powershell\"]
\nState : Running
\nVmName : MyCompany Windows 7
\nHostName : Win7Desk01.MYCOMPANY.LOCAL
\nOSFullName : Microsoft Windows 7 (64-bit)
\nIPAddress : {172.16.10.90}
\n[\/cc]
\nNow, I could have simply saved that one-liner as a function or script block but naturally I had to take things a step further. I wanted a function that would also include some error handling and handle a connection to my VM host if it wasn't already connected. Thus was born Get-RunningVM.
\n[cc lang=\"Powershell\"]
\nFunction Get-RunningVM {<\/p>\n
Param([string]$VMhost=\"ESX\",
\n [string]$protocol=\"https\",
\n [string]$port=\"443\",
\n [string]$user=\"root\",
\n [string]$password)<\/p>\n
#verify we're connected to a VM host
\nTry {
\n if (get-vmhost -Server $VMhost -State connected -erroraction \"Stop\") {
\n $connected=$True
\n }
\n}
\nCatch {
\n #Try to connect
\n Try {
\n $viserver=Connect-VIserver -Server $VMhost -protocol $protocol -port $port -user $user -password $password -errorAction \"Stop\"
\n $connected=$True
\n }
\n Catch {
\n $msg=\"Failed to connect to server {0} on {1}:{2} as user {3}\" -f $vmhost,$protocol,$port,$user
\n Write-Warning $msg
\n Write-Warning $error[0].Exception.Message
\n }
\n}<\/p>\n
#if we're finally connected to a host, get running VMs
\nif ($connected) {
\n #get the powered on VMs and display VMGuest information
\n get-vm | where {$_.powerstate -match \"on\"} | get-vmguest |
\n select State,VMName,Hostname,OSFullname,IPAddress
\n}<\/p>\n
} #end function
\n[\/cc]
\nThe function requires that the VMware snapin already be loaded. I have a nested set of Try\/Catch constructs to check if I'm connected to VM host and if not, to do so. Once connected I execute my one-liner. I'm using basic, default connection information for my host since I'm not in a large enterprise environment. You might need to tweak the parameters. In fact, since I only have a single VM host, I'm not sure what other tweaks might be necessary for a multiple server environment. I'd love to get some real-world feedback on that. In fact, you will have to edit the default parameter values since the default VMHost is my server name. Using default values saves a lot of typing.<\/p>\n