On 10/07/2016 09:31 AM, Andrea Bolognani wrote:
On Fri, 2016-10-07 at 09:12 +0200, Boris Fiuczynski wrote:
Daniel, Andrea, have you looked into the change in behaviour caused by patch 4 of this series? When libvirtd is stopped I get all my running domains suspended. Restarting libvirtd now also causes a disruption since all domains are suspended and than resumed. Before the commit of this patch the domains used to remain running without these disruptions and as a user this is what I expect to happen. I propose to revert commit fb2025ede9ecde1aa04ba6e01ce0c82c9e42dc66.
Oh, you're right! Thank you for reporting this issue.
We don't want to revert the change though, merely to downgrade the Requires to a Wants.
That way, libvirtd stopping (or restarting) will not cause libvirt-guests to stop, but when starting libvirt-guests an attempt will still be made to start up libvirtd if it's not running already.
I'll have patches on the list shortly.
-- Andrea Bolognani / Red Hat / Virtualization
Andrea, there is another "side effect" of the Requires directive. libvirt-guests gets automatically started when libvirt is updated to v2.3.0. This has some rather nasty implications for the end users. -- Mit freundlichen Grüßen/Kind regards Boris Fiuczynski IBM Deutschland Research & Development GmbH Vorsitzender des Aufsichtsrats: Martina Köderitz Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen Registergericht: Amtsgericht Stuttgart, HRB 243294