Everything which uses xenstored does this via the socket. Update the
existing service files to enable the xenstored.socket with the Requires=
statement. And schedule startup of the given service files after the
socket is enabled with the After= statement.
Once something tries to access the socket systemd will launch xenstored.
Signed-off-by: Olaf Hering <olaf@aepfle.de>
Cc: Ian Campbell <ian.campbell@citrix.com>
Cc: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>
Acked-by: Wei Liu <wei.liu2@citrix.com>
[Unit]
Description=xen-init-dom0, initialise Dom0 configuration (xenstore nodes, JSON configuration stub)
Requires=xenstored.socket
-After=xenstored.service
+After=xenstored.socket
ConditionPathExists=/proc/xen/capabilities
[Service]
[Unit]
Description=qemu for xen dom0 disk backend
Requires=proc-xen.mount var-lib-xenstored.mount xenstored.socket
-After=xenstored.service xenconsoled.service
+After=xenstored.socket xenconsoled.service
Before=xendomains.service libvirtd.service libvirt-guests.service
RefuseManualStop=true
ConditionPathExists=/proc/xen/capabilities
[Unit]
Description=Xenconsoled - handles logging from guest consoles and hypervisor
Requires=xenstored.socket
-After=xenstored.service
+After=xenstored.socket
ConditionPathExists=/proc/xen/capabilities
[Service]
[Unit]
Description=Xendomains - start and stop guests on boot and shutdown
Requires=xenstored.socket
-After=xenstored.service xenconsoled.service xen-init-dom0.service
+After=xenstored.socket xenconsoled.service xen-init-dom0.service
ConditionPathExists=/proc/xen/capabilities
[Service]