Description of problem: https://fedoraproject.org/wiki/Features/SysVtoSystemd Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 511091 [details] Native systemd service file for libvirtd https://fedoraproject.org/wiki/Packaging:Guidelines:Systemd https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd http://fedoraproject.org/wiki/Packaging:Tmpfiles.d
Note that libvirt-guest sys legacy script requires some work to work with systemd You probably need to put the start/stop section from it into a script then call it from the unit file as in something like.. [Unit] Description=Suspend Active Libvirt Guests After=syslog.target network.target [Service] EnvironmentFile=-/sysconfig/libvirt-guests ExecStart=/path/to/libvirt-guests start ExecStop=/path/to/libvirt-guests stop [Install] WantedBy=multi-user.target
Posted a patch upstream http://www.redhat.com/archives/libvir-list/2011-July/msg00343.html
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Now upstream, for 0.9.8. commit 4789fb2e4e5bbb9132310a802a90f0ce85ec0016 Author: Daniel P. Berrange <berrange> AuthorDate: Thu Jul 7 14:45:07 2011 +0100 Commit: Daniel P. Berrange <berrange> CommitDate: Fri Nov 18 16:16:02 2011 +0000 Add support for systemd init service This patch adds support for a systemd init service for libvirtd and libvirt-guests. The libvirtd.service is *not* written to use socket activation, since we want libvirtd to start on boot so it can do guest auto-start. The libvirt-guests.service is pretty lame, just exec'ing the original init script for now. Ideally we would factor out the functionality, into some shared tool.