Keeping Up With VMworld 2009

If, like me, you couldn’t get to Cannes this year then all is not lost. You can keep up with what’s happenning almost as it happens and still keep working. Many of the attendees are tweeting the major annoucements and updates of what they are doing. Follow them on Twitter and they’ll keep you up to date. Alan Renouf (Virtu-Al) maintains a list of VMware twits on his blog and even has a PowerShell script that will enable you to follow them all on Twitter.

Read More

HA Agent on ESX-HOST in cluster CLUSTER-NAME has an error

If I wanted to, this could be a very big post all about configuring HA correctly. But I don’t want to reinvent the wheel. Instead I just want to share my experiences with this error:

HA Agent on ESX-HOST in cluster CLUSTER-NAME has an error

Odds are that you will eventually see this one pop up in vCenter for one of your ESX 3.x hosts. If you’re not sure what it means, well the translation basically is that the host displaying the error could fail and your VMs running on it probably won’t get started up automatically on another host. Essentially HA is broken on the host. (more…)

Read More

vCenter 2.5 Update 4 released

Update 4 of vCenter 2.5 (the management tool for VMware’s Virtual Infrastructure) has been released. Not a huge number of new features and probably a few bug fixes is about all you’re going to get from it. The release notes can be found here. vCenter now supports the customisation of Windows 2008 guest operating systems as well as introducing a Performance Overview plugin that provides a single view of performance metrics – I look forward to having a look at that.

Read More

Communication with the virtual machine may have been interrupted

I was trying to power up a new VM on an ESX 3.5 host just now and I got the following error: “A general system error ocurred: The system returned an error. Communication with the virtual machine may have been interrupted” Nice and helpful! It appears that there are two ways to fix this. The first is to reboot your ESX host. Of course this isn’t normally practical and you may have VMs running. The alternative is to make your way into the service console and issue the following command:

Assuming that no errors are displayed as the service is restarted you should be sound as a pound (although these days the £ isn’t worth much).

Read More