Malaysia VMware Communities

With the surprise of new license structure change from VMware, it had impacted large number of the existing customers which may end up required to double or triple their existing CPU license if they require to upgrade to vSphere 5. This was mainly cost by the cap happen per CPU sockets which is only 48GB each even for Enterprise plus. There are many users start to evaluate alternative solution such as HyperV, Citrix Xen and KVM now due to the large impact on software cost may be added to the existing environment.

Imagine you have a 2 way server with 192GB memory now, you will require to purchase 4 sockets license to entitle the VRAM for 192GB. Honestly speaking, the new license structure doesn’t sound to be green and really make the existing users getting harder to defend the decision to stick with VMware. VMware are not promoting high consolidation anymore while force you to buy more license or consider a smaller server to be deployed in your infrastructure.  No matter how they spin about the flexible licensing scheme, I think many smart users feel upset with the new model they released. Providing a choice, there will be many users choose to remain at version 4.1 without upgrade and start looking into option as HyperV, XEN or KVM. VMware are opening bigger door to their competitor to challenge their market share.

Read more »

VMware had recently announced new version of vSphere 5.0 since two days ago. There are a lot of new capabilities in there but the down side could be also a major change in the software licensing scheme.

Here is a quick summarize of the new capabilities of vSphere 5. With the new licensing option, some of you may require to upgrade the existing license. If you looking at upgrade your existing license, kindly please refer to the picture below for reference.

for the full review of the new vSpehre 5, I highly recommend you to go through the official documentation here.

Read more »

I had receive the notification email from John Troyer Vmware Inc today which notify myself that the award of vExpert 2011 had been announce and I am one of them. I would like to thank the team who involve for the evaluation and of course to Mr John Troyer who had been working very hard every year to run this program.

I am here promised to continue my contribution for the virtualization community in the future with the best interest of knowledge sharing to the world wide users.

Thanks VMware !!!!!!!!

Read more »

My Client had a weird issue recently on 1 of the production vSphere 4.1 host. Error message shown on summary tab as ” DRS is not able to function normally cause by insufficient resource”.This is not the exact message as I can’t remember the full error message, but it represent the similar meaning of the error. This message had been alerted for more than a week as we thought the mgmt-ware restart command should able to fix this.  The system is currently in production, therefore we are suggesting to vmotion out all the production VMs, and put the host to maintenance before we issue the command.

Read more »

Microsoft SQL 2008 R2 had been officially supported for VMware vSphere 4.1 update 1. Previously it doesn’t supported if you are not on update 1. I just did an upgrade yesterday and here is some finding to share. 1st, I tried to perform an upgrade as usual, and of course I retain all the database information to prevent reconfiguration and performance data lost for the previous environment. Unfortunately, the update manager portion had given error which it not allowed us to continue the installation. It left me no choice that a re installation will be required. If you hit to the same situation, do not panic as your previous configuration will still retain, and no down time require even you are on dVswitch. Ensure no host name changes in this case will be safe enough for you to proceed further.

During the re-installation, you I will suggest you follow the sequence to un-install all the vCenter application 1 by 1. Update Manager required to be un-install before you uninstall the vCenter server. You can backup and re-attach the SQL DB as the MDF and LDF files is in place. If your vCenter is on virtual environment, strongly recommend a snapshot taken before any changes been made. Once you re-attach the DB, you will require to perform the DSN connections to be created from ODBC.

Here is the tricky part you need to take note. It take me 2 hours to figure out due to some confuse and mistake. vCenter Server will able to run on 64 bits DSN as standard, you will not face any issue on that. When come to update manager, DO NOT try to access the ODBCAD32.exe from start run directly on windows. It will point you to the 64 bits ODBC configuration tab. You will require to browse to the path directly as :

%systemdrive%\Windows\SysWoW64\Odbcad32.exe

Read more »