On standalone, the VMs are not started/shutdown with pacemaker, so we need to use the autostart feature of libvirtd. It seems that this "virsh list" as ExecStartPost makes libvirtd choke on autostart.
This "virsh list" was there to make sure libvirtd is properly started before we start pacemaker.
This commits moves this check as an ExecStartPre of pacemaker, so that it does not meddle with libvirtd startup.
On standalone, the VMs are not started/shutdown with pacemaker, so we need to use the autostart feature of libvirtd. It seems that this "virsh list" as ExecStartPost makes libvirtd choke on autostart. This "virsh list" was there to make sure libvirtd is properly started before we start pacemaker.
This commits moves this check as an ExecStartPre of pacemaker, so that it does not meddle with libvirtd startup.
This will solves #613.