Virtualization Category



Don’t use Host Update Utility to patch Virtual Center managed ESXi servers

No Comments »

Just a friendly reminder folks! Do not use Host Update Utility (that easily installs with Vmware client) to update and patch ESXi servers managed by Virtual Center. It may break the config and you may experience problems in the future.

Remember that Vmware supported methods of updating ESXi servers are using vihostudate utility or burning the CD and installing from it.

Non-supported mode (and not recommended thought!) is to use “unsupported” mode and using esxupdate utility. Many folks report great success, but remember I haven’t recommended this method to you :)… Read the rest of this entry »


Cannot install the vCenter agent service. Unknown installer error

3 Comments »

If you have Virtual Center U1 installed you may experience ESXi servers disconnecting without a reason. After the host has been disconnected you cannot Connect/Add it back. The most common error when you try to add/connect ESXi host back to Virtual Center is:

Cannot install the vCenter agent service. Unknown installer error

From my very own experience this is a problem with / partition allocated too small. The VirtualCenter tries to upload specific .tgz files (for aam) and there is no free space available to extract the tgz file. I will post a quick fix shortly. Vmware has also … Read the rest of this entry »


Vsphere 4 U1 finally supports Windows 2008 R2 Enterprise, Standard, Datacenter, Web Server editions

No Comments »

On November 19, 2009 Vmware has released a new and updated list of new guest OS support and it’s been great news! Now vSphere 4.0 U1 fully supports Windows Server 2008 R2 Enterprise, Standard, Datacenter, and Web Server Editions.

The following new guest OS support has been added with vSphere 4.0 U1 (Update 1):

Windows 7 Enterprise, Professional, Ultimate and Home Premium Editions
Ubuntu 9.10 Server and Desktop
Debian 5.0.1, 5.0.2, and 5.0.3
FreeBSD 7.2

Good job Vmware!… Read the rest of this entry »


DL585 G5 HP Vsphere CIM providers – ESXi bundle

2 Comments »

Vsphere is a perfect choice for consolidating servers and to better utilize the hardware. We currently use HP DL585 G5 AMD powered workhorses powered by Vsphere 4.0 ESXi and Virtual Center reports hardware alert (under the tab Hardware Status):

1 Warning: System Board 8 ProcHot out of 111 sensors.

In vSphere 3.5 we easily solved the problem by installing HP ESXi CIM providers for Vmware 3.5. I went to the HP site and found HP ESXi providers for vSphere 4 (file name: hp-esxi4.0uX-bundle-1.1.zip). I downloaded and used vihostupdate.pl to update the server. Remember that you need to put … Read the rest of this entry »


An error occurred during operation: CheckAndAllocateCache

No Comments »

Not the first time  I see the following error:  An error occurred during operation: CheckAndAllocateCache when performing fresh Vsphere host update using Host Update Utility. You should ignore the error and rescan the host and patch the host again. Sometimes it works with the second try, sometimes, you have to reboot the box and it will work.

A complete log is attached below:

Patching 10.10.0.2

The patch operation has failed with this error: An error occurred during operation: CheckAndAllocateCache

Patching 10.10.0.2

Start uploading files to host

Metadata and binaries have been successfully uploaded

Scanning the host completed

Start installing patches

Read the rest of this entry »

vSphere host update utility proxy configuration

3 Comments »

Quite a few folks are running Vmware Vsphere behind the corporate firewalls. We do the same and experienced some problems with Host update utility.

It was quite hard to figure out how to specify the proxy settings so that our Host Update utility can easily check Vmware update servers (for folks who want to open direct access the update server name is hostupdate.vmware.com ) for latest patches.  So we finally figured it out and here are the necessary steps:

Open the VIUpdate folder (in our case: C:Program FilesVMwareInfrastructureVIUpdate 4.0 ) and find file named settings.conf

Open it in text editor … Read the rest of this entry »


Migrating from 3.5 to Vsphere – Bios updates

No Comments »

It’s been very recommended to upgrade BIOS 4 to BIOS  7 if you are migrating your Virtual Infrastructure 3.5 servers to Vsphere 4. You will experience much better performance using Vsphere 4 and don’t forget to upgrade BIOS. You can do it by shutting down virtual machine and right-click the mouse on the machine name in the inventory. You will notice a new menu appearing “Upgrade virtual hardware”. You can click it and upgrade BIOS in a few seconds, BUT REMEMBER TO TAKE A SNAPSHOT before doing it or there is no way to return the virtual BIOS to version … Read the rest of this entry »


Vsphere performance boosts for migrations

No Comments »

We have been migrating quite a few physical servers to Vsphere infrastructure and I strongly suggest re-installing servers from scratch rather than using Converter to do actual migration. From my experience if you are doing migrating SUSE SLES 10 SP 2 and others, it’s better to install a server (virtual guest OS)  from scratch and do application migration.

You will experience much better performance and no problems with drivers, BIOS 4 to BIOS 7 upgrades and so on.… Read the rest of this entry »


The operation is not allowed in the current state of the host

1 Comment »

Yesterday I was trying to hot-clone one production server in Vsphere and got the error:

The operation is not allowed in the current state of the host

Finally, I figured out where was the problem. I had running multiple servers in a HA cluster (with DRS activated) and one of the hosts were in a maintenance mode. This was the problem – I removed the maintenance mode and hot-cloning worked perfectly.… Read the rest of this entry »


Vmware Virtual Center HA cluster agent error

Comments Off on Vmware Virtual Center HA cluster agent error

If you are running Vmware Virtual Center 2.5 and see the following error logs:

HA agent on HOSTNAME in cluster CLUSTERNAME in DOMAIN has an error : cmd addnode failed for primary node: unable to import /var/log/vmware/aam/aam_config_util.def

It means that you need to run “Reconfigure for HA” on every HA cluster starting with the other Hosts before you do it with a host with red-flag.

Many folks suggest removing the host from the HA cluster and then reconnecting, but I have done it many times by using Vmotion some machines to other hosts that are not so overloaded and then … Read the rest of this entry »