On Fri, Feb 8, 2013 at 2:52 PM, Eric Blake <eblake@xxxxxxxxxx> wrote: > On 02/08/2013 01:46 PM, Dennis Jenkins wrote: >> On Fri, Feb 8, 2013 at 12:38 PM, Dennis Jenkins >> <dennis.jenkins.75@xxxxxxxxx> wrote: >>> Hello. >>> >>> tl;dr = v1.0.0 can boot my LXC containers, v.1.0.1 and v.1.0.2 fails. >>> Paraphrased error message: "lxcContainerMountProcFuse:616 : Failed to >>> mount ..../meminfo" >>> >>> I'd like to know if my host is misconfigured, or my domains, or >>> ... why 1.0.2 and 1.0.1 are not working for me. >> >> http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=ae9874e471fc61d9d654247c2fd24d9baa455afa >> >> It looks like I have been bitten by the above bug. >> >> What version of libvirt will these patches appear in? eg, is there a >> way to map a git commit to a future release? > > Commits in libvirt.git will appear in the next release, which we tend to > do about every 4-8 weeks. DV has already announced that 1.0.3 will > probably be out at the end of February: > > https://www.redhat.com/archives/libvir-list/2013-January/msg02076.html > > -- > Eric Blake eblake redhat com +1-919-301-3266 > Libvirt virtualization library http://libvirt.org > I don't believe that commit fixes the whole issue. I've unfortunately been insanely busy lately so I haven't been able to follow up but another Gentoo user reported the same issue and I already asked him to try the patch you mentioned. I was going to do my best to try and follow up soon with another idea but for reference the bug is here: https://bugs.gentoo.org/show_bug.cgi?id=451584 -- Doug Goldstein _______________________________________________ libvirt-users mailing list libvirt-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvirt-users
