Archive

Posts Tagged ‘Fix’

Hyper-V. CSV Volumes pause states 5120‏: Workaround

April 16, 2016 4 comments

 

Microsoft is aware that after installing KB3126593 (MS16-014) there may be an issue that causes loss of network packets.

This may cause Cluster Shared Volumes (CSV) on the nodes Failover Clusters to going into a paused state with an event ID 5120 in the System event log what indicates “Status c000020c – STATUS_CONNECTION_DISCONNECTED”. 

You will also find that, on the node that owns the CSV volume(s), there will be an event 7031 with the source: “Service Control Manager”, which indicates “The Windows Firewall Service terminated unexpectedly”. 

Troubleshooting Cluster Shared Volume Auto-Pauses – Event 5120. https://blogs.msdn.microsoft.com/clustering/2014/12/08/troubleshooting-cluster-shared-volume-auto-pauses-event-5120/

Microsoft is aware of this problem and are working on a fix. But until it is release here is what you could do to get around this issue:

Option 1: Disable the Firewall LOGGING for all profiles (domain, private, public). (just the logging, not the firewall . You don’t want to be un-protected)

1.  Start the Windows Firewall with Advanced Security management console (wf.msc)

2.  Right-click Windows Firewall with Advanced Security on Local Computer and select Properties

3.  For all profiles (Domain, Private, Public), under Logging, click Customize. Set Log Dropped Packets and Log Successful connections to NO.

Option 2. Uninstall https://support.microsoft.com/en-us/kb/3126593 from the systems.

I will post an update once Microsoft releases the Hotfix.

Advertisements

Removing the ghost Hyper-V vNic adapter when using Converged Networks after in-place upgrade to W2012R2

November 20, 2013 7 comments

Scenario:

You have a Windows 2012 with NIC Team configured, Hyper-V Virtual Switch and vNIC’s and you have done an in-place upgrade to Windows 2012 R2

What will happen:

You will find out that the Hyper-V Virtual Nic Adapter (vNIC) is disconnected (as shown below). As you can see, the Management and Migration vNIC’s are showing as network cable unplugged.
pic1

You can also use wmi to query for the vNIC’s (pictured below):

gwmi   -nnamespace root\virtualization\v2  -Class MSVM_InternalEthernetPort | select elementname

pic3

What should you do to avoid this situation:

Recommendation: Before upgrading from Windows 2012 to Windows 2012 R2, make sure you remove the Hyper-V Virtual Switches and the Network Team (in this order).

What you could do if you did not follow the recommended approach:

Below I describe the step by step that you need to take in order to get the ghost vNIC’s removed.
Note: The following process was certified by Ben Armstrong (aka Virtual PC Guy), Microsoft PM for Hyper-V and it is supported by Microsoft, as a valid similar approach that fix the Physical Networking by using the registry, as per MS KB : http://support.microsoft.com/kb/146333 ( don’t follow the method described in that article, to fix the VNIC issue.)

Steps:

1. in the Network Connections, take note of the vNIC name (e.g. Hyper-V Virtual Ethernet Adapter #2)  in the properties: Select the vNIC (e.g. Management), right click properties ( as per below):

pic2

2. Open the registry: Windows Key + R, then type regedit

3. Locate the following Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\ROOT\VMS_MP

4. Go though the folders until you find the folder that contains the FriendlyName with the SAME name of the ghost vNIC

pic4

5.  Select the Folder, right click and select Permissions, click on Advanced and replace the owner of the folder to Local Server Administrators (currently: System), by clicking on Change, typing Administrators (make sure the From this location show your server name) and click OK.

pic5

6. Disable the inheritance by clicking on Disable inheritance and then clicking on Convert inherited permissions into explicit permissions on this object and then add the local server Administrators group with Full Control

pic6

7. Select all the objects INSIDE the folder, right click and click on Delete

pic7

8. Repeat the steps 5-7 for all ghosts vNIC’s and close the registry

9. Open the Device Manager: Windows Key, type Device Manager and click on Scan for Hardware Changes. ( Select the Server Name, Click on Action and then Scan for Hardware Changes)

pic8

…and you are done! All fixed. Go back to Network Connections and refresh and you will noticed that the ghosts vNIC’s are all gone.

Thanks to Ben Armstrong, who actually found this solution and Taylor Brown.

Hyper-V W2008R2. Full update list. From Oct/2009 and up to June/2012

July 25, 2012 Leave a comment

The latest Hyper-V service packs, updates, and hotfixes for Windows Server 2008 R2 are listed here in chronological order.

http://social.technet.microsoft.com/wiki/contents/articles/1349.hyper-v-update-list-for-windows-server-2008-r2-en-us.aspx

Hyper-V. New Linux Integration Services 3.2

December 3, 2011 6 comments

This release includes the following features:

  • Synthetic Mouse Support: Finnaly ! The virtualized mouse device is no longer bound to the VMConnect window, and can now be used with a RDP session, which means that you no longer need to install a separate package to get integrated mouse support, and will not have to worry about the mouse being captured by the virtual machine.
  • Merged Device Drivers: We now present a single device driver for both IDE and SCSI devices (hv_storvsc).
  • Windows 8 Fix: The synthetic network device (hv_netvsc) can now be used with a Windows 8 host, eliminating the hang on boot that was previously seen.
  •  SCVMM Fix: This release fixes the issue as described inKB2586286.
  •  Improved Setup Experience: Users now only need to run install.sh (as root) to automatically detect the correct architecture and install the appropriate drivers

In addition, :

  • The driver applied to guest virtual machines running Red Hat Enterprise Linux Server 6.1 (architecture x 86 and x 64) and CentOS 6.0 (architecture x 86 and x 64). For earlier version should be used components integration version 2.1
  • In fact, it’s modified drivers in the Linux kernel 3.2, but can work with the Linux kernel 2.6.32, shipped with Red Hat and CentOS

BIG NOTE: Microsoft is working with the sponsors of the Linux distros and in the future a list of officially supported distributions will be expanded.

You can download them directly from here: http://www.microsoft.com/download/en/details.aspx?id=28188