Bug#848317: [Pkg-libvirt-maintainers] Bug#848317: not arch dependent but racy

Hmm, just applying did not fix it for me. Needs more debugging on the different group setup on Debian/Ubuntu in relation to the issue and the upstream fix I'll come back once I have any new insight to this, but it is at a lower prio for me now. Do we have a "deferred" bug state or anything like

Bug#848317: [Pkg-libvirt-maintainers] Bug#848317: not arch dependent but racy

FYI - that http://www.spinics.net/linux/fedora/libvir/msg141665.html pretty much looks like it. ​I'll need to experiment with that applied but wanted to mention it here.

Bug#848317: [Pkg-libvirt-maintainers] Bug#848317: not arch dependent but racy

For the long term solution given that I can't find the root cause I reported it upstream to libvirt list but kept you on cc there. Please note that I even reproduced back to libvirt 1.3.1 so I doubt it is a regression, but more likely never worked.

Bug#848317: [Pkg-libvirt-maintainers] Bug#848317: not arch dependent but racy

I agree that it eventually has to be resolved and fixed upstream, but at least I seem to be unable to find the spot in this haystack of cgroup things. So until this bug is properly resolved I'd ask to skip this particular part of the smoke test. BTW - the isolation level requirement I mentioned

Bug#848317: [Pkg-libvirt-maintainers] Bug#848317: not arch dependent but racy

I tested the sequence I listed before with: - current sid libvirt 2.4.0-3 - current experimental libvirt 2.5.0-1 Both hit just the same issue just as much as my Ubuntu environments did - so did the upgrade from 2.4.0-3 to 2.5.0-1 does as well. To be clear, I certainly get to a point where the

Bug#848317: [Pkg-libvirt-maintainers] Bug#848317: not arch dependent but racy

On Mon, Dec 19, 2016 at 6:37 PM, Guido Günther wrote: > Great. Now that you found a way to reproduce it should be possible to > cook a patch for upstream that fixes this! > While I'd love to do so, a morning of failed debugging cut that approach at least for now. I'll share

Bug#848317: [Pkg-libvirt-maintainers] Bug#848317: not arch dependent but racy

I was setting up a VM independent of autopkgtests to debug this further, but so far only confirmed what I had already: Yet as documentation if we later on need to refer to that data: Logs of journalctl -fex and the libvirt log on sl guest when doing the killing restart # Before: $ virsh list

Bug#848317: [Pkg-libvirt-maintainers] Bug#848317: not arch dependent but racy

Summary of minimal steps to reproduce: 1. Spawn new KVM Guest of your choice 2. install test dependencies $ apt-get install libvirt-daemon-system libvirt-clients libxml2-utils 3. run the following sequence as root export LIBVIRT_DEFAULT_URI=lxc:/// cat << EOF > /tmp/smoke-lxc.xml sl 256000

Bug#848317: [Pkg-libvirt-maintainers] Bug#848317: not arch dependent but racy

Hi, On Mon, Dec 19, 2016 at 02:59:04PM +0100, Christian Ehrhardt wrote: > Hi, > I think we can forget my former suggestion for isolation at least for now. > Thanks for closing 848319 btw that explanation gave me the confidence to > continue debugging this case. > > Now I found that I seem to be