Create VM Mutually Exclusive/Affinitive Host Scheduling Policies

Virtual machine mutually exclusive/affinitive host scheduling policies need to be bound to both a virtual machine scheduling group and a host scheduling group to take effect on the virtual machines and hosts within the groups. Assuming you have already added multiple hosts running multiple business virtual machines, you can follow the steps below to use these scheduling policies:

1. Create a VM Scheduling Group
2. Create a Host Scheduling Group
3. Create a VM Mutually Exclusive/Affinitive Host Scheduling Policy

Create a VM Scheduling Group

In the ZSvirt platform, click Menu > Business Reliability > VM Scheduling Policy > VM Scheduling Group to enter the VM Scheduling Group page. Click the New VM Scheduling Group operation to create a new group.

Set the following parameters:

• Name: Set the virtual machine scheduling group name, for example, Virtual Machine Scheduling Group A2
• Description: Optional, can be left blank
• Virtual Machine: Select one or more target virtual machines to join this scheduling group

After clicking OK, the new virtual machine scheduling group will be created successfully.

Create a Host Scheduling Group

Click Host Scheduling Group > New Host Scheduling Group, and set the following parameters:

• Name: Set the host scheduling group name, for example, Host Scheduling Group A2
• Description: Optional, can be left blank
• Host: Select one or more hosts to join this scheduling group

After clicking OK, the new host scheduling group will be created successfully.

Create a VM Mutually Exclusive/Affinitive Host Scheduling Policy

Click VM Scheduling Policy > New VM Scheduling Policy, and set the following parameters:

• Name: Set the virtual machine scheduling policy name, for example, Virtual Machine Scheduling Policy A2
• Description: Optional, can be left blank
• Type: Select Virtual Machine Mutually Exclusive or affinitive Host
• Execution Mechanism: Supports Hard and Soft execution mechanisms
  • Hard: Virtual machines are forcibly assigned hosts based on the associated VM scheduling policies. For example, if you associate the VM Exclusive from Each Other policy with a VM scheduling group and select the Hard mechanism for the policy, any two of the virtual machines in the scheduling group are not allowed to run on the same host. If no host is available to be scheduled based on the policy for a virtual machine, the virtual machine will end up failure upon startup.
  • Soft: Virtual machines are primarily assigned hosts based on the associated VM scheduling policies. For example, if you associate the VM Exclusive from Each Other policy with a VM scheduling group and select the Soft mechanism for the policy, any two of the virtual machines in the scheduling group will primarily not run on the same host. If no host is available to be scheduled based on the policy for a virtual machine, the virtual machine will attempt to run on a host that does not satisfy the policy.
• Associate VM Scheduling Group: After binding, the scheduling policy will take effect on all virtual machines within the virtual machine scheduling group. You can bind existing or newly created scheduling groups. Here, select the scheduling group created above.
• Associate Host Scheduling Group: After binding, the scheduling policy will take effect on all hosts within the host scheduling group. You can bind existing or newly created scheduling groups. Here, select the scheduling group created above.

After clicking OK, the new virtual machine mutually exclusive/affinitive host scheduling policy will be created successfully. The virtual machines and hosts will run according to the scheduling policy.