The vmware serverd log shows nothing particularly interesting, and I have reconfigured the vmware twice to try and fix this (which interestingly enough could not find the vmware modules for my os either time).
I am running CentOS 5.0 with all the latest updates through this morning, plus a 2.6.18-8.1.8 kernel with NTFS file system support compiled in as a module, and vmware server shows this:
$ vmware -v
/usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libpng12.so.0/libpng12.so.0: no version information available (required by /usr/lib/libcairo.so.2)
VMware Server 1.0.3 build-44356
(Not sure what that note about libpng12 means....)
Here is the server log's tail:
Jul 30 17:57:48: app| SP: Retrieved username: mhr
Jul 30 17:57:54: app| Adding to list of running vms: /F/vmware/Windows XP Professional/Windows XP Professional.vmx
Jul 30 17:57:54: app| Attempting to launch vmx : /F/vmware/Windows XP Professional/Windows XP Professional.vmx
Jul 30 17:57:55: app| New connection on socket server-vmxvmdb from host localhost (ip address: local) , user: mhr
Jul 30 17:57:55: app| Connection from : /F/vmware/Windows XP Professional/Windows XP Professional.vmx
Jul 30 17:57:55: app| Setting up autoDetect info.
Jul 30 17:57:55: app| VMServerdConnect: connecting to /F/vmware/Windows XP Professional/Windows XP Professional.vmx
Jul 30 17:57:55: app| Connected to /F/vmware/Windows XP Professional/Windows XP Professional.vmx
It is now 18:43 and the window is still hung.
Any suggestions or clues? This is the first glitch I've had with vmware server on CentOS 5.
Thanks.
mhr
_______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos