Unexpected resource lock on VM

Unexpected resource lock for the virtual machine where they cannot be handled by the Hyper-v manager and recovered by Host restart .

Resource lock on VM . 

10/12/2014         12:07:51 PM       Error      GEPHVH2Q0925J1W.DXB.JI.NET                1130       Microsoft-Windows-FailoverClustering            Network Manager           NT AUTHORITY\SYSTEM                Cluster network 'Cluster Network 1' is down. None of the available nodes can communicate using this network. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

10/12/2014         12:38:12 PM       Error      GEPHVH2Q0925J1W.DXB.JI.NET                1130       Microsoft-Windows-FailoverClustering            Network Manager           NT AUTHORITY\SYSTEM                Cluster network 'Cluster Network 1' is down. None of the available nodes can communicate using this network. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

10/12/2014         12:46:00 PM       Error      GEPHVH2Q0925J1W.DXB.JI.NET                1130       Microsoft-Windows-FailoverClustering            Network Manager           NT AUTHORITY\SYSTEM                Cluster network 'Cluster Network 1' is down. None of the available nodes can communicate using this network. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

10/12/2014         1:23:18 PM          Error      GEPHVH2Q0925J1W.DXB.JI.NET                1130       Microsoft-Windows-FailoverClustering            Network Manager           NT AUTHORITY\SYSTEM                Cluster network 'Cluster Network 1' is down. None of the available nodes can communicate using this network. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

10/12/2014         2:52:19 PM          Error      GEPHVH2Q0925J1W.DXB.JI.NET                1130       Microsoft-Windows-FailoverClustering            Network Manager           NT AUTHORITY\SYSTEM                Cluster network 'Cluster Network 2' is down. None of the available nodes can communicate using this network. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

10/22/2014         1:08:31 PM          Error      GEPHVH2Q0925J1W.DXB.JI.NET                35           Microsoft-Windows-Kernel-Processor-Power             N/A        NT AUTHORITY\SYSTEM                Performance power management features on Hyper-V logical processor 0 are disabled due to a firmware problem. Check with the computer manufacturer for updated firmware.

10/22/2014         1:08:31 PM          Information        GEPHVH2Q0925J1W.DXB.JI.NET                55           Microsoft-Windows-Kernel-Processor-Power              N/A        NT AUTHORITY\SYSTEM                Hyper-V logical processor 0 exposes the following power management capabilities: Idle state type: ACPI Idle (C) States (1 state(s)) Performance state type: ACPI Performance (P) / Throttle (T) States Nominal Frequency (MHz): 2400 Maximum performance percentage: 100 Minimum performance percentage: 100 Minimum throttle percentage: 100

Issue escalated at Microsoft side . After investigation they presented the below steps :

Next action plan as follows:

1-      Take a complete  backup for al nodes and shared storage including VMs.

Note if the VM backup fails please make sure you have back even on hardware level.

2-      Contact your hardware and storage vendor direct support to apply the following:

a.      Validate your have latest  firmware released for SAN storage , SAN\Network switches and FC\NIC controllers for Windows Server 2012 R2 compatibility.

b.       Verify you have the latest drivers released for Windows Server 2012 R2:

Followed the point where the latest drivers needed installation and focused on NIC driver (according to the error messages)

  The Emulex driver caused this. They corrected the situation in the latest driver version . 

In the version installed this was one of the resolved points :

1.Windows NIC driver transmission no longer consumes all of the available cycles on one

CPU core, resulting in the system freezing or pausing.

If another similar issue occurs please first check emulex website for indications on upgrading to the latest driver version.