On Wed, Aug 26, 2015 at 02:13:54PM +0200, Martin Kletzander wrote:
> On Wed, Aug 26, 2015 at 11:41:54AM +0100, Daniel P. Berrange wrote:
> >On Tue, Aug 25, 2015 at 05:12:20PM +0200, Martin Kletzander wrote:
> >>When images are on mounted filesystems, there is no guarantee libvirtd
> >>will start be
On Wed, Aug 26, 2015 at 11:41:54AM +0100, Daniel P. Berrange wrote:
On Tue, Aug 25, 2015 at 05:12:20PM +0200, Martin Kletzander wrote:
When images are on mounted filesystems, there is no guarantee libvirtd
will start before they are mounted. In systemd world, this is done
with 'After=systemd.mo
On Tue, Aug 25, 2015 at 05:12:20PM +0200, Martin Kletzander wrote:
> When images are on mounted filesystems, there is no guarantee libvirtd
> will start before they are mounted. In systemd world, this is done
> with 'After=systemd.mount' in the service file.
>
> Signed-off-by: Martin Kletzander
When images are on mounted filesystems, there is no guarantee libvirtd
will start before they are mounted. In systemd world, this is done
with 'After=systemd.mount' in the service file.
Signed-off-by: Martin Kletzander
---
daemon/libvirtd.service.in | 1 +
1 file changed, 1 insertion(+)
diff -
