6.9.3. Demonstrating virtual-machine high availability of incorrectly-fenced hosts

  1. On the Tree pane, select VMs. The available virtual machines display on the Virtual Machines tab.
    Virtual machines running on hosts

    Figure 6.13. Virtual machines running on hosts

    In this example, there are currently two virtual machines running on the Atlantic host; and another four on Pacific. You can check whether a virtual machine is highly available by selecting it looking at the General tab of the details pane. Here, on the Atlantic host RHEL6Thames is set to be highly available, while RHEL6Congo is not.
  2. On the Tree pane, select Hosts. The available hosts display on the Hosts tab. Select the Atlantic host, click the Power Management drop-down menu and select Restart.
    Restart host

    Figure 6.14. Restart host

    The Restart Host(s) dialog displays, click OK to confirm and proceed. The host's status changes to Reboot, then Non-Responsive.
    Non-responsive host

    Figure 6.15. Non-responsive host

    You have now simulated an environment where a host is manually fenced before it was placed into maintenance. Since power management has been configured for this host, it will automatically reboot after a short period.
  3. While the host is being restarted, observe what has happened to the virtual machines which were running on it. On the Tree pane, click VMs to display the Virtual Machines tab. Notice that both the virtual machines running on Atlantic were shut down as soon as the host was restarted.
    Virtual machines starting on another host

    Figure 6.16. Virtual machines starting on another host

    The highly available virtual machine, RHEL6Thames, is automatically restarted. Its status changes from Down to Wait for Launch, and then to Powering Up. It runs on the Pacific host in the interim period while the Atlantic host is still rebooting. In contrast, RHEL6Congo remains turned off, its status displays as Down.