6

Setup: Virtual Host, running server 2012, hosting around 10 production VMs

Problem: Last night, 2 VMs stopped with no warning, event log notification, or any information. The rest of the VMs on this host were running fine. We caught this error, and since it was before business hours, decided to restart the vhost. Once the vhost came back up, all the VMs had the exact same issue that the other two had previous. Except for one. There is 1 vm out of 10 that is still running fine. The error message in its entirety is here:

[Window Title]
Hyper-V Manager

[Main Instruction]
An error occurred while attempting to start the selected virtual machine(s).

[Content]
'VMNAME' could not initialize.

An attempt to read or update virtual machine configuration failed.

[Expanded Information]
'VMNAME' could not initialize. (Virtual machine ID IDREMOVED)

'VMNAME' could not read or update virtual machine configuration: Unspecified error (0x80004005). (Virtual machine ID IDREMOVED)

[^] Hide details  [Close]

What we have checked so far:

  • Windows updates - none installed last night
  • event logs = clean of errors
  • no system wide changes took place
  • The XML file (config file) and vhd are still in the same locations

What we have done in the meantime: Thankfully we have a disaster plan in place which allowed us to failover to our replication server which is functioning perfectly. All machines are currently working just fine there, albeit a little slow. We are running short on ideas other than to remove all the broken vms from the vhost (config files and vhds) and have the replication server replicate over back to the vhost (essentially creating a new vhd and config file on the vhost, then we can failover to the main machine again.

Anyone have any thoughts?

closed as too broad by Greg Askew, Ward - Reinstate Monica, Tom O'Connor, mdpc, ThoriumBR Sep 14 '17 at 20:04

Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • After this length of time, I am assuming you went ahead with the replication plan you had. In my experience, when a VM goes this direction, I usually remove the VM from Failover Cluster Manager and recreate the VM with the old VHD. This requires rebuilding the VM configuration but depending on the complexity of the envoronment/vm its doable. – Byron C. Apr 23 '14 at 0:10
0

Check my answer here:

Cannot create Hyper-V Virtual Machine - General Access Denied 0x80070005

what you might find useful there:

  1. a suggestion to use Process Monitor to find out exactly what is going wrong in the process

  2. if your problem is broken file permissions on your config files, and it seems like a possibility, you can use or adapt my batch file to restore permissions (be careful with that, though!).