I have a Win2012 hyper-v failover cluster running in our Dev lab. It is very simple with 2 nodes and shared SMB storage on the server running the failover cluster role. a few nights ago all of the VMs on one of the nodes failed to start giving the error message: failed to lock virtual machines configuration file (unspecified error 0X800040005).
I checked the path configured on the Hyper-V node (c:\program data\Microsoft\hyper-v\virtual machines) that points to the configurations files and VHDX files on the SMB share and it was correct. I also tested that the node could access the path listed in the symlink via explorer and it could. I disabled AV to no avail and also there is no back up software running in this node. I also tried re-adding the symlink using the mklink command but this still did not get the VM to start. It reports a lock on the config file however when I go on to the server with the storage I do not see any open handles on the files.
There were no changes as far as I am aware and the only way I have found to get each server back on-line is to delete the config file which causes the VM to dissapear from the inventory and recreate using the existing VHDX file, albeit that I have to re-add the additional configurations again and that the new config file is stored on the local disk rather than the shared storage. There were no permissions changes as this would have caused issues on the second node which is working fine.
I would really like to find out what caused this and find out how I can get the rest f the VMs back on-line without having to rebuild them.