KB2846340 – Duplicate Friendly Names Of NICs Displayed In Windows

This KB applies to Windows Vista and Windows Server 2008 up to Windows 8 and Windows Server 2012. There’s no mention of Hyper-V, but considering that hosts have lots of NICs, it seemed relevant to me. The scenario is when duplicate friendly names of network adapters are displayed in Windows.

Symptoms

Consider the following scenario:

  • You have one or more network adapters installed on a computer that is running one of the following operating systems:
    • Windows Vista
    • Windows Server 2008
    • Windows 7
    • Windows Server 2008 R2
    • Windows 8
    • Windows Server 2012
  • The display names of the network adapters are changed. For example, the device driver is updated.
  • You add new network adapters to the computer. The new network adapters are of the same make and model as the original network adapters.

In this scenario, duplicate friendly names of the original network adapters are displayed in Device Manager.
For example, you have two network adapters installed on a computer. Before you update the driver, Device Manager shows the following:

  • <Network adapter name>
  • <Network adapter name> #2

After the driver is updated, the names of the network adapters are changed to the following in Device Manager:

  • <Network adapter new name>
  • <Network adapter new name> #2

After you add new network adapters that are of the same make and model, Device Manager shows the following:

  • <Network adapter new name>
  • <Network adapter new name> #2
  • <Network adapter new name> #3
  • <Network adapter new name> #4
  • <Network adapter new name> #5
  • <Network adapter new name> #6
  • <Network adapter new name>
  • <Network adapter new name> #2

In this scenario, Device Manager displays duplicate friendly names of the original network adapters.

A hotfix is available to resolve this issue.

My Most Popular Articles In 2013

I like to have a look at what people are reading on my blog from time to time.  It gives me an idea of what is working, and sometimes, what is not – for example, I still get lots of hits on out-dated articles.  Here are the 5 most viewed articles of the last year, from 5 to 1.

5) Windows Server 2012 Hyper-V Replica … In Detail

An oldie kicks off the charts … this trend continues throughout the top 5.  At least this one is a good subject that is based on WS2012 and is still somewhat relevant to WS2012 R2.  Replica is one, if not the, most popular features in WS2012 (and later) Hyper-V.

4) Rough Guide To Setting Up A Hyper-V Cluster

I wrote this article in 2010 for Windows Server 2008 R2 and it’s still one of my top draws.  I really doubt you folks still are deploying W2008 R2 Hyper-V; I really hope you folks are not still deploying W2008R2 Hyper-V!!!!  Join us in this decade with a much better product version.

Please note that the networking has change significantly (see converged networks/fabrics).  The quorum stuff has changed a bit too (much simpler).

3) Windows Server 2012 Licensing In Detail

Licensing!!! Gah!

2) Comparison of Windows Server 2012 Hyper-V Versus vSphere 5.1

There’s nothing like kicking a hornets nest to generate some web hits Smile  We saw VMware’s market share slide in 2013 (IDC) while Hyper-V continued the march forward.  More and more people want to see how these products compare.

And at number one we have … drumroll please …

1) Windows Server 2012 Virtualisation Licensing Scenarios

Wow! I still cannot believe that people don’t understand how easy the licensing of Windows Server on VMware, Xen, Hyper-V, etc, actually is.  Everyone wants to overthink this subject.  It’s really simple: It’s 2 or unlimited created Window Server VMs per assigned license to a host people!!!  This page accounted for 2.8% of all views in the last 12 months.

Sadly, not a single post from the last year makes it into the top 10.  I guess that folks aren’t reading about WS2012 R2.  Does this indicate that there is upgrade fatigue?

Linux Integration Services Version 3.5 For Hyper-V Is Released

Microsoft has released version 3.5 of the Hyper-V integration components for Linux.  This download is intended for versions of Linux that do not have the Linux Integration Services (LIS) for Hyper-V already installed in the kernel.

Version 3.5 of the LIS supports:

  • Red Hat Enterprise Linux (RHEL) 5.5-5.8, 6.0-6.3 x86 and x64
  • CentOS 5.5-5.8, 6.0-6.3 x86 and x64

Hyper-V from 2008 R2 onwards is supported, including Windows 8 and 8.1.

The below matrix describes which Hyper-V features are supported in which version of the LIS and distro/version of Linux:

image image

Notes

  1. Static IP injection might not work if Network Manager has been configured for a given HyperV-specific network adapter on the virtual machine. To ensure smooth functioning of static IP injection, ensure that either Network Manager is turned off completely, or has been turned off for a specific network adapter through its Ifcfg-ethX file.
  2. When you use Virtual Fibre Channel devices, ensure that logical unit number 0 (LUN 0) has been populated. If LUN 0 has not been populated, a Linux virtual machine might not be able to mount Virtual Fibre Channel devices natively.
  3. If there are open file handles during a live virtual machine backup operation, the backed-up virtual hard disks (VHDs) might have to undergo a file system consistency check (fsck) when restored.
  4. Live backup operations can fail silently if the virtual machine has an attached iSCSI device or a physical disk that is directly attached to a virtual machine (“pass-through disk”).
  5. LIS 3.5 only provides Dynamic Memory ballooning support—it does not provide hot-add support. In such a scenario, the Dynamic Memory feature can be used by setting the Startup memory parameter to a value which is equal to the Maximum memory parameter. This results in all the requisite memory being allocated to the virtual machine at boot time—and then later, depending upon the memory requirements of the host, Hyper-V can freely reclaim any memory from the guest. Also, ensure that Startup Memory and Minimum Memory are not configured below distribution recommended values.

The following features are not available in this version of LIS:

  • Dynamic Memory hot-add support
  • TRIM support
  • TCP offload
  • vRSS

Corrupted Memory Dump When You Obtain Full Memory Dump From A VM On WS2012 Or W2008R2 Cluster

Microsoft have released a KB article for when you get a corrupted memory dump file when you try to obtain a full memory dump file from a virtual machine that is running in a cluster environment.

Symptoms

You have a virtual machine that is running in a cluster environment in Windows Server 2012 or Windows Server 2008 R2. When you try to obtain a full memory dump file from the virtual machine, a corrupted memory dump file is generated. While the memory dump file is loading, you may receive the following message:

**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
GetContextState failed, 0xD0000147
Unable to get program counter
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147

Additionally, you may notice that writing a full memory dump file does not finish and that the virtual machine is restarted on another node in the cluster.

Cause

This issue occurs because the Enable heartbeat monitoring for the virtual machine option is selected for the virtual machine. This option resets the clustered virtual machine after one minute (the default value), and the clustered virtual machine requires longer that one minute to finish writing the memory dump.

Note Heartbeats between the virtual machine and Virtual Machine Manager occur every few seconds. It can require up to one minute to detect that the virtual machine is down because the virtual machine resource checks the heartbeat status from Virtual Machine Manager in its isAlive entry-point function. By default, isAlive occurs one time every minute. However, the heartbeats may stop 30 seconds before the one-minute interval. In this case, the cluster can restart the virtual machine on the same server or fail it over to another node.

There are two options for resolving this issue.

Option 1: Change the settings from the GUI
  1. Open Failover Cluster Manager.
  2. Click Roles, and then find the virtual machine resource. 
  3. On the Resources tab, right-click the virtual machine. 
  4. Click Properties, and then click the Settings tab.
  5. In Heartbeat Setting, click to clear the Enable automatic recovery for application health monitoring check box.
  6. Click to clear the Enable heartbeat monitoring for the virtual machine check box, and then click OK.
Option 2: Change the settings by using Windows PowerShell
  1. Start Windows PowerShell.
  2. Check the virtual machine name. To do this, type the following Windows PowerShell command:

    PS C:> Get-ClusterResource

  3. Check whether the Enable heartbeat monitoring for the virtual machine and Enable automatic recovery for application health monitoring options are selected. To do this, type the following Windows PowerShell command:

    PS C:> Get-ClusterResource <VirtualMachineName> | Get-ClusterParameter CheckHeartbeat

  4. When the CheckHeartbeat value is 1, both options are selected. To cancel both options, change this value to 0. To do this, type the following Windows PowerShell command:

    PS C:> Get-ClusterResource <VirtualMachineName> | Set-ClusterParameter CheckHeartbeat 0

    NoteIf you want to cancel only the Enable automatic recovery for application health monitoring option, you should run the following Windows PowerShell command:
    PS C:> (Get-ClusterResource <Object>).EmbeddedFailureAction = 1

5nine Software Releases V2.0 Of VMware-To-Hyper-V V2V Conversion Tool (FREE!)

5nine Software announced the release of the free 5nine V2V Easy Converter v2.0 yesterday.  This will allow you to convert VMware VMs into Hyper-V VMs with support for VHD and VHDX and the following guest OSs:

  • Windows Server 2008
  • Windows 7
  • Windows Server 2003 (x86 and x64)
  • Most of Advanced Server 2000
  • Ubuntu Linux
  • CentOS Linux

Yes: V2V conversions to Hyper-V for Linux guests!

The last three versions of Hyper-V are supported:

  • Windows Server 2008 R2 SP1 Hyper-V
  • Windows Server 2012 Hyper-V
  • Windows Server 2012 R2 Hyper-V

If you have any questions, please contact 5nine Software Information at info(at)5nine(dot)com or via phone +44 (20) 7048-2021 from 7am to 5pm GMT

KB2867302–Clustered File Share Resource Fails With “Status 5. Tolerating …” Cluster Log Error

Microsoft posted a KB article for when you have a situation on W2008, W2008 R2 or WS2012 where a cluster fileshare resource fails on a failover cluster node and the cluster log contains "status 5. Tolerating…".

Symptoms

Consider the following scenario:

  • In Windows Server 2008, 2008 R2 or 2012 you set up a Windows failover cluster with a highly available file server.
  • The cluster nodes are configured with a disjointed namespace in which the computer’s primary DNS suffice does not match the DNS domain of which it is a member.

In this scenario, you may notice that the highly available file server works fine on some of the cluster nodes but consistently fails on others. In examining the cluster log, you see something similar to the following entries with the first entry referring to "status 5. Tolerating…":
00001b6c.000008c8::2013/01/23-04:00:13.797 WARN [RES] File Server <FileServer-(yoel-cluster)(Cluster Disk 6)>: Failed in NetShareGetInfo(yoel-cluster, share2), status 5. Tolerating…
00001b6c.000008c8::2013/01/23-04:00:13.797 ERR   [RES] File Server <FileServer-(yoel-cluster)(Cluster Disk 6)>: Not a single share among 1 configured shares is online
00001b6c.000008c8::2013/01/23-04:00:13.797 ERR   [RES] File Server <FileServer-(yoel-cluster)(Cluster Disk 6)>: File system check failed, number of shares verified: 1, last share status: 5.
00001b6c.000008c8::2013/01/23-04:00:13.797 ERR   [RES] File Server <FileServer-(yoel-cluster)(Cluster Disk 6)>: Fileshares failed health check during online, status 5.

Cause

One or more nodes of the failover cluster may contain mismatched entries in the DNS suffix search list.

Resolution

To resolve the issue, verify all cluster nodes are configured with the same DNS suffix search list and the entries are listed in the same order. The DNS suffix search list can be modified using the following steps:

  1. Open the properties page for the network adapter.
  2. Open the properties page for Internet Protocol Version 4 (TCP/IPv4).
  3. Select the Advanced button under the General tab.
  4. Select the DNS tab.

This is a configuration issue and there is no hotfix.

KB981618 – WS2008 R2 Host Hangs OR Restarts During Live Migration

A hotfix has been released for Windows Server 2008 R2 Hyper-V for when computers that use AMD central processing units hang or restart during the Live Migration process.

This issue is caused by caused by AMD erratum 383. For detailed information, see the “Symptoms,” “Cause,” and “Resolution” sections of this article.

The article explains that:

Symptoms

When you run Windows Server 2008 R2 Hyper-V on a computer that uses AMD Family 10h central processing units (CPUs), the host computer may restart or stop responding unexpectedly. When this issue occurs, you receive no error messages.

This issue may occur when the Live Migration feature is used to move a virtual machine (VM) from one Windows Server 2008 R2 Hyper-V-based node to another node. This problem usually affects the source node that is the original location of the VM and usually does not affect the target node that is the new location where the VM will be moved.

Note This issue may occur in other scenarios and does not occur only in Live Migration scenarios.

Cause

This issue occurs because of erratum 383 in AMD Family 10h processors. This erratum generates a machine check exception. This machine check exception causes the hardware to restart or to stop responding.

A hotfix has been released to fix this issue.

Altaro Launches Hyper-V Backup v4

Congratulations to the really nice folks at Altaro (that’s been my experience and that of some of my customers) on the release of Altaro Hyper-V Backup v4.  Here are some of the features:

image

Altaro, like a few others, are really quick to keep up with Microsoft.  I wouldn’t be surprised if they quickly celebrated the release while installing WS2012 R2 Hyper-V to get working on it … while certain big names in backup still don’t support WS2012.

image

Hyper-V Backup is available as a nice free solution for the very small business and a fairly priced solution for larger businesses.

KB2858695 – Unable To Use kdump or kexec On Linux VMs On Hyper-V

Microsoft has released a knowledge base article to deal with a situation where you are unable to use kdump or kexec for Linux virtual machines on Hyper-V.

Symptoms

Consider the following scenario:

  • You have a computer that is running a Microsoft Windows operating system with the Hyper-V role installed.
  • You install Linux in a Hyper-V virtual machine on the computer.
  • You configure kdump on Linux VM which already has the Linux Integration Services drivers either pre-built or manually installed.

In this scenario, if the Linux virtual machine crashes, the core dump of the Linux kernel is not generated.

Cause

This issue occurs because Hyper-V is unable to host two simultaneous connections from the same synthetic driver running inside a virtual machine.

When kdump is configured on a Linux virtual machine that is using the Linux Integration Services synthetic storage driver (also known as storvsc), the kexec kernel is configured to use the same driver. If the Linux virtual machine crashes, the synthetic storage driver hosted in kexec kernel attempts to open up a connection to the Hyper-V storage provider. However, Hyper-V fails to establish the new connection because of the pre-existing connection to the same storage driver within the crashed Linux virtual machine. Due to this reason, the kexec kernel is unable to dump core for the crashed Linux virtual machine.

Resolution

To resolve this issue, configure the kexec kernel with the standard Linux storage driver. This configuration needs to be done after the kdump functionality is enabled on a Linux virtual machine. The basic idea is to turn off the Linux Integration Services storage driver and then enable the standard Linux storage driver inside the kexec kernel by using the prefer_ms_hyper_v parameter at strategic locations.

There are more instructions on the KB article to deal with resolving this issue with each of the supported distros.