Is it possible to post us the vmware.log for this VM that lives with the VM so that we can take a look?
Your vm is simply gone unresponsive during snapshot and quite possible during some heavy task like vmotion etc.. You can fix it from yourself but your snapshot operation will be stopped.
Follow below blog
i did all these....
but now i have different problem...My vm looks invalid on inventory.
i wonder if i create a new virtual machien and use existing vmdk..does it works ? but also i have snapshot files in storage.
completly i confused.
and i removed it from inventroy and add again nothing chanced..
From the Direct Console User Interface (DCUI):
- Connect to the console of your ESXi host.
- Press F2to customize the system.
- Log in as root.
- Use the Up/Downarrows to navigate to Restart Management Agents.Note: In ESXi 4.1 and ESXi 5.0, 5.1 and 5.5, this option is available under Troubleshooting Options.
- Press Enter.
- Press F11to restart the services.
- When the service has been restarted, press Enter.
- Press Escto log out of the system.
From the Local Console or SSH:
- Log in to SSH or Local console as root.2.
- Run these commands:/etc/init.d/hostd restart
After restarting the Host will be lost connection and become responsive again and will connect to the vcenter.
Step 2) After reconnecting the host in vCenter, the VM is fully operational (the vMotion task failed at the moment I restarted the management agents) again.
okay. did you tried readding the vm in to your inventory .
remove it from the inventory and readd the .vmx file in to the vcenter. hope it works.
yeah existing vmdk will readd in to the inventory. but try to remove and register again.
yes i try to add it again inventroy but nothing change.
Please follow these kb and see if your issue can fix.
it didnt work and as i see there are 3 version of different snapshot on vm and it cant commit.
So the problem was because of snapshots i think..but i dont understand why that vm has different version of snapshots ? i had backup it with veeam backup why veeam didn't commit the snapshots ?
this can happen when a backup job can be not finished, the snapshots stay till the next successful backup...
Under certain circumstances there might be snapshots left over after backup activity; the general explanation can be found on Veeam forums.
However, as far as I know, even if VB&R has left a snapshot after backup/replication task, it should delete it during next job cycle. Starting from version 8, VB&R has functionality called snapshot hunter that should find and take care about orphaned snapshots in automatic fashion.
Again i have same problem with exchange machine.
Veeam backup failed. I have shapshot and i cant delete them , the machine dosent respond (no console, no ping).
when i try to delete snapshot i get this error;
"A general system error occurred: vim.fault.GenericVmConfigFault "...
and i cant restart to VM..
Right Click on the VM from vcenter.
Select Guest -> End VMWare Tools.
Then Restart the VM.
This fixed the issue for me.