If you are running Windows Server 2012 Hyper-V hosts and you are managing them with System Center Virtual Machine Manager 2012 SP1 and you are running VM Networks with Network Virtualization you can get the following error when you try to deploy a new Virtual Machine to the Hyper-V host.
“Windows network virtualization is not enabled on a host NIC available for placement”
This happens if:
- You create a Logical Network with Network Virtualization enabled
- You add the Logical Network to a Host Adapter or a Logical Switch on the Hyper-V host
- You create a Isolated VM Network
- Deploy a new Virtual Machine with the VM Network.
Resolution:
- Enable the Windows Network Virtualization Filter driver on the Hyper-V host
If you are running this on a Team you have to enable the Windows Network Virtualization Filter driver on the Network Adapter Team.
Tags: error, Hyper-V, Micorsoft, Network Virtualization, SCVMM, SCVMM 2012 SP1, SP1, System Center, System Center 2012, System Center 2012 SP1, Virtual Machine Manager, Virtualization, VM Network, VMM, Windows Server, Windows Server 2012 Last modified: January 6, 2013
Easy to do through the GUI, now how to enable this setting on a server core machine?
Hi
I’m currently testing 2012. I’ve created a Windows based team (2 Physical-NICs) and created a Virtual Switch on the Team. (Can only create one per interface)
Then I’ve created vEthernet Cards on top of the Virtual Switch, each with their own weight and VLAN assigned (Done everything via PowerShell).
Everything works perfectly, except when the Dynamic IP address leasing from VMM 2012 SP1 comes into the picture. I cannot get VMM to lease an IP address to the Windows machine with this type of configuration.
Can it be that I need more than one Virtual Switch in order to get this working?
Any help would be appreciated.
Thanks.
@ Gill
$sw = Get-VMSwitch –Name […]
or
$sw = Get-VMSwitch -SwitchType External
Then
Enable-NetAdapterBinding -InterfaceDescription $sw.NetAdapterInterfaceDescription -ComponentID “ms_netwnv”