This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(121.6, 83%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EE%3C/text%3E%3C/svg%3E)
I am configuring Hyper-V on Windows Server 2022. My server has 2 physical NICs. I don't know much about Hyper-V, so I would enjoy feedback on the best way to configure the NICs for Hyper-V VM and the physical host access. Should I use teaming NICs? Or should I dedicate one NIC to the Hyper-V NIC and the other NIC to the host operating system?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
When you create the vSwitch you'll also assign it some name. Then during the virtual machine guest configuration use the dropdown and select the new vSwitch (by name), then within each virtual machine use each VM's vEthernet to configure the addressing in the exact same manner as if it were a physical NIC
--please don't forget to upvote and Accept as answer if the reply is helpful--
Thank you for answering my questions.
You're quite welcome.
Yes, you can create an external vSwitch. When you create a new external vSwitch the internet protocols are removed from the adapter and the Hyper-V Extensible Switch protocol is added turning that physical port into a multi-port virtual switch. Connect your VMs to this vSwitch and use each VM's vEthernet to configure the addressing in the exact same manner as if it were a physical NIC
vSwiches do not have an address since it is now a multi-port virtual switch.
--please don't forget to upvote and Accept as answer if the reply is helpful--
Dave---
Thanks again for taking the time to answer my questions. Just to confirm, I create the Hyper-V Extensible switch using one of the server's physical NICs (which has a static IP address). For each hosted VM, I point them to the Hyper-V Extensible switch for their NIC. Is that correct?
Most likely leave one for the host to use and configure an external vSwitch for the guests to use.
When you create a new external vSwitch the internet protocols are removed from the adapter and the Hyper-V Extensible Switch protocol is added turning that physical port into a multi-port virtual switch. Connect your VMs to this vSwitch and use each VM's vEthernet to configure the addressing in the exact same manner as if it were a physical NIC
--please don't forget to upvote and Accept as answer if the reply is helpful--
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept as answer if the reply is helpful--
Dave---
Thanks, this answers part of my question. I would configure the Hyper-V NIC to an external connection as they need to "talk" to other VMs, the host server and the Internet. Do you recommend that I dedicate one NIC to Hyper-V? Should that NIC have a static IP address and be shared with the host operating system?
