OrgACRN
/
acrn-hypervisor
mirror of https://github.com/projectacrn/acrn-hypervisor.git
1
0
Fork 0
Code Issues Releases Wiki Activity
acrn-hypervisor/misc/acrn-manager/acrnd.service

16 lines
295 B
SYSTEMD
Raw Normal View History

tools: acrnd: the deamon for acrn-manager There will be a daemon running on SOS: to forward wakeup_reason to acrn-dm; to co-ordinate the lifecycle of VMs and SOS; to handle ioc-timed wakeup/poweron. 1.to forward wakeup_reason to acrn-dm acrnd is responsible to retrive wakeup_reason from SOS lifecycle service and attach the wakeup_reason to acrn-dm parameter for ioc-dm; 2.co-ordinate the lifecycle of VMs and SOS When SOS is about to suspend/shutdown, SOS lifecycle service will send a request to acrnd to guarantee all guest VMs are suspended or shutdown before SOS suspending/shutdown process continue. On receiver the request, acrnd starts polling the guest VMs state, and notify SOS lifecycle service when all guest VMs are put in proper state gracefully. 3.handle ioc-timed wakeup/poweron For vechile specific mode like garage mode, guest UOS may need to wakeup/poweron in a future time for tasks such as map updating etc. To setup a timed wakeup/poweron, ioc-dm will send request to acrnd, acrnd maintains a list of timed requests from guest VMs, and acrnd selects the nearest request and send it to SOS lifecycle service who will setup the physical IOC. Reviewed-by: Yan Like <like.yan@intel.com> Acked-by: Geoffroy Van Cutsem <geoffroy.vancutsem@intel.com> Signed-off-by: Tao Yuhong <yuhong.tao@intel.com>
2018-06-21 23:31:46 +08:00
[Unit]
Description=ACRN manager deamon
tools: acrnd: bugfix: service lack of prerequisition As a system service, acrnd will launch UOS, that must be done after all required services and conditions are ready, such as acrnprobe, weston, etc. Tracked-On: #1278 Signed-off-by: Tao Yuhong <yuhong.tao@intel.com>
2018-09-18 18:58:21 +08:00
After=weston.service
After=systemd-resolved.service
ConditionPathExists=/sys/kernel/gvt
ConditionPathExists=/dev/acrn_vhm
tools: acrnd: the deamon for acrn-manager There will be a daemon running on SOS: to forward wakeup_reason to acrn-dm; to co-ordinate the lifecycle of VMs and SOS; to handle ioc-timed wakeup/poweron. 1.to forward wakeup_reason to acrn-dm acrnd is responsible to retrive wakeup_reason from SOS lifecycle service and attach the wakeup_reason to acrn-dm parameter for ioc-dm; 2.co-ordinate the lifecycle of VMs and SOS When SOS is about to suspend/shutdown, SOS lifecycle service will send a request to acrnd to guarantee all guest VMs are suspended or shutdown before SOS suspending/shutdown process continue. On receiver the request, acrnd starts polling the guest VMs state, and notify SOS lifecycle service when all guest VMs are put in proper state gracefully. 3.handle ioc-timed wakeup/poweron For vechile specific mode like garage mode, guest UOS may need to wakeup/poweron in a future time for tasks such as map updating etc. To setup a timed wakeup/poweron, ioc-dm will send request to acrnd, acrnd maintains a list of timed requests from guest VMs, and acrnd selects the nearest request and send it to SOS lifecycle service who will setup the physical IOC. Reviewed-by: Yan Like <like.yan@intel.com> Acked-by: Geoffroy Van Cutsem <geoffroy.vancutsem@intel.com> Signed-off-by: Tao Yuhong <yuhong.tao@intel.com>
2018-06-21 23:31:46 +08:00
[Service]
Type=simple
capture acrnd AaaG booting messages to journald It's for AaaG boot time measurement only. Tracked-On: #1759 Signed-off-by: Yan, Like <like.yan@intel.com> Signed-off-by: Tao Yuhong <yuhong.tao@intel.com>
2018-10-26 23:57:00 +08:00
ExecStart=/usr/bin/acrnd -t
StandardOutput=journal
StandardError=journal
tools: acrnd: the deamon for acrn-manager There will be a daemon running on SOS: to forward wakeup_reason to acrn-dm; to co-ordinate the lifecycle of VMs and SOS; to handle ioc-timed wakeup/poweron. 1.to forward wakeup_reason to acrn-dm acrnd is responsible to retrive wakeup_reason from SOS lifecycle service and attach the wakeup_reason to acrn-dm parameter for ioc-dm; 2.co-ordinate the lifecycle of VMs and SOS When SOS is about to suspend/shutdown, SOS lifecycle service will send a request to acrnd to guarantee all guest VMs are suspended or shutdown before SOS suspending/shutdown process continue. On receiver the request, acrnd starts polling the guest VMs state, and notify SOS lifecycle service when all guest VMs are put in proper state gracefully. 3.handle ioc-timed wakeup/poweron For vechile specific mode like garage mode, guest UOS may need to wakeup/poweron in a future time for tasks such as map updating etc. To setup a timed wakeup/poweron, ioc-dm will send request to acrnd, acrnd maintains a list of timed requests from guest VMs, and acrnd selects the nearest request and send it to SOS lifecycle service who will setup the physical IOC. Reviewed-by: Yan Like <like.yan@intel.com> Acked-by: Geoffroy Van Cutsem <geoffroy.vancutsem@intel.com> Signed-off-by: Tao Yuhong <yuhong.tao@intel.com>
2018-06-21 23:31:46 +08:00
[Install]
WantedBy=multi-user.target