The battle of the hypervisors continues. Microsoft has done an admirable job positioning Hyper-V as one you must contend with, even if you prefer vSphere for certain virtualization tasks. You’ll find plenty of sound advice for working with and configuring Hyper-V in the blogs presented here. As a side note, I don't know why anyone hasn't yet latched onto the title The Hypervisor Advisor. If you’re a virtualization expert looking to start up a blog, feel free to steal that title!
One recent post, "VMQ on Team Interface Breaking Hyper-V Networking," gets into the nitty gritty of why several VMs weren't communicating:
"I recently had a situation where virtual machines on a Windows Server 2016 (WS2016) Hyper-V host could not communicate with each other. Ping tests were failing: Extremely high latency Lost packets In this case, I was building a new Windows Server 2016 demo lab for some upcoming community events in The Netherlands and Germany, an updated version of my Hidden Treasures in Hyper-V talk that I’ve done previously at Ignite and TechEd Europe (I doubt I'll ever do a real talk at Ignite again because I’m neither a MS employee or a conference sponsor). The machine I’m planning on using for these demos is an Intel NUC. It’s small, powerful, and is built with lots of flash storage. My lab consists of some domain controllers, storage, and some virtualized (nested) hosts, all originally connected to an external vSwitch. I built my new hosts, but could not join them to the domain. I did a ping from the new hosts to the domain controllers, and the tests resulted in massive packet loss. Some packets go through but with 3000+ MS latency."
In this case, I was building a new Windows Server 2016 demo lab for some upcoming community events in The Netherlands and Germany, an updated version of my Hidden Treasures in Hyper-V talk that I’ve done previously at Ignite and TechEd Europe (I doubt I'll ever do a real talk at Ignite again because I’m neither a MS employee or a conference sponsor). The machine I’m planning on using for these demos is an Intel NUC. It’s small, powerful, and is built with lots of flash storage. My lab consists of some domain controllers, storage, and some virtualized (nested) hosts, all originally connected to an external vSwitch. I built my new hosts, but could not join them to the domain. I did a ping from the new hosts to the domain controllers, and the tests resulted in massive packet loss. Some packets go through but with 3000+ MS latency."
"I see very often confusion around the configuration of the Hyper-V networking and the creation of the virtual networks (Hyper-V). Therefore I will try to give you here a short/simple overview how you can configure your Hyper-V Host networking environment in regards to best practice which ensures the reliability and availability of your virtualized workloads."
What are some of your favorite Hyper-V blogs? Drop me a line at [email protected]!
Posted by Lafe Low on July 7th, 2017 at 1:08 PM