Hi Gregory, It seems that my issue has resolved itself after I have done the following.
1. Disconnected my esx server from virtualcenter
2. Closed VI Client
3. Restarted VirtualCenter (windows service)
4. Open VI Client and re-added my host.
It's been almost 1 week without issues. It think it just too easy to be a permanent work arround so I won't hold my breath.
Could it be an issue if we manage hosts directly via VI client and via VirtualCenter ?
I just encountered this issue this morning for the first, and unfortunately our Sys Admin who normally takes care of these problems is away.
The problem in a nutshell for us was the VMHost kept reporting as "Not Responding". As such out of the 10 or so VM clients hosted by this host, only a few were in a state were we could not power them on,off or restart. The error message kept reading "The attempted operation cannot be performed in the current state (Power Off)". But these VM clients were indicated as "Powered On" in Virtual Infrastructure Client. What I did to resolve the issue is as follows:
Shutdown all VM's on the Host that could be contacted
Restart VM Host which resolved the "Not Responding" issue of the Host
Once VM host was restarted, I started up each one of the VM Clients.
Unfortunately there were still some VM's that had the issue of "The Attempted operation cannot be performed in the current state (Powered Off)". But after taking a snapshot of these VM's the issue was resolved and I was able to start them up.
I had the exact same error once but it turned out to be because the virtual machine's CD drive was still "connected" to an .iso on the datastore that wasn't there anymore.
I ran into this same issue tonight... Turned out that by logging in to the ESX host using VI Client I was able to see much more information. When I clicked on the troubled VM there was a big yellow dialog box that said "There is no more space for the redo log on ... So I was able to clean up some space on the datastore, clicked Retry on the error, and the VM came right back online...
Had the same issue. Our connection to the SAN dropped and after it got restored there was one VM with this error. Couldn't do anything (i thought) with it, no reset, remove from inventory was grayed out etc...
Turned out I had to "answer question" a couple of times, just choose continue/disconnect (cdrom). After that it was accessible again.
I've the same problem, It seems that some host have incorrect information of vm state. In my case it occurs after a failed vmotion.
I try to reset management service of two hosts (source and destination off vmotion) with the command: service mgmt-vmware restart, then I restart Virtual center service on virtual center server and then it shows vmstate correct and I can start VM
Thanks for you post
A VM had the said problem after removing a snapshot.
We resolve this issue with the command "service mgmt-vmware restart" on the host esx (4.0.u2)
Thanks for the tip.
2) esxcli vm process list (Search list vm)
"Compatibility ESXi 4 and later"
After weekly problems...success