the cluster network configuration. For nonclustered hosts, Live Migration must be
configured and enabled if it was not enabled when you enabled the Hyper-V role on
the server. The configuration for Live Migration is part of the Hyper-V host’s core
configuration, which is as follows:
1 . Launch Hyper-V Manager (this can also be configured using SCVMM in the
Migration Settings area of the server’s properties).
2 . Select the Hyper-V host, and select the Hyper-V Settings action.
3 . Select the Live Migrations area.
4 . Select the Enable Incoming And Outgoing Live Migrations check box, as shown in
Figure 7.35.
5 . Note that the number of simultaneous Live Migrations allowed can be configured,
and this number is the maximum allowed and not necessarily the number of
simultaneous Live Migrations that will always be performed. The migration
module examines the amount of available bandwidth and dynamically ascertains
whether an additional Live Migration could be supported by the amount of
bandwidth available on the migration network. If not, the migration is queued.
6 . The configuration allows any network that is available to be used for Live
Migration. Or you can select a specific network or networks by selecting the Use
These IP Addresses For Live Migration check box and then adding and ordering IP
networks that should be used in CIDR notation—for example, xxx.xxx.xxx.xxx/n,
where the n is the number of bits to use for the subnet mask, so 10.1.2.0/24 is the
same as 10.1.2.0 with a subnet mask of 255.255.255.0. This would allow any IP
address in the 10.1.2.0 network to be used for Live Migration.
To set this using PowerShell, use the Add-VMMigrationNetwork and Set-
VMMigrationNetwork cmdlets. Note that this setting is for the networks that can be
used to receive incoming Live Migration. When a host is the source of a Live
Migration, it will use whatever network it has available that can communicate with
the Live Migration network configured to receive on the Live Migration target.
7 . Click OK.