On Tue, Dec 09, 2014 at 01:06:55PM +0100, Olaf Hering wrote: > Starting domains during boot will most likely require network for the > local bridge and it may need access to remote filesystems. Add ordering > tags to systemd service file. > > Signed-off-by: Olaf Hering <o...@aepfle.de> > Cc: Ian Jackson <ian.jack...@eu.citrix.com> > Cc: Stefano Stabellini <stefano.stabell...@eu.citrix.com> > Cc: Ian Campbell <ian.campb...@citrix.com>
Acked-by: Wei Liu <wei.l...@citrix.com> > --- > > This should go into 4.5 to avoid failures if xendomains is scheduled before > remote mounts are fully available. > > tools/hotplug/Linux/systemd/xendomains.service.in | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/tools/hotplug/Linux/systemd/xendomains.service.in > b/tools/hotplug/Linux/systemd/xendomains.service.in > index 9962671..66e2065 100644 > --- a/tools/hotplug/Linux/systemd/xendomains.service.in > +++ b/tools/hotplug/Linux/systemd/xendomains.service.in > @@ -2,6 +2,8 @@ > Description=Xendomains - start and stop guests on boot and shutdown > Requires=proc-xen.mount xenstored.service > After=proc-xen.mount xenstored.service xenconsoled.service > xen-init-dom0.service > +After=network-online.target > +After=remote-fs.target > ConditionPathExists=/proc/xen/capabilities > > [Service] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
