Malaysia VMware Communities

SRM version 4 had officially released and ready to download from VMware Official Website. Before this, users with SRM will not able to upgrade to vSphere 4 due to the SRM compatible. Now you will be excited to upgrade your existing ESX 3.5 to vSphere 4 with SRM 4. You can read more about SRM 4 from here. You can download the latest copy of SRM 4 from here.

Long distance VMotion had been officially supported since Sep 2009.

Read more »

I found the white paper been published by Hal Rosenberg from VMware regarding the performance troubleshooting guide on VMware vSphere 4. The document is very details and helpful, and I would like to recommend to everyone as a technical reference which may be helpful for every ESX administrator. You can download the document from here

I am currently doing some test to simulate the real update requirement for my production VMware Farm to be upgraded from ESX 3.5 to vSphere 4. To minimize the impact to our production system, we may want to do this with as minimal impact as possible. Due to the virtual hardware version and tools upgrade require, is pretty tough for us to perform the entire upgrade at 1 time. Therefore, our plan is get the host upgraded and follow by each individual virtual machine to be upgraded follow the suitable timing for different business unit. HA and DRS will need to be disable temp during the ESX upgrade.

I am able to get the ESX 3.5 to be manage by the latest vcenter. A vmotion from ESX 3.5 to vsphere 4 had been successes too, but the latest version of virtual machine which built from vSphere 4 might not compatible to vmotion back to the ESX 3.5 hosts. At the same time, if you have different processors chipset in the environment and require EVC to be turned on, it may be a little challenge to do so. You may want to ensure the EVC to be done with no down time.  You may need to refer to my previous post about how to enable EVC with no down time.

Read more »

To have SSH enable on vSphere 4i is always important and helpful when you require to troubleshoot any problem you may face. The way to get this done should similar as esx 3i.

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.

Read more »