I use VMWare ESX 6.0 as the main hypervisor, and then install 2 VM windows server 2k12. the first VM I use for Hyper-V and create 2 VM again on it. 2 VM on top Hyper-V I suppose VM A and VM B. My problem is VM A and VM B cannot ping to physical server (VMware vsphere). Server Hyper-v can ping to VMware and ping to Guest OS (VM A and VM B). But I try on VMware Workstation all VM can communication (test ping).

Thank you for your respons. all host and vm in the same network. But just VM A, and VM B cannot ping to VMWare and VM C. But finally my problem solved. this problem because setup vSwitch in VMWare in side promiscuous mode. So we need change promiscuous mode from reject to accept. and now all vm A and vm B can ping to external network.

The important unit here is the Virtual Machine Manager (VMM), quite similar to VMware vCenter

Hyper-V Manager is a lightweight tool that depends only upon MMC.EXE; VMM has hefty hardware and software requirements, including a Microsoft SQL Server deployment. VMM must also install an agent component on each Hyper-V host that it manages.

Hyper-V Manager is free with the Windows desktop or Windows Server license that it runs on; VMM has no free edition. It can only be purchased along with the System Center suite, which is very expensive.

If you can afford the $5k for Essentials Plus (and have less than 4 hosts) I vastly prefer VMware's ESXi to Hyper-V. Lack of support for file level storage was my biggest gripe with Hyper-V. IMO, VMware has the strongest "paid-for" product and Xenserver has the strongest "free" product (I have no experience with KVM). Hyper-V does have an optional "paid for" component to make it easier to manage multiple hosts. They will all charge you for support.

I think people assume that because Hyper-V is a Microsoft product they won't need support but they are often wrong, and Microsoft's support is the worst of the bunch.

Thank you for your respons. all host and vm in the same network. But just VM A, and VM B cannot ping to VMWare and VM C. But finally my problem solved. this problem because setup vSwitch in VMWare in side promiscuous mode. So we need change promiscuous mode from reject to accept. and now all vm A and vm B can ping to external network.