System Manager#

The System Manager, SysMgr, coordinates the ordering of state transition of each partition during a system state transition. The System Manager performs the following:

  • System Manager supports following System Power state transitions:

    • Boots Guest OS after a time delay as specified in PCT configuration.

    • Executes a full System Shutdown and System Reboot.

    • Executes entry into Suspend To RAM and resumes System back from Suspend state as required.

  • System Manager coordinates system boot between a Guest OS and Virtualization servers.

    • System Manager broadcasts Guest OS power state change events (Boot, Shutdown, Reboot, Suspend, Resume) for a Guest OS to all the Virtualization Servers. The servers handle actions specific to the Guest OS power state change.

  • System Manager requests all Guest OS and Virtualization Server to enter a Suspend-To-RAM state during System Suspend to RAM.

  • System Manager requests all Guest OS and Virtualization Servers to shutdown during System shutdown and System reboot.

Boot Between Guest OS and Servers#

Before initiating a boot, the System Manager waits for acknowledgment (ACK) from all Virtualization Servers. Once the System Manager receives the ACK, it starts the boot process for the Guest OS.

Note

A time delay for booting up a Guest OS can also be set prior to initiating the boot process by setting the .boot_delay configuration parameter in guest_config.h. The delay is the time (in milliseconds) since the system is powered ON.

.boot_delay = 0,

The Guest OS and the servers communicate over the Inter-VM Communication (IVC) channels.

Only a privileged Guest OS can issue System power state transitions (System Shutdown, System Reboot and Entry and Exit from Suspend to RAM.) A VM is configured to be privileged by setting the .is_privileged parameter in guest_config.h for specified Guest OS.

On this page