For reasons which escape me, my VMWare Server, which was working perfectly a week ago when I shut down my machine for vacation, no loner comes up with the formerly working Windows XP system - it just stays in the small window where it normally boots and does nothing.
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
Any chance your filesystem is full? That same thing happened to me awhile back on a different OS and that was the problem.
Mark Hull-Richter wrote:
For reasons which escape me, my VMWare Server, which was working perfectly a week ago when I shut down my machine for vacation, no loner comes up with the formerly working Windows XP system - it just stays in the small window where it normally boots and does nothing.
On 7/31/07, Adam Gibson agibson@ptm.com wrote:
Any chance your filesystem is full? That same thing happened to me awhile back on a different OS and that was the problem.
If you mean the vmware virtual disk, I don't think so - last I looked it had 8+Gb free (20Gb total). As for the rest of the system:
$ df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda2 79356528 6261352 68999004 9% / /dev/sda1 101086 39703 56164 42% /boot tmpfs 964420 0 964420 0% /dev/shm /dev/sda5 200335792 12113396 177881760 7% /home /dev/hda1 31412256 180288 30912840 1% /C /dev/hdb1 62658052 19804468 42217012 32% /D /dev/sdb1 102568532 48403676 53122804 48% /E /dev/hda2 126155260 89093152 35780444 72% /F /dev/hdb3 55509784 31742448 23203376 58% /G /dev/sdb2 205093168 164750464 38259076 82% /H
There's gobs of space (yeah, I know the mount points are hokey - they correspond to my old Windows drives, and are usually samba-mounted on my vmware guest, when it's running...).
Thanks.
mhr
On Mon, 2007-07-30 at 18:45 -0700, Mark Hull-Richter wrote:
For reasons which escape me, my VMWare Server, which was working perfectly a week ago when I shut down my machine for vacation, no loner comes up with the formerly working Windows XP system - it just stays in the small window where it normally boots and does nothing.
It turns out that this was the same problem I was seeing on CentOS 4.4 right before I upgraded, only rebooting does not help. I have booted to a plain vanilla 2.6.18-8.1.8 kernel and even went back to the 2.6.18-8.1.6 kernel where this was working before, so it clearly is NOT a CentOS problem (never thought it was!).
The logs are rather unrevealing as to what happens - the guest just starts to boot and hangs with a black screen (and the play button blinking). It has been suggested (elsewhere and before) that I create a new VMWare guest OS, attach the current non-working drive to it and try to clean it up from there. This might work and I will try it, but I was wondering if there was anyone else out there who might have an idea what this could be.
Thanks.
mhr
-
Adam Gibson -
Mark Hull-Richter