github/acrn-hypervisor
1
0
Fork 0
mirror of https://github.com/projectacrn/acrn-hypervisor.git synced 2025-09-09 20:59:03 +00:00
Code Issues Projects Releases Wiki Activity

DOC: Update-GSG-rt_industry_ubuntu

Browse Source 
Remove the Power Management ('pm') parameters from the sample launch scripts,
and update the comments, At most one VM is allowed to use "--pm_notify_channel uart"
at a time, since only one socket connection to SOS life_mngr is allowed.
Remove it by default and allow user to add on demand
rt_industry_ubuntu.rst
enable_s5.rst

Signed-off-by: li shuang <shuangx.li@intel.com>
This commit is contained in:
li shuang
2021-03-30 09:21:13 +08:00
committed by David Kinder
parent f94a43f98e
commit f583af3747
2 changed files with 29 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
doc/tutorials/enable_s5.rst
View File

@@ -48,6 +48,22 @@ The diagram below shows the overall architecture:
.. graphviz:: images/s5-scenario-2.dot
:name: s5-scenario-2
Initiate a system S5 from within a User VM (e.g. HMI)
=====================================================
As in Figure 56, a request to Service VM initiates the shutdown flow.
This could come from a User VM, most likely the HMI (Windows or user-friendly Linux).
When a human operator click to initiate the flow, the lifecycle_mgr in it will send
the request via vUART to the lifecycle manager in the Service VM which in turn acknowledge
the request and trigger the following flow.
.. note:: The User VM need to be authorized to be able to request a Shutdown, this is achieved by adding
"``--pm_notify_channel uart``" in the launch script of that VM.
And, there is only one VM in the system can be configured to request a shutdown. If there is a second User
VM launched with "``--pm_notify_channel uart``", ACRN will stop launching it and throw out below error message:
``initiate a connection on a socket error``
``create socket to connect life-cycle manager failed``
Trigger the User VM's S5
========================