Sunday, May 16, 2010

CentOS 5.5 (and VMWare 2.0.2)

Yesterday the CentOS version 5.5 has been released. It is only few weeks after the Red Hat 5.5, this last update of CentOS was rather quick compared to the previous one.
So, time to try it.
I was especially looking for a solution for the issue I got within VMWare 2.0.2 on CentOS 5.4 as I described few months ago here.
So, before the upgrade I dropped the extra file I used to workaround the issue (please, read the article linked above), then after running a simple “yum list updates” and “yum update”, the system is upgraded :
[root@hercules /root]# rpm -q centos-release
[root@hercules /root]#
I bounced the server, then run a “” from VMWare software binaries, and eventually everything is working fine. The system is stable, the VMWare webserver is not hanging and works fine. No need anymore the workaround needed on CentOS5.4 to downgrade some of the packages…
Thanks to the CentOS team for their hard work and to deliver this update so fast !


Update (17-May-2010) : you may still have issues on some circumstances… please, read my comment below.


Tim... said...


Good to know. I recently reimaged one of my servers with 5.4. Yesterday I did a yum update and got it to 5.5. I left the old workaround in place and it worked fine that way too.

Based on your experience, when I get home I'm might remove the workaround. It will feel cleaner that way. :)



Gasparotto Nicolas said...

I'm afraid, on some circumstances it does not work... Everything worked fine until I use command line to stop and start VMs (I have several scripts to manage all my VMs stop/start), since then the WebServer keeps crashing. It seems it keeps working only when you are using the Web Interface, but not with OS command line...
So, you can stay on old version of the guilty RPMs or, as I did, you can use the solution #2 described here below (that's better, it is only impact your VMWare software) :
In brief : download glibc-2.5-34 from CentOS5.3, and modify the file vmware-hostd to add the mentioned glibc path to LD_LIBRARY_PATH

I think we have no choive but wait for a real update from VMWare.