** Description changed: + ==================================================== + 1. Impact: cannot start vms inside a container + 2. Devel solution: drop the cgmanager patches + 3. Stable solution: same as devel solution + 4. Test case: see comment #7 below for a very detailed and easy to use example + 5. Regression potential: There should be no regressions, and the lp:qa-regression-tests passed. + ==================================================== + Our installer attempts to load VM's within an lxc container. This worked on trusty, however, with the latest releases from vivid and wily those VM's are unable to start. This affects running juju-local within a container as well. We think it has something to do with cgmanager/cgproxy, however, we can manually run and launch qemu just fine within the container. This could potentially be an issue with libvirt attempt to set cgroup values for the qemu processes. The current workaround to get a VM to start within a vivid and wily container running LXC 1.1.2+ is to disable cgroups in /etc/libvirt/qemu.conf I'm starting this bug and will ask Ryan Harper to provide a more in- depth result of his debugging, but, wanted to have this on the radar. Specs: Host: Vivid, kernel: 3.19.0-15-generic, lxc: 1.1.3+stable~20150815-0227-0ubuntu1~vivid Container: Vivid, kernel: 3.19.0-15-generic, lxc: 1.1.2-0ubuntu3.1, libvirt 1.2.12-0ubuntu14.1
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1486296 Title: Unable to start VMs under a lxc container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1486296/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
