RHEV: RHEV behavior on a VM abnormally terminated
Environment
Red Hat Enterprise Virtualization (RHEV) 2.1
Issue
When VM is abnormally terminated (e.g. VM receive SIGKILL signal):
- What is the number of reboots by RHEV-M?
- Can we change setting if there is the number of reboots?
- Which RHEV-H has reboot VM?
Resolution
Considering the following scenarios:
- A VM can be defined as highly available (HA). Once defined a such, if it terminates abnormally, RHEV-H running the VM is responsible to restart it. If it terminates abnormally again, it will be restarted again and so on - unless the abnormal termination stops occuring or till VM's definition is changed not to be HA.
- If a host fails to run and there are VMs running on it, RHEV-M is responsible for making a migration of those VMs to another host (if available), according to cluster's policy definitions.
For more information please refer to these sections of the Administration Guide:
- Cluster Policy
- Highly Available host / server.
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
