Did change physical SSDs in RAID VD in 2012 R2 Datacentre running Hyper-V
Image up/down, bcd never likes such changes, so quick bcdboot to re-create it, server up & running fine, Failover Cluster Manager suddenly can not live migrate VM from other cluster host.
Throws errors about CPU being not compatible (strange, did not change CPU, did not touch BIOS)
Poke around, cold move VM to the other host, try to start & this time error that Resources can not be brought online
What resource? Cluster storage is accessible, networks as well. Forget FCM, lets use Hyper-V Manager.
Oh well, that one gives at least correct error -"hypervisor is not running"
Of course, bcdboot does not have any logic to check that hypervisor was installed on this host, so did not auto start it in bcd
bcdedit /set hypervisorlaunchtype Auto
reboot and all is back to normal.
But I am losing more & more faith in MS Hyper-V related tools. How come FCM could not produce correct meaningful error message that would relate to the actual issue?
Seb