Re: [libvirt-users] libvirt-1.2.2-r1 (Gentoo) fails to start LXC containers

On 09/11/2013 04:44 PM, Daniel P. Berrange wrote: > On Tue, Sep 10, 2013 at 09:09:44AM -0500, Dennis Jenkins wrote: >> I recently upgraded "libvirt" on Gentoo to 1.2.2-r1 (latest available). I >> have not used LXC containers for a few weeks, so I don't recall what >> version of libvirt I was using when my container last booted successfully. >> >> ostara ~ # tail /var/log/libvirt/lxc/dwj-hfax-dev.log >> 2013-09-10 13:56:22.767+0000: starting up >> PATH=/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.6.3:/usr/x86_64-pc-linux-gnu/i686-pc-mingw32/gcc-bin/4.7.3 >> LIBVIRT_DEBUG=3 LIBVIRT_LOG_OUTPUTS=3:file:/var/log/libvirt/libvirtd.log >> /usr/libexec/libvirt_lxc --name dwj-hfax-dev --console 20 --security=none >> --handshake 23 --background --veth veth1 >> PATH=/bin:/sbin TERM=linux container=lxc-libvirt >> container_uuid=681410de-7b56-41bd-b38d-3c66ce97e7b3 >> LIBVIRT_LXC_UUID=681410de-7b56-41bd-b38d-3c66ce97e7b3 >> LIBVIRT_LXC_NAME=dwj-hfax-dev /sbin/init >> error receiving signal from container: Input/output error > > We'll need you to increase the log level to get more detail in this > file. > > 1. Stop the 'libvirtd' daemon > > 2. Edit /etc/libvirt/lxc.conf and set log_with_libvirtd=1 > > 3. Run > > $ LIBVIRT_LOG_FILTERS=1:lxc LIBVIRT_LOG_OUTPUTS=1:stderr /usr/sbin/libvirtd > > 4. rm -f /var/log/libvirt/lxc/dwj-hfax-dev.log > > 5. Try to start your guest with virsh > > > Now send us the much more verbose logfile that was created Dennis has already knew what's wrong with his environment, his kernel doesn't support securityfs. libvirt should handle this problem.