It looks like VMware Server 2.0 doesn't recognize the Windows 7 guestOS values. Try changing it to "winvista-64" and see if this allows the VM to boot. If this works, I can add an exception in the code to use the winvista guestOS values for Windows 7 under VMware Server 2.0.


On 2/9/2011 3:08 AM, James Patrick Sigmon wrote:
Hey Andy,

Sorry I for not responding earlier; I had to put this issue on the back burner 
for a bit for other things.

Attached is the output for the vcld.log.  Also, the error is currently captured 
in the attached screenshot.  The vmguests for this image still fail to start.

Here is the basic output from VMware:

[root@server15 Virtual Machines]# vmware-vim-cmd vmsvc/getallvms
Vmid                  Name                                                File  
                                  Guest OS       Version   Annotation
208    vmwarewin7-base-v1                    [local] 
vmwarewin7-base-v1/vmwarewin7-base-v1.vmx                 otherGuest        
384    vmguest-3:vmwarewin7-base-v1          [local] 
vmguest-3_8-v0/vmguest-3_8-v0.vmx                         otherGuest        

The guestOS value is "windows7-64."  I've also, attached copies of the vmx 
files for the base image and the vmguest.



On Jan 28, 2011, at 2:23 PM, Andy Kurth wrote:

What is the guestOS value in the .vmx file?  Also, it would be helpful to 
include the vcld.log output.


On 1/26/2011 3:14 PM, James Patrick Sigmon wrote:
Hey guys,

With the Internet issue resolved, I was able to return to my Windows 7 image 
and complete the Cygwin install.  I proceeded to complete all the necessary 
steps thereafter.

When I make a reservation for the image, it gets to where it boots the image then windows 
fails to load - "Windows failed to start.  A recent hardware or software change 
might be the cause" (see attached screenshot).

I checked the vmware server manager and the only difference I can see is that 
the vmguest is being assigned the Guest OS: Other (32-bit).  As my image is a 
64-bit, I believe this to be a hint at the problem.  I double checked the 
database and the architecture is set to x86_64.  So I'm at a lose as to what's 
going on here.

Any ideas?


Patrick Sigmon

Reply via email to