Virtual machine '%1' could not be started because the hypervisor is not running (Virtual machine ID %2).%r The following ...

Virtual machine '%1' could not be started because the hypervisor is not running (Virtual machine ID %2).%r
The following actions may help you resolve the problem:%r
1) Verify that the processor of the physical computer has a supported version of hardware-assisted virtualization.%r
2) Verify that hardware-assisted virtualization and hardware-assisted data execution protection are enabled in the BIOS of the physical computer.  (If you edit the BIOS to enable either setting, you must turn off the power to the physical computer and then turn it back on.  Resetting the physical computer is not sufficient.)%r
3) If you have made changes to the Boot Configuration Data store, review these changes to ensure that the hypervisor is configured to launch automatically.%r

Virtual hard disks associated with a virtual machine that has replication enabled and is currently involved in initial replication, ... Virtual machine '%1' cannot be started on this server. The virtual machine NUMA topology requirements cannot be satisfied ... Virtual machine '%1' cannot be started on this server. The virtual machine NUMA topology requirements cannot be satisfied ... Virtual machine '%1' cannot be started on this server. The virtual machine NUMA topology requirements cannot be satisfied ... Virtual machine '%1' could not be started because the hypervisor is not running (Virtual machine ID %2).%r The following ... Virtual machine '%1' is configured to allow unfiltered SCSI commands for physical disks attached to SCSI controllers. (Virtual ... Virtual Machine Management service is shutting down while some virtual machines begin running. All running virtual machines ... Virtual machine migration for '%1' failed because checkpoint data root cannot be changed for a clustered virtual machine. ... Virtual machine migration for '%1' failed because configuration data root cannot be changed for a clustered virtual machine. ...