xendomains will manage guests behind libvirts back: - libvirt starts a guest - that guest can be "managed" by libvirt and xl at the same time - when xendomains runs on shutdown it will save the guest using xl libvirt does not know about this - when xendomains runs on boot it will restore the saved guest using xl libvirt does not know about this, it will just fail to manage the restored guest
To prevent xendomains from interfering with libvirt add a Conflicts= to xendomains.service. It will cause libvirt to be stopped if xendomains is started manually with 'systemctl start' 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> Cc: Wei Liu <wei.l...@citrix.com> --- v2: correct typo, it has to be libvirtd.service tools/hotplug/Linux/systemd/xendomains.service.in | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/hotplug/Linux/systemd/xendomains.service.in b/tools/hotplug/Linux/systemd/xendomains.service.in index 66e2065..c7bfb61 100644 --- a/tools/hotplug/Linux/systemd/xendomains.service.in +++ b/tools/hotplug/Linux/systemd/xendomains.service.in @@ -5,6 +5,7 @@ After=proc-xen.mount xenstored.service xenconsoled.service xen-init-dom0.service After=network-online.target After=remote-fs.target ConditionPathExists=/proc/xen/capabilities +Conflicts=libvirtd.service [Service] Type=oneshot _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
