VMware Cloud Community
mcraig88
Contributor
Contributor
Jump to solution

I have a VM that is in a ‘stuck’ state. That is I cannot power it off, reset it, or log into it.

Attached is the log, I grep'd the contents of vmware.log for info regarding this VM.

VM: swfdev01

Command:

# vmware-cmd /vmfs/volumes/Dev_VM3/swfdev01/swfdev01.vmx stop hard

Error:

# VMControl error -999: Unknown error: SoapError: ServerFaultCode(0) : (Operation failed since another task is in progress.)

Tags (2)
Reply
0 Kudos
1 Solution

Accepted Solutions
SuryaVMware
Expert
Expert
Jump to solution

run vm-support -x will list the world ID of all the VMs. Pick up the world ID of the VM in hung state.

Run vm-support -X <WID> answer 'y' to the quesions that follow, it will take a while to finish the dump logs and will kill the VM eventually.

You will be able to power-on the VM.

-Surya

View solution in original post

Reply
0 Kudos
10 Replies
Troy_Clavell
Immortal
Immortal
Jump to solution

try to kill the VM and if that doesn't work, restart hostd

“ps -ef | grep

service mgmt-vmware restart

aguacero
Hot Shot
Hot Shot
Jump to solution

SSH to the ESX host where the VM lives and run the following commands:

  1. service vmware-vpxa stop

  2. service mgmt-vmware restart

  3. service vmware-vpxa start

Give that a try! It's a known bug in 3.0.x Supposedly fixed in 3.5

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!
SuryaVMware
Expert
Expert
Jump to solution

run vm-support -x will list the world ID of all the VMs. Pick up the world ID of the VM in hung state.

Run vm-support -X <WID> answer 'y' to the quesions that follow, it will take a while to finish the dump logs and will kill the VM eventually.

You will be able to power-on the VM.

-Surya

Reply
0 Kudos
mcraig88
Contributor
Contributor
Jump to solution

Nope, this didn't work. Thanks though.

Reply
0 Kudos
mcraig88
Contributor
Contributor
Jump to solution

This appeared to work at first, but I then tried to power off the VM,

and it timed out and did not power off.

Thanks though.

Reply
0 Kudos
Troy_Clavell
Immortal
Immortal
Jump to solution

see this thread, there are a lot of good suggestions, maybe one will work for you

http://communities.vmware.com/thread/87797

Reply
0 Kudos
mcraig88
Contributor
Contributor
Jump to solution

Thanks SuryaVMWare also made a suggestion that I am currently trying:

http://communities.vmware.com/message/1187696#1187696

Reply
0 Kudos
RParker
Immortal
Immortal
Jump to solution

Nope, this didn't work. Thanks though.

I know this isn't real scientific, but can you vmotion the other VM's and just reboot the host?

ESX is software, and sometimes software is designed for one thing but at times it does something completely out of control (like not let you reboot / power off a VM). This doesn't happen very often, but ESX does hang VM's.

A reboot / reset of the host may be your only hope.

Reply
0 Kudos
mcraig88
Contributor
Contributor
Jump to solution

Unfortunately, the powers that be decided we didn't need VMotion. So

that is not an option.

This worked though.

http://communities.vmware.com/message/1187696#1187696

Thanks for your ideas.

Reply
0 Kudos
arthurdent78
Contributor
Contributor
Jump to solution

vmware-support did the trick for me

Reply
0 Kudos