FS#48601 - [libvirt] Allow libvirtd to start before network is up

Attached to Project: Community Packages
Opened by Kevin Zhao (Jesse2004) - Wednesday, 16 March 2016, 01:20 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 19 April 2016, 15:18 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Libvirtd starts very very slowly due to too many 'after='s in the service file.

# systemd-analyze critical-chain libvirtd.service

libvirtd.service @1min 30.942s
└─network.target @1min 30.812s
└─firewalld.service @3.302s +3.494s
└─polkit.service @20.104s +641ms
└─basic.target @2.591s
└─sockets.target @2.590s
└─virtlockd.socket @2.589s
└─sysinit.target @2.578s
└─sys-fs-fuse-connections.mount @20.192s +4ms
└─systemd-journald.socket @688ms
└─-.slice @553ms

Specifically, I shouldn't need my network connected to be able to use my virtual machines, right?

Additional info:
* package version: 1.3.2-3


Steps to reproduce:
This task depends upon

Closed by  Sergej Pupykin (sergej)
Tuesday, 19 April 2016, 15:18 GMT
Reason for closing:  Upstream
Comment by Doug Newgard (Scimmia) - Thursday, 17 March 2016, 04:04 GMT
The service file comes from upstream, you should probably talk to them. I'm guessing it's this way because the network needs to be up to provide networking to the guests.

Loading...