Two Hyper-V Host connect VM's on internal network? - Hyper-V
Two Hyper-V Host connect VM's on internal network? - Hyper-V
#LnQ¯\_(ツ)_/¯
Two Hyper-V Host connect VM's on internal network? - Hyper-V
or do i need a extra NIC on each hyper-v host and connect them with a cross over cabel?
Yes, the crossover could work or just use another physical switch.
Two Hyper-V Host connect VM's on internal network? - Hyper-V
Assuming each host has an unused physical NIC adapter you can configure another external vSwitch associated with this adapter (uncheckallow management operating system to share ….) on each host, then do two things;
- plug these adapters into a common physical switch
- configure the VM guests to use the new vSwitch
If you only have the single physical NIC in each host then I'd move the VM guests to an external vSwitch and configure them on 192.168.1.xxx network.
((please don't forget to mark helpful replies as answer)
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter ManagementDisclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.
Two Hyper-V Host connect VM's on internal network? - Hyper-V
But i dont want the vm's on my private network. I want to isolate them?
Was thinking doing thisLAB01 connected to private Network - add a second usb nic to connect to LAB02 with static ip.Create a external network binded to the usb nic - do the same on LAB02 onboard nic.Can above solution work or do i need a extra NIC on each hyper-v host and connect them with a cross over cabel?
Two Hyper-V Host connect VM's on internal network? - Hyper-V
or do i need a extra NIC on each hyper-v host and connect them with a cross over cabel?
Yes, the crossover could work or just use another physical switch.
Two Hyper-V Host connect VM's on internal network? - Hyper-V
Hi,
Thanks for your question.
If this, based on my experience, you could simply deploy RAS feature (Routing and Remote Access) on the two hosts. Then both configure LAN Routing on them.
https://protechgurus.com/configure-lan-routing-windows-server-2016/
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Then we can interconnect the two subnets with VMs across the physical network, but isolates with it. Although, the VMs within the different hosts can communicate and have the same mask, they actually reside in the different subnets.
If you have enough NICs on each host, we can implement you want as Dave said.
Thanks for your sharing and support. If you have any question or concern, please feel free to let me know.
Have a nice day!
Best regards,
Michael
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]
Two Hyper-V Host connect VM's on internal network? - Hyper-V
#LnQ¯\_(ツ)_/¯
Two Hyper-V Host connect VM's on internal network? - Hyper-V
Two Hyper-V Host connect VM's on internal network? - Hyper-V
Agree with Tim, the network is independent of the operating systems used. It would still work.
Two Hyper-V Host connect VM's on internal network? - Hyper-V
Two Hyper-V Host connect VM's on internal network? - Hyper-V
Two Hyper-V Host connect VM's on internal network? - Hyper-V
"but think you need a 2nd network card on each device so they can connect to a seperet network as internal."
Internal networks do not allow communication between hosts. It allows communication among all the virtual machines on a single host and the host itself.
In order for VMs residing on different hosts, you must use external networks. You can create multiple external networks on a NIC, but if you do not want packets from one subnet on the physical connection of a given NIC, you have to have a second NIC for that other subnet.