Recall there are at least two separate issues:
(A) glibc libraries break vmware-hostd which cause it to crash and sometimes bring down the virtual machines with it.
(B) firefox on the local machine is unable to connect to the web interface over ssl (https)
These are distinct, though confusingly have been reported in the same bug report http://bugs.centos.org/view.php?id=3884
(A) glibc and vmware-hostd issue
The two old solutions have been well publicized:
which both involve retaining the old glibc libraries (either for the whole machine, or by attempting to load the old library in the vmware startup script). Though the first solution did work for me (the second did not), I am reluctant to retain these old libraries. You can also install a vnc server on your guests to access them without the web interface, though I often found that crashing vmware-hostd would kill the VM machines too.
There is another option which does not involve maintaining the old glibc libraries which I found here (solution 2):
http://webalution.com/techshare/2009/11 ... rkarounds/
You modify the vmware startup script (/etc/init.d/vmware) to avoid the dynamic loading of the library and start the vmware-hostd process directly: The modifications to the script are shown below:
- Code: Select all
# Start host agent
vmware_bg_exec "`vmware_product_name` Host Agent" \
"$vmdb_answer_LIBDIR/vmware-hostd" -a -d -u "$vmware_etc_dir/hostd/config.xml"
# "$vmdb_answer_SBINDIR/vmware-hostd" -a -d -u "$vmware_etc_dir/hostd/config.xml"
This fix has given me a stable interface to the vmware system and my virtual machines for over a week. Your mileage may vary.
(B) Connecting via ssl using firefox to the web interface locally to the server
Obviously one work around is to connect over the non-ssl interface on (default port 8222).
There is another way (which I found here http://planetvm.net/blog/?p=1087).
You enable ssl2 in firefox: You go to the advanced configuration in firefox by typing about:config in the location bar (note and accept the warning) and then scroll down to the setting:
and click on it to toggle the boolean to true, then restart firefox. I was then able to connect to the vmware web interface using port https 8333 and open consoles as I once was able to previously under CentOS 5.3 and earlier. (No deleting of certificates needed despite the suggestions on the web).
As many people have reported, vmware server does not seem to be actively maintained by vmware, so the long term solution for me is probably to migrate to kvm, but that will have to wait for a slower day when I can muddle though usb pass through. Note that for those of you experimenting with both kvm and vmware, if your virtual machines fail to start (hanging at 95%) it is because you have forgotten to unload the kvm kernel modules before restarting vmware.
I hope this is of use to some people.
[Moderator edited to insert code tags to preserve the formatting.]