For users who plan for an upgrade in the near future or any new deployment, I will suggest you to deploy all your ESX host with ESXi for the ease of upgrade or migration. The upgrade process is pretty straight forward from version 4 to version 5 without any big hassle.

Related posts:

1. VMware Just Launch vSphere 5 with Major Changes
2. Confused Explaination from VMware about New License Scheme on vSphere 5
3. Major Changes on Nexus 1000V Version 1.3 to 1.4

Basically I will not discuss How To Install PowerChute Network Shutdown on VMware ESX /ESXi again and you may refer to APC official link here.

If you’re try to install APC PCNS 2.2.4 on vSphere Management Assistant (vMA) 4.1 and I’m sure you will get the similar error like “This version of PowerChute Network Shutdown only support VMware ESXi” which I think APC teams should it much more clear. The error message caused by APC PCNS (ver 2.2.4) setup file – “install.sh” which check on “/etc/vima-release” file. In the vMA 4.1 released, you’re can only found “/etc/vma-release” file which changed recently. Create a symbolic link or edit the installation script can temporary ignore these error message. See this link.

Unfortunately, the solution as above does not help much. I found another serious problem which the connectivity between the ESXi 4.1, vMA 4.1 and PCNS 2.2.4 authentication problem due to “/opt/APC/PowerChute/group1/bin/shutdownhost.pl” and “vi-fastpass”.

To cut the story short, I would suggest you go with vMA 4.0 and just ignore vMA 4.1 until APC solve the problem. Again, you may consider William Lam post “Why you should upgrade from vMA 4.0 to vMA 4.1”

The solution are pretty simple.

Option 1:
1. Turn OFF VMware HA on Cluster Feature setting.
2. Enable VMware HA setting again.

Option 2:
1. Enter maintenance mode
2. Remove ESXi hosts from cluster
3. Add ESXi hosts back to cluster
4. Exit maintenance mode

Done! The annoying warning message will go away.

1. First, you press Alt + f1 then type “unsupported” and press enter.
2. You will see the prompt for password after this. Key in the root password you had previously configure, and you will be able to log in to the service console.
3. Follow by that, do a vi /etc/xinetd.conf and look for #ssh. Remove the # and save the file after this.
4. Go to /sbin, and run this command ./services.sh restart
5. Noted: If you still having problem with SSH access, please restart and it should be work.

You will have your SSH enable now. Have fun.

Latest updated 12/08/2010:
Using Tech Support Mode in ESXi 4.1

Get a free license for VMware ESXi and build virtual machines in minutes with this easy-to-deploy, OS-independent hypervisor.

Check out more details about VMware ESXi free edition here.

Frankly speaking, I’m big fans of VMware and I would like to share the related news – Microsoft Hyper-V jokes.

Microsoft to do what VMware does nearly 10 years later – From Mike RTFM

ESX Server beats Hyper-V – DanteDog’s Blog

So how important is LiveMigration/VMotion now?

Hyper-V, not in my datacenter Part 1 – Gabes Virtual World

Hyper-V, not in my datacenter Part 2 – Gabes Virtual World

Hyper-V, not in my datacenter Part 3 – Gabes Virtual World

Will Microsoft sunset VMware? – 18 months later

Hyper-V with Server Core — Too Dry and Crunchy for our Taste

Hyper-V Server is Finally Here – But What Exactly Is It?

VMware ESX VMotion vs Microsoft Hyper-V Quick Migration, are they really comparable?

How VMware ESX performance trumps Hyper-V’s price.

What do you think? Please feel free to share with us.

Download VMware workstation, VMware ESX 3.5 and ESXi and start your testing now!

Look at the video.


An video uploaded by DaviD Davis from TrainSignal.

Installation – ESX 3.5i had advantages as the entire process is fast and simple. ESX 3.5 require more interaction as it looks similiar to Linux installation. I know the ESX 3.5 can be script and customize by using the ks.cfg which I had done previously for mass deployment. For comparison 1 to 1, ESX 3.5i is much more easier and faster.

Configuration – Basically I dun really find much different as I do manage this machine with my virtual center. The only different is the Linux connection and command no longer usable on ESX 3.5i. By the way, I read some artical to tweak around to make the SSH work on the 3.5i, but I will prefer to proceed with powershell or CLI if I do need to use command prompt.

Perfomance – ESX 3.5i had better through put. In my test, I created 3 VM which 2 of them running on Windows 2003 SP2 with 4GB memory and 4Vcpu, plus additional 1 VM with SUSE Linux. I did the same on ESX 3.5 too. The respond on the ESX 3.5i is much smooth and not lacking, as ESX 3.5 you will see some lacking from the console open on Virtual center.  Follow by file copy test, the VM on ESX 3.5i is slightly faster than ESX 3.5. just less than a minute faster which I tried to copy some file with 20GB. Beside these points, I had not found anything different.

Manage ability – ESX 3.5 will still be the best, as there are none of the software vendor will guarantee bugless on their products. If the ESX 3.5 having some technical issue, it can be easily troubleshoot and anlayze from the Linux command which is more familiar with. ESX 3.5i still have a gap to be close up as is still new to most users yet.

Here is all my finding and I will post more in the future for any new finding