Hi Adrian, On Fri, Nov 07, 2014 at 05:22:55PM +0000, Adrian Davey wrote: > > Hi, > > To further the bug report, I installed fedora 20, tried the container again, > it fails with not understanding how to deal with sys or proc mount points, > libvirt version was too low. I then updated the system to latest virt repo > which is the same version number as debian's 1.2.9. tried again, fails in > the same way as it does on debian, so thats good / bad news, at least we are > consistent! > > I have now installed a debian system at jessie level with kernel 3.14.2 > (from d-i usb install), got my test container working with idmap: good > result! > > Upgraded all packages to sid, container still starts: good result! > > Updated to linux-image-amd64 (brings in linux-image-3.16.0-4-amd64 == 3.16.7 > , no idea why the kernel team has changed their package names recently), > container fails to start. > > Looking back at the fedora installation, it too is a 3.16 kernel. I am > rather surprised the fedora folks haven't noticed, I doubt fedora 21 will > work with idmap libvirt_lxc either. > > I posted on libvir mailing list [1] about possible issues with kernel / > libvirt needing to be synced for mounting proc, but nobody replied. > > So in conclusion, seems the kernel did break somewhere after 3.14.2. I will > try later kernels but fishing in the dark as to where to look for the > relevant changes, git bisect is a little beyond me.
Thanks for investigating! That would explain why it works with the 3.16-rc6 I'm currently running. > > Do I open a bug with the kernel or should this bug just be re-assigned ? I'd reassign and add an affects <bugnumber> libvirt-daemon-system so it also shows up in libvirt's bugs. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
