Michael Tokarev wrote: > On 29.05.2012 07:56, Wakko Warner wrote: > [] > > (process:14897): GLib-CRITICAL **: g_thread_pool_new: assertion > > `g_thread_supported ()' failed > > worker thread initialization failed > [] > > You know what, forget all of the above. My libglib version is 2.28.6-1. I > > extracted the library from libglib2.0-0_2.32.3-1_amd64.deb and ran: > > LD_LIBRARY_PATH=/junk/kvm/glib/lib/x86_64-linux-gnu > > /junk/kvm/qemu-kvm-1.0-11-debian/usr/bin/kvm -fsdev > > local,security_model=mapped,id=fsdev-fs0,path=/var -device > > virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=kernel,bus=pci.0,addr=0x3 -M > > pc-0.14 -nodefaults -vga std > > and it works fine. > > > > The fix for this bug might be to just depend on a newer version of > > libglib2.0-0. I upgraded this package on my system and qemu-kvm and > > everything is happy. > > Thank you Wakko, thank you very much for finding this. Trying > different glib version is something I'd do at the very end if > I had to debug this problem, so it is very unlikely I'd found > it even if I really tried... ;) And note I'd start with squeeze > version (see below) and that'd failed to reproduce the issue too :)
I'm using SID actually. After the compiles worked (I did 3. One I reverted the pci fix that went into -10, then the other 2 were no changes, just different gcc versions) I figured since both worked and the error thrown was a glib error, I figured I'd try a newer glib. > Now, it is actually interesting. libglib2.0-0 version in squeeze > is 2.24.2-1, and that version actually _works_. I don't have > 2.28.6-1 version around (I know about snapshot.d.o). It is even > more interesting that the problem only manifests itself when > using this -fsdev option. I keep the old packages that are removed from debian (2.7tb worth of source, amd64 and i386) incase something like this happens. If you would like, I can provide you with the version of glib that doesn't work. It is interesting. Most of my VMs use fsdev for the modules. That way, I have 1 copy of the modules, kernel, etc for all the VMs I have. I found that this was the cause because I have 2 test VMs that are net booting and don't use fsdev. The fsdev ones failed, the netboot started. > When qemu-kvm is compiled against current version of libglib2, > the dependency placed for the package is ">= 2.24.0" (this is > a manual dependency from soversions file in libglib package). > That file becomes out of date quite often, for many and especially > complex packages, since it is difficult to watch for the symbol > or behavour changes carefully. I can understand that. > The difference between -9 and -11 packages regarding glib is that > -9 were compiled against older libglib package (pre-2.32), while > when I compiled -11, some 2.32.x version were current. So this > sort of proves this theory, which becomes a mismatch between > more recent libglib headers or library and older runtme library > (which is all about that soversions file). Makes sense. > Hmm. > > I'll try to take a look at all this when I've some spare time > (as I already mentioned I'm quite busy currently). But at least, > can we downgrade the severity of the bug now, please? :) I know how the busy thing goes. I see no reason not to downgrade that. > And thank you very much, once again, for the great work you > did by finding the real cause, really, much apprecated! You're welcome. The only pain was trying to install the -dev packages for the libraries I had installed. -- Microsoft has beaten Volkswagen's world record. Volkswagen only created 22 million bugs. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
