Microsoft has released a hotfix for when you cannot add network adapters to a virtual machine on a Windows Server 2008 R2-based failover cluster.
Consider the following scenario:
- You create a failover cluster on some computers that are running Windows Server 2008 R2 SP1.
- You enable the Hyper-V role on both cluster nodes.
- You configure a virtual machine as a cluster resource.
- You try to add a network adapter to the virtual machine by using the Refresh Virtual Machine Configuration wizard.
In this scenario, you cannot add the network adapter successfully until the virtual machine is removed from the cluster.
A supported hotfix is available from Microsoft.
This blog post is the property of Aidan Finn (@joe_elway / http://www.aidanfinn.com) and may not be reused in any manner without prior consent of Aidan Finn. You may quote one paragraph from this blog post if you link to the original blog post.
- You Pause A Clustered Hyper-V Host And Low Priority VMs are QUICK MIGRATED!
- KB2752183 – Cannot Migrate A W2008 R2 Hyper-V VM From Non-Bulldozer Host To Bulldozer Host
- PowerShell Script To Create A Converged Fabric For Clustered Windows Server 2012 Hyper-V Host
- Updated: PowerShell Script To Create A Converged Fabric For Clustered Windows Server 2012 Hyper-V Host
- KB2722461 – High Rate Of SMIs May Cause Hyper-V Host To Hang At Boot On W2008 R2