On Mon, Mar 05, 2012, Serge Hallyn wrote:
> This is should be independent of the libvirt-cgconfig-wait job. That
> doesn't actually explicitly start libvirt-bin. Are you on precise?
Yes, I'm on precise
> Note that really libcgroup and libvirt do not work together anyway, due
> to a race at startup. We recommend cgroup-lite (which is in main) be
> used in its place.
>
> But libvirt starting after upgrades, when you have start_libvirt="no, is
> puzzling.
Right now the daemon is running, but the main issue is that the upgrade
itself is stuck at starting libvirt-bin when the package's postinst
run, and I don't understand why.
I'll switch to cgroup-lite and see if that helps, still worth merging
the proposed shell syntax fix if that's ok with you -- but I'm happy to
upload it if you +1 it
On Mon, Mar 05, 2012, Serge Hallyn wrote: cgconfig- wait job. That
> This is should be independent of the libvirt-
> doesn't actually explicitly start libvirt-bin. Are you on precise?
Yes, I'm on precise
> Note that really libcgroup and libvirt do not work together anyway, due
> to a race at startup. We recommend cgroup-lite (which is in main) be
> used in its place.
>
> But libvirt starting after upgrades, when you have start_libvirt="no, is
> puzzling.
Right now the daemon is running, but the main issue is that the upgrade
itself is stuck at starting libvirt-bin when the package's postinst
run, and I don't understand why.
I'll switch to cgroup-lite and see if that helps, still worth merging
the proposed shell syntax fix if that's ok with you -- but I'm happy to
upload it if you +1 it
--
Loïc Minier