acrn-hypervisor/tools/acrn-manager/acrnd.service

[Unit]
Description=ACRN manager deamon

[Service]
Type=simple
ExecStart=/usr/bin/acrnd
ExecStop=/usr/bin/killall -s TERM acrnd

[Install]
WantedBy=multi-user.target
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`

			`[Service]`
			`Type=simple`
			`ExecStart=/usr/bin/acrnd`
			`ExecStop=/usr/bin/killall -s TERM acrnd`

			`[Install]`
			`WantedBy=multi-user.target`