Default implementations of TCP/IP typically set the MTU (maximum transmission unit) size at 1500 bytes. This is to ensure optimal interactions with legacy systems and Internet pathways. Using larger values for MTU (jumbo frames) can increase the speed of large data transfers because, when all goes well, there are more useful data bytes per overhead header and encapsulation bytes.
A long-standing barrier to virtualization is specialized hardware required by applications. It might not ever be possible to virtualize some of those solutions, but you do have options for applications requiring USB-connected devices. This applies to both 2008 R2 and 2012.
Floppy disks have mostly disappeared from datacenters large and small, but their legacy lives on. As one of the oldest technologies since the dawn of the personal computer, support is ubiquitous. That makes their virtual equivalents especially well-suited to help solve any problems you might encounter with the other drive technologies in a virtual machine. If you have a virtual machine that doesn’t recognize its virtual CD-ROM drive or the SCSI system and you don’t want to power it off to add a virtual IDE VHD, the virtual floppy might be exactly what you need.
A critical skill, too often handled haphazardly on-the-fly, is the creation and sizing of virtual machines. The efficiency of modern hypervisors often covers for configurations that could have used a little more forethought, and many SMBs won’t tax their systems enough for it to be of great concern — at least not until the bug of VM sprawl that eventually infects most installations makes it a concern. To maximize your potential for virtual machine density, taking great care in the creation of guest configurations can provide substantial payback.
With Hyper-V’s “knobless” design, the biggest thing you have to remember about managing Hyper-V’s memory is to not try to assign more to virtual machines than you actually have available in your host. That’s not to say that you can’t find some room for tweaking.
The virtual switch provided by Hyper-V is compliant with the official 802.1q standard, which means that it can assign its virtual switch ports to virtual local area networks (VLANs). Hyper-V will assign 802.1q VLAN tags to outbound packets from those switch ports and will properly route inbound 802.1q VLAN-tagged packets to their proper virtual switch ports. Understanding the concept is the hardest part; configuring Hyper-V for it is simple.
Anyone who has read much of my work on Hyper-V knows that I’m of the opinion that networking is one of the most complicated aspects of setting up Hyper-V, especially in a clustered environment. Part of it is that a lot of the concepts in Hyper-V networking lack a corollary in the physical realm so previous experience doesn’t carry forward very well. Another part of it is that Hyper-V is the first time that many administrators will see multiple network cards in the same physical unit that aren’t teamed together. One aspect that confuses a lot of people is the role of binding order for all those adapters in the parent partition. The contents of this post will apply to both Hyper-V R2 and 2012.
Hyper-v 2012 introduces several new features and improvements over its predecessors and they’re all getting plenty of attention. This article will highlight the features I’ve employed most during the first few days of testing and implementation and looks at the ones I expect will get the most usage in the future.
Hardware failure presents the greatest drawback to consolidation on a hypervisor. Whereas one malfunctioning stick of RAM used to be a threat to one operating system, it can now bring down several virtual machines at once. Proper planning can mitigate and in some cases eliminate the effects of such a failure.
One of the many benefits of virtualization is the “abstraction” of hardware. This means that a virtualized operating system is never closely matched with the hardware that it lives on. This gives systems administrators access to a large number of previously unavailable capabilities. One of these is “high availability”. Freed from the constraints of the underlying hardware, virtual machines can be easily moved to other hardware. These moves can even be automated.
In 2008, I was tasked with evaluating the potential virtualization strategy for a medium-sized business. A solutions provider was trying to make a sale on VMWare vSphere 3.5. The business wasn’t opposed to it, but as a matter of due diligence I was tasked with considering the competition. As you might recall, there weren’t many competitors at that time.
Even though Hyper-V R2 is a fantastic hypervisor, it’s not easy to manage if you haven’t got the proper tools. Fortunately, there are plenty of downloads available if you know where to look. Here are our top 10 favorite free Hyper-V downloads. 1) Microsoft’s Remote Server Administration Tool If you didn’t install Hyper-V as a role inside Windows Server, or if you used a Core installation of Windows, you won’t have any management tools at all to start with. Even if you’re running a full Server GUI to manage Hyper-V, it’s still a good idea to manage the hypervisor remotely to lower resource contention and add a little convenience. Download and install Microsoft’s Remote Server Administration Tools to your computer running Windows 7 and manage your Hyper-V and Failover Cluster (as well as a number of non-Hyper-V roles on your other Windows Servers) from the comfort of your own desktop.… Read More»
According to members of Microsoft’s Hyper-V team, one of the chief design goals of the hypervisor was to make it “knobless”. They wanted it to just work without a lot of tuning and balancing on the part of administrators. For the most part, that works out pretty well — once you’ve deployed.