VMWare Workstation & Hypwe-V on Same Windows 10 Host

In my lab environment, I am havng a Windows host which enabled Hyper-V, also installed VMWare workstation. It was very confusion when I tried to put both Hyper-V machines and VMWare machines into same network, since the network names are quite different.

In this post, I am going to record all network names in three different places:

• Windows Host Network Connections
• VMware workstation Virtual Network Editor environment
• Hyper-V Virtual Switch Manager 

Six Physical NICs:

From Device Manager:

VMWare Workstation's Virtual Network Editor

External - Virtual Switch (vEthernet (External) in Windows's network connections)

• External network - Intel(R) 82579LM Gigabit Network Connection - 192.168.2.245

Hyper-V Virtual Switch Manager

Control Panel - Network and Sharing Center

Ethernet = QLogic BCM5709C Gigabit Ethernet (NDIS VBD Client) #63

Ethernet 2 = QLogic BCM5709C Gigabit Ethernet (NDIS VBD Client) #62

Ethernet 3 = QLogic BCM5709C Gigabit Ethernet (NDIS VBD Client) #64

Ethernet 4 = QLogic BCM5709C Gigabit Ethernet (NDIS VBD Client) #65

Ethernet 5 = Intel(R) 82574L Gigabit Network Connection

Ethernet 6 = Intel(R) 82579LM Gigabit Network Connection - 192.168.2.245

Hyper-V 

 

Once you did Hyper-V network new virtual switch configuration to bridge #3 switch, the VMWare VMnet2's bridge configuration will disappear, since that "QLogic BCM5709C Gigabit Ethernet (NDIS VBD Client) #64" has been used by Hyper-V.

But you will find out a new Hyper-V Virtual Ethernet Adapter #10 appears, which is your computer's vEthernet (vEthernet (LAN2). 

Now, the Windows Machines in Hyper-V and VMware workstation can ping each other.

References