Yellow Bricks

by Duncan Epping

VirtualCenter

VM’s automatically renamed

· ·

Yesterday evening I witnessed a weird phenomenon. We had to bring down a complete environment to move a 19″ rack to a different location. We switched the SAN on, waited a couple of minutes and switched the ESX hosts on. When the ESX hosts finished booting we booted the VirtualCenter. Everything looked normal in the VI Client. I had all connections to the SAN and all ESX Hosts were up and running. So I decided to power up the first VM, it was a VM named LNX01. Within a second the VM got renamed to LNX05(1). I though I was going nuts. I checked the settings of the renamed VM and indeed it was pointing out to the LNX05 diskfiles/vmx.

Maybe it was just me, or this one VM so I decided to give another one a try, I powered up LNX02. Same happening here, within a second the VM was renamed to PS01(1) and booted fine. The settings were pointing out to PS01. I checked a couple of VM’s but could not find anything weird. I restarted the VirtualCenter service just to be sure. I started the VM LNX03 and again it was renamed… Than I decided to restart the “mgmt-vmware” services on all of the ESX hosts and the problem never returned again. It seems like VirtualCenter had a different view than the ESX hosts had. But I can’t think of a logical reason what could cause this. I searched the knowledge base but could not find any related problems, well besides an old article based on VirtualCenter 1.2.

Powershell VI Toolkit

· ·

Today I combined a couple of Powershell scripts which as a result gives a nice html formatted file with a table. This table contains all VM’s with their VMware Tools status and version. I’ve uploaded the script here. The outcome looks like the following:

As you can see, the VMware tools status is “ok” but the versions are totally out of line. I know there are already a few tools handling this but as far as I know none of them creates a text/html output file.

Performance stats gone

· ·

Clint discovered the following:

Source –
Ran into a problem while doing some performance testing on some test VMs. We found that we had no historical performance data for the VM or Host. All we had was real time data. This can be a major issue, especially when you are trying to troubleshoot or like in this case get performance data for a performance test! My co-worker did some research and found that we are not an isolated event. This is a bug in VC 2.5.

The Fix

We found a few references to doing a “repair” install of VC 2.5. So we went ahead and tried it and it worked. We also found references to the performance data getting corrupted. In that case they had to restore the database to a prior dataset and re-install the VC.

I’ve seen the same at several customer sites and indeed the fix that Clint describes, repair of VirtualCenter, works.

Customization specifications fails during entering password

· ·

For some weird reason the customization specification wizard in VirtualCenter 2.5 fails when entering the administrator password. The error: An internal error occurred, and the wizard is unable to store the administrator password securely.

After reinstalling VirtualCenter the error still occurs. I googled the error and stumbled upon this VMware KB but this did not solve my problem…. I’m lost, anyone?