On Wed, Aug 19, 2015 at 2:33 PM, Serge Hallyn <1486...@bugs.launchpad.net> wrote:
> 1. when you say vivid vm and vivid container, do you mean a vivid vm > launched > inside a vivid container, regardless of the host? Or a vm - regardless > of > guest os - launched inside a vivid container running inside a vivid vm? > Wily host, launching Vivid cloud image, running a Vivid ubuntu-cloud template inside the Vivid VM Wily host, launching Wily cloud image, running a Wily ubuntu-cloud template inside the Wily VM uvt-simplestreams-libvirt --verbose sync release="~(vivid|wily)" arch=amd64 uvt-kvm create --developer --memory 1024 --cpu 2 --disk 10 --unsafe-caching v1 release=vivid arch=amd64 uvt-kvm create --developer --memory 1024 --cpu 2 --disk 10 --unsafe-caching w1 release=wily arch=amd64 get userdata.txt file from: http://paste.ubuntu.com/12130368/plain/ In each VM: scp userdate.txt $VM: sudo apt-get install libvirt-bin lxc sudo lxc-create -t ubuntu-cloud -n $release-v1 -- -u userdata.txt sudo lxc-start -n $release-v1 sudo lxc-attach -n $release-v1 sudo apt-get -y install libvirt-bin qemu-system-x86 uvtool ubuntu-cloud-keyring exit sudo lxc-ls --fancy # look for container ip ssh ubu...@10.0.3.xxx uvt-simplestreams-libvirt sync release=trusty arch=amd64 uvt-kvm create --disk 5 testme release=trusty arch=amd64 Vivid on Vivid, this will fail with uvt-kvm saying unknown libvirt error and an error in /var/log/libvirt/qemu/testme.log containing the handshake fail and error on input/output message. On Wily, this passes. > 2 Can you set cgmanager in the parent host/vm of the container to run with > --debug, then show the 'journalctl -u cgmanager' output? > Yes, I'll collect and update. I've also tested just upgrading cgmanager in VM/host only, and VM/host and container to wily levels (0.37) but that did not fix the issue in Vivid. > > 3 perhaps also set log_level=1 in /etc/libvirt/libvirtd.conf, restart > libvirt, > and show the journalctl -u libvirt-bin output. > We have this, but unfortunately to doesn't have anything useful w.r.t which calls in libvirt are failing. At best, we have syslog error when libvirtd attempts to write to cgroups on behalf of the VM and we get: Aug 18 20:18:59 openstack-single-ubuntu libvirtd[11203]: cgmanager: cgm_set for controller=devices, cgroup_path=machine/ubuntu-local-machine-1.libvirt-qemu failed: invalid request I'll collect this as well incase I missed something important. Ryan -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
