Hello,
I've been tasked to do a trial of Hyper-V to see if it is a viable vSphere alternative for us. I have reserved equipment for the test, but so far I have not got too far. Our shop is entirely Unix & VMware at present, so we have minimal Windows
Server experience beyond what is needed to run vCenter.
For the first server, we need a place to manage things so we have installed Windows Server 2012, configured networking, and added the Hyper-V role. (All other cluster nodes will be bare Hyper-V.)
For the tests, the physical network topology of each cluster node is two Intel gigabit NICs teamed with LACP and sliced into four VLANs:
- Management LAN
- Storage LAN (not yet used)
- Migration LAN (not yet used)
- Virtual Machine LAN
Everything seems fine with the physical configuration. It was no trouble to configure and seems to work fine; both the management VLAN and storage LAN are connected to the Windows Server 2012 host and work fine. I have set up the virtual machine
LAN as external & dedicated to Hyper-V (unchecked "Allow management operating system to share this network adapter" in Hyper-V Virtual Switch Manager). I have created a small virtual machine and used the "Legacy" adapter type (to PXE boot) on the
virtual switch.
All appears to work, but during PXE boot no IP address is obtained from the DHCP server. I did some packet tracing and it seems the requests are going out and the DHCP offers are coming back, but they aren't making it to the VM.
As a second test, I loaded a handy FreeBSD Live CD image, which works fine and sees the network adapter but has the same behavior. Outbound traffic (e.g. ARP requests) is fine but inbound traffic (e.g. ARP replies) are not received.
As a third test, I configured two virtual machines running the FreeBSD image. I statically configured addresses on both, and they could see each other, but still neither could see traffic from the outside world.
So, the problem is definitely some sort of barrier between the VLAN adapter and the virtual switch. I've tried disabled the Windows Firewall on the Windows Server side, but no effect.
Does anyone have any suggestions for where I could look to further debug this problem?
Thanks for any help!