Basically...

Post #331,211 by folkert 8/12/10 10:38:11 AM Reply	Basically... Don't run VMWare server v2.0.x on CentOS newer than v5.3 If you DO want to run it on CentOS v5.latest (or are forced to) You MUST do this. Assumptions here is X86_64 processor and CentOS version for 5.x. Download from CentOS v5.3 archive locations: glibc-2.5-34.el5_3.1.x86_64.rpm Extract "libc-2.5.so" from that rpm. Make a directory called: /usr/lib/vmware/lib/libc.so.6 Copy your "libc-2.5.so" into that directory as /usr/lib/vmware/lib/libc.so.6/libc.so.6 Then edit: /usr/sbin/vmware-hostd Make this the second to last line of the script: export LD_LIBRARY_PATH=/usr/lib/vmware/lib/libc.so.6:$LD_LIBRARY_PATH And start as normal and watch you stability issues go away. Don't ask me how I know this.
Post #331,212 by mvitale 8/12/10 10:51:45 AM Reply	How do you know this? (Muah. You knew it was coming.) -Mike "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." - Benjamin Franklin, 1759 Historical Review of Pennsylvania
Post #331,214 by jake123 8/12/10 11:26:42 AM Reply	pfiles and the debugger would be my guess.
Post #331,220 by folkert 8/12/10 12:34:29 PM Reply	and strace and gdb Plus, once I found what it was looking for the VMWare forums actually had someone that figured it out as well. That is where I got the editing of the file from.
Post #331,223 by jake123 8/12/10 1:20:02 PM Reply	Ah, good ol' strace but I was always under the impression that gdb was the debugger... ;) ...and of course, there's always the win of being able to follow someone's footprints!
Post #331,242 by static 8/12/10 7:24:18 PM Reply	So they've built it against an older glibc? That's more than a bit daft. And lazy. It shouldn't be hard to build it against something current. Or is RedHat to blame? I wouldn't put it past them; they like doing little things that they think are "better" that everyone else ignores. Wade. Q:Is it proper to eat cheeseburgers with your fingers? A:No, the fingers should be eaten separately.
Post #331,247 by folkert 8/12/10 9:38:14 PM 8/12/10 9:38:42 PM Reply	Its RedHat's issue... (and VMWare's) 5.4 introduced some seriously incompatible Virtualization tech to VMWare. Shortly after that VMWare decided to effectively abandon the product. EOL is September 2011. Since VMware Server in in Maintenance Mode... IOW not to be updated anymore. I'm not sure what I'm gonna use to replace it, as I don't wanna go redo things... deprecation is the only way. Edited by folkert Aug. 12, 2010, 09:38:42 PM EDT Expand All History

Welcome to IWETHEY!