"Powering On..." Forever

[Randy_Evans]

After enabling guest customization and change SID, and powering on a Windows Server 2003 64-bit virtual machine, the virtual machine has been stuck in the "Powering On..." state for over 30 minutes. In vCenter, the virtual machine is powered off.

How can I troubleshoot this problem?

Thanks.

[Randy_Evans]

Restarted the cell (we have only one cell right now) using the command below.

service vmware-vcd restart

The same virtual machine is still in the same "Powering On..." state. In vCenter, the virtual machine is still powered off. It's been in that "Powering On..." state for three hours now, so it's probably safe to say it's stuck there until we do something about it.

What should we do to get this virtual machine back in service?

How can we prevenet this from happening again?

Thanks.

[sjoglekar]

Can you try this -

1. Power on the VM in vCenter

2. Power it off in vCenter

3. from VCD UI, do a 'reconnect to vCenter'.

Do you have a ISO attached to the VM? If you do, can you detach the ISO and try again?

Can you please upload the logs as well?

Thanks,

Sangeeta

[Randy_Evans]

Tried 1, 2, and 3, but no change.

Will post logs.

[Randy_Evans]

Restarted the cell (we have only one cell right now) using the command below.

service vmware-vcd restart

The  same virtual machine initially appears in the same "Powering On..." state, but within a few minutes the status changes to "Partially Powered Off",  "Cannot start", with the Activiry Task Detail Below.

Operation: Running Virtual Machine SDQMS(548934193)

Job ID: 511646749

Type: com.vmware.vcloud.entity.vm

Status: Error

Organization: ISTC-SD

Owner: evansr

Start time: Tue Mar 8 2011 01:11:12 PM

Stop time: Wed Mar 9 2011 09:11:02 AM

Details: Task VAPP_DEPLOY terminated abruptly and cannot be restarted.

[sjoglekar]

It will be great if you could open a support request for this one. It seems like it needs complete log analysis.

-Sangeeta

[Randy_Evans]

With the problem virtual machine powered off, we copied it to a catalog, and deplyed it as a new vApp. The new copy of the virtual machine in the new vApp is working perfectly.

The old virtual machine was originally deployed before we had all the guest customization files installed. We initially deployed this virtual machine without guest customization and have now enabled guest customization. It is possible that these changes have led to the problem with this virtual machine.

With this work-around we have been able to resolve this issue for the end-user. Time permitting, we will open a technical support request so we can find the root cause.

Thanks.