libvirt started after cgred - cgroup not working correctly

[edison]

I enabled cgroup for libvirt by:
Create a new virt group, by adding
group virt {
        cpu {
                cpu.shares = 9216;
        }
}
into /etc/cgconfig.conf. And add "root:/usr/sbin/libvirtd cpu virt/" into /etc/cgrules.conf
So, when I start libvirt-bin, libvirtd will create its own cgroup directory under /mnt/cgroup/cpu/virt/

Everything works well, except after reboot the machine.
I found libvirt doesn't create its own cgroup under /mnt/cgroup/cpu, or /mnt/cgroup/sysdefault, instead of /mnt/cgroup/cpu/virt
After some tests, the root cause is libvirtd is started earlier than cgred.
On lucid, libvirt-bin is started by upstart, while cgred is started by sys-V init script. How can I specify the dependency between the two? Apparently, libvirt-bin should be started after cgred.
Right now, I add the following hack in /etc/init/libvirt-bin.conf:
pre-start script
        mkdir -p /var/run/libvirt
        # Clean up a pidfile that might be left around
        rm -f /var/run/libvirtd.pid
        while [ 1 ]
        do
            if [ -f /var/run/cgred.pid ]
            then
                break
            else
                sleep 1
            fi
        done
end script
Then libvirt works with cgroup again.

[Rudd-O (rudd-o)]

I also need this bug fixed. If cgred is on the system, then libvirt should start *after* it.

[Serge Hallyn (serge-hallyn)]

Rudd-O, can you use the same workaround listed in the
description?

This should be fixed by converting the libcgroup package to use
upstart. Can you file a bug against the libcgroup package to
do so?

[The Loeki (the-loeki)]

For me, the workaround works.

The related bug has already been filed under #644669

[Serge Hallyn (serge-hallyn)]

Thanks for pointing that out. I'm not sure what I was originally thinking (why I needed a separate bug rather than marking this as affecting both).

[Serge Hallyn (serge-hallyn)]

Marked this invalid since the fix will come in libcgroup (in bug 644669).