4c396d23a6
For awhile, libvirt has moved away from the monolithic libvirtd in favor
of modular virt${DRIVER}d daemons that each manage a specific function.
This is the default behavior for per-user "session" instances that
launch on demand. We still provide a legacy libvirtd service, but let's
add services for the modular daemons favored by upstream.
|
||
|---|---|---|
| .. | ||
| files | ||
| patches | ||
| template | ||