As of VMware VirtualCenter 2.5 Update 1, ESX Server 3i systems can only be added to an HA cluster if the system has swap enabled.
This article applies to:
- VMware ESXi 3.5.x Embedded
- VMware ESXi 3.5.x Installable
- VMware VirtualCenter 2.5.x
ESX 3i Servers with swap not enabled will show the following message(s):
An error occured during configuration of the HA agent of the host.
HA Agent has an error : Host in HA cluster must have userworld swap enabled.
To enable swap on the ESX 3i Server:
Just a quick update on my earlier posts regarding ESX 3.5 on the HP ProLiant ML110 G5 and the HP Proliant ML115 G5. I have now been informed by posts on http://www.techhead.co.uk/ that the embedded NIC in these servers are now supported by VMware ESX Server 3.5 Update 2.
I have not tried to install ESX 3.5 Update 2 on these servers, so I can't speak from my own experience just yet, but information can be found here.
VMware has released an Express Patch to counter the problem with the original ESX/ESXi 3.5 Update 2 which casued the server licenses to expire as of 12 August 2008. This patch and more information can be found at: http://www.vmware.com/go/esxexpresspatches
In the meantime, VMware has also re-issued the entire ESX/ESXi 3.5 Update 2 release. They are available for download at http://www.vmware.com/download.
We know now that VMware ESX Server 3.5 works well with the HP Proliant ML110 G5. So, I thought I'd try running it on the HP Proliant ML115 G5. This however did not go as well a I thought it would.The integrated NIC in both the ML110 and ML115 is not supported, that I knew, so I installed an Intel Pro1000 GT NIC in the ML115. This card is supported so I was able to install VMware ESX 3.5 on the ML115 with no problems at all.
However, when the server booted up and started loading the VMKernel modules... that was where it all went horribly wrong. The server could not mount the root partition!!! Read on, because there is a fix to this problem.
Those of us who have tried running Veeam FastSCP on 64-bit Windows found that it installs perfectly, but once you try and run the application, it comes up with an error. Someting like "Unable tp connect to (local\VEEAM)".
It's sad to say, but Veeam FastSCP does not support 64-bit operating systems at this moment in time. However I found a little workaround that will allow you to use the application on 64-bit Windows, at your own risk and unsupported it has to be said.
So here's how:
1. Download the Microsoft .NET Framework 2.0 SDK (THE 64-BIT VERSION!) from the Microsoft Website. This download is about 300MB if I remember correctly.
2. Install the SDK on the 64-bit machine that you would like to run Veeam FastSCP on.
3. Now, open a command prompt (Start -> Run -> Type "cmd" -> OK)
4. Change directory to: C:\Program Files\Microsoft.NET\SDK\v2.0 64bit\Bin
5. Now Run: corflags "C:\Program Files (x86)\Veeam\Veeam Backup and FastSCP\VeeamShell.exe" /32BIT+
6. Now when you try and run Veeam FastSCP again, it should work fine.
(C) 2008 Article from ZDNet by Dan Kusnetzky
Virtual machine overhead has been part of the folklore for quite some time. I’ve heard it described as the “virtualization tax” by those opposed to the use of this technology. In the past, they may have been right. A technology that offered consolidation, agility and yet imposed a 15% to 20% performance overhead clearly wouldn’t be the proper tool for performance sensitive workloads. VMware’s Richard McDougall (Chief Performance Architect) brought that topic up and, in my view, successfully put it to bed.