Triggering the Recovery Mechanism Inside a Guest OS Container

The recovery mechanism discussed under topic Triggering Recovery Mechanism by Loader is true until Hypervisor binary is loaded. Once Hypervisor boots up, it is no longer true due to the following reasons:

• More than one guest OS is configured in the PCT. Each guest OS boots up independently in its guest OS environment provided by Hypervisor. Guest OSes do not have information about other guest OSes.
• It may be possible that one or more guest OS boot fails, and other guest OSes boot up fine. There may be multiple boot failure scenarios here. How is each failure scenario handled?
• If one or more guest OS boot fails, then how and who decides whether to trigger recovery mechanism or reboot that guest OS?
• Triggering recovery mechanism in a guest OS environment involves informing Hypervisor. Hypervisor makes the final decision to trigger recovery.

To handle boot failures inside a guest OS environment, a different recovery mechanism policy is required inside the guest OS environment.