If you want to ensure that a resource never runs on specific hosts, you can set the
possible owners. When a resource is restricted to possible owners, it cannot run on
hosts that are not possible owners. This should be used with care, because if no
possible owners are available that are configured, the resource cannot start, which
may be worse than it just not running on a nonoptimal host. To set the possible
owners, you need to modify the cluster group of the virtual machine, which is in the
bottom pane of Failover Cluster Manager. Right-click the virtual machine resource
group and select Properties. Under the Advanced Policies tab, the possible owners are
shown. If you unselect servers, that specific virtual machine cannot run on the
unselected servers.
The same PowerShell cmdlet is used, Set-ClusterOwnerNode, to set both the preferred
and possible owners. If the cmdlet is used against a cluster resource (that is, a virtual
machine), it sets the preferred owners. If it is used against a cluster group, it sets the
possible owners.
It’s common where possible to cluster the Hyper-V hosts to provide mobility and high
availability for the virtual machines and create guest clusters where applications
running within the virtual machines are cluster aware. This can be seen in Figure 7.14.
Figure 7.14 Guest cluster running within a Hyper-V host cluster