Hello Matthias,

I also faced this problem yesterday, when checking the system after update to Fedora 14 was completed. And I was also in a hurry because I needed VMware Server in working order for my daily work.

It seems the libc library provided with glibc package in Fedora 14 is not compatible with VWware Server anymore. I used glibc and zlib packages from Fedora 13 and was able to restart VMWare Server in Fedora 14.

Execute as root:

1. mkdir fedorafix

1. cd fedorafix

1. wget http://www.mirrorservice.org/sites/download.fedora.redhat.com/pub/fedora/linux/updates/13/x86_64/glibc-2.12.1-4.x86_64.rpm

1. wget

http://www.mirrorservice.org/sites/download.fedora.redhat.com/pub/fedora/linux/releases/13/Fedora/x86_64/os/Packages/zlib-1.2.3-23.fc12.x86_64.rpm

1. rpm -Uvh --nodeps --root=/tmp/ glibc-2.12.1-4.x86_64.rpm

1. rpm -Uvh --nodeps --root=/tmp/ zlib-1.2.3-23.fc12.x86_64.rpm

1. cp -Rp /tmp/lib64/ /usr/lib/vmware/lib/fc13lib64

Then edit as root /usr/sbin/vmware-hostd and and this line before the last one:

export

LD_LIBRARY_PATH=/usr/lib/vmware/vmacore:/usr/lib/vmware/lib/libexpat.so.0:/usr/lib/vmware/lib/libxml2.so.2:/usr/lib/vmware/lib/fc13lib64

Restart VMware service. I got then VMware Server working again.

This problem drove me crazy, as I really needed to have this working again as soon as possible. I have posted in my blog the full story about the problem and the search for a solution (sorry, in spanish).

Hope this helps you too.

Regards,

                  Victor

I forgot the patch URL:

http://www.sputnick-area.net/scripts/vmware7.1.1-patch-kernel-2.6.35.bash

(the same for Ubuntu)

I think the previous solution is non good, al last it's a downgrade of OS!

I don't understand because vmware not mark this product as RETIRED:

at every upgrade of kernel OS we have always the same problems,

and we must stop to use it and wait patch from unofficial source.

I'm not glad if this will happen in future, Vmware Server it's a perfect product

for open source, ma work in this way every time it's a bit crazy.

What we think about ?

AZ

Hi Victory,

I believe you so I'll try your solution.

Your new problem is a very old problem for vmware. A lot of documentation exist about this.

You try to disconnect every unusefull virtual hw (cdrom, sound card, and so on ...) e try to uncheck

the sync of timer fron vmtools for example, Try also to disable memory trimming.

No idle time exist in a virtual world , believe me

Oh my old ancient time, when only hardware interrupt live in my computer.    

If still getting a crash (after having created the first VM and restarted) try this workaround:

http://communities.vmware.com/message/1670144#1670144

Basically you have to rename/disable the libxml2 provided by vmware.