Installation of Symantec Backup Exec 2012 is fully supported on Windows 2008R2 Hyper-V nodes as described in the Software Compatibility List. However after rebooting the node, Hyper-V throws the following errors. Important to note is that the cluster itself is online without any warnings or errors as described in this post. The errors are visible after live migrating a virtual machine to the impacted target host or when you attempt to start a virtual machine on the impacted node.
‘VM Name’ failed to start.
Microsoft Emulated IDE Controller (Instance ID {########-####-####-####-############}): Failed to Power on with Error: ‘A device attached to the system is not functioning.’
Failed to open attachment ‘Drive Letter:\path\Virtual Hard drivers\VMNAME_########-####-####-####-############.vhd’. Error: ‘A device attached to the system is not functioning’
Failed to open attachment ‘Drive Letter:\path\Virtual Hard drivers\VMNAME_########-####-####-####-############.vhd’. Error: ‘A device attached to the system is not functioning’
and
‘VM Name’’ Microsoft Emulated IDE Controller (Instance ID {########-####-####-####-############}): Failed to Power on with Error: ‘A device attached to the system is not functioning.’ (0x8007001F) (Virtual Machine ID: ########-####-####-####-############)
Some research resulted in the following conclusion:
- In the Kernel Mode the following components exist:
- Fsdepends.sys: File System Dependency Manager Mini Filter Driver
- Vhdmp.sys: VHD Miniport Driver
- vdrvroot.sys: Virtual Drive Root Enumerator
- The VirtDisk.dll uses the above mentioned components for starting the VDS VHD API’s.
- And those are used for the Virtual Disk Service which is configured with a manual startup type…