In the course of attending Microsoft TechEd, I’ve learned a few things about Hyper-V. For starters, it’s easy to use. That’s really important for a virtualization technology, especially in regards to advanced virtualization features that really make a technology a solution.
One example is to configure migration with Hyper-V. Hyper-V R3 is part of Windows Server 2012 with the Hyper-V role and part of the standalone Hyper-V Server 2012 (free hypervisor). Migration with Hyper-V is possible without shared storage (Cool!) and is easy to configure as well.
For a network that uses 1 Gigabit networking to a host, the default migration limit of two simultaneous migrations should be fine. If a number of network interfaces are provisioned on a switch, which can have an aggregated backplane or 10 Gigabit networking, more than two migrations may be attractive.
Configuring the number of simultaneous migrations for a Hyper-V host is a server setting in the Live Migrations field as shown in Figure A:
From this screen you also can specify designated and preferred IP addresses to use for the migration. This can increase performance as well as provide separation for this type of traffic on the network.
From a usability perspective, when Hyper-V is used by itself (outside of System Center Virtual Machine Manager), this configuration space is quite easy to use yet very powerful. In regards to storage migration configuration (next option in this area of the Hyper-V configuration), the configuration option allows the number of simultaneous storage migrations to be set there.
Virtual machine migration (storage or host) is one of the most critical virtualization administrative tasks. Specifically, it is the key to abstraction from hardware, as it can be done with minimal or manageable downtime. Hyper-V’s migration options, including the free ones, for Hyper-V R3 are easy to use for virtualization administrators.
Do you use Hyper-V migration? If so, share your best practice for configuring the amount of live migrations on the hosts.