Vasilax50
asked on
Remove snapshot stuck for more than 20 hours - ESXi 5.0
Yesterday tried to remove VM snapshots on ESXi 5.0, and the process is stuck for more than 20 hours.
Running vim-cmd vimsvc/task_list of this host it shows:
(ManagedObjectReference) [
'vim.Task:haTask-44-vim.Vi rtualMachi ne.removeA llSnapshot s-12580485 '
The VM is unresponsive, no shutdown, does not even allow to rename the VM, any task gets an error "another task is already in progress", no problems manipulating with any other VMs.
I have no problem to lose this particular VM, but the host is in production cluster.
Thanks
Running vim-cmd vimsvc/task_list of this host it shows:
(ManagedObjectReference) [
'vim.Task:haTask-44-vim.Vi
The VM is unresponsive, no shutdown, does not even allow to rename the VM, any task gets an error "another task is already in progress", no problems manipulating with any other VMs.
I have no problem to lose this particular VM, but the host is in production cluster.
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Looks like your, hanccocka, solution works :)
Restarted Network Management Agents on host and VCenter Service and the process gone
But now in inventory I have inaccessible virtual machine named "Unknown 37" , if I try to remove from inventory, it created another, "Unknown 38" VM
Also, I cannot delete the the old VM folder from the Datastore
Thank you
Restarted Network Management Agents on host and VCenter Service and the process gone
But now in inventory I have inaccessible virtual machine named "Unknown 37" , if I try to remove from inventory, it created another, "Unknown 38" VM
Also, I cannot delete the the old VM folder from the Datastore
Thank you
was this the VM that had the snapshot issue.
its looking likely that there is a lock on the VM, which is no surprise
there are two ways to get rid of locks, the short way restart the host, the long way, login via console or ssh, find the lock, using lsof, kill the process.
its looking likely that there is a lock on the VM, which is no surprise
there are two ways to get rid of locks, the short way restart the host, the long way, login via console or ssh, find the lock, using lsof, kill the process.
ASKER
Thank you !
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1014165