6.7. High Availability: Virtual Machine Interruption

6.7.1. High availability -- Virtual machine interruption

In the previous section, you demonstrated virtual machine high availability when a host becomes non-responsive and then rebooted. This section simulates a virtual machine crash. The expected outcome is for the highly available virtual machines to restart automatically, while the non-highly available ones will remain shut down until they are manually restarted.
In your current environment, the host that you restarted in the previous section (Atlantic) should be running again. The highly available virtual machine (RHEL6Thames) has been restarted on another host (Pacific), while the non-highly available virtual machine (RHEL6Congo) is still powered down.
For this demonstration, restart RHEL6Congo. The Atlantic host is automatically selected to run this virtual machine as its workload is currently lighter than Pacific's. Next, live migrate two more virtual machines to the Atlantic host so the workload is equally balanced. Select RHEL6RioGrande and RHEL6Thames, and click Migrate. On the Migrate Virtual Machine(s) dialog, leave the option as Select Host Automatically and click OK.
To recap, you now have three virtual machines running on each host. Click on the Host label to alphabetically sort the virtual machines according to host.
Sort virtual machines by host

Figure 6.9. Sort virtual machines by host