23.05.2011 15:30, Daniel Bareiro wrpte: > This is the output without daemonizing: > > > *** glibc detected *** kvm: free(): invalid next size (fast): 0x09fad3c0 *** [...] > Can we confirm that it is the same problem? If you need to do another > test, please don't hesitate to ask me.
Yes it's exactly this problem, you can check the other bug I mentioned - it shows this very memory corruption too. That's why I merged the two. > As I noted earlier, trying to migrate from Defiant (Debian GNU/Linux > 5.0.8 with Linux 2.6.32-15~bpo50+1 and qemu-kvm 0.12.5+dfsg-3~bpo50+2) > to SS01, this problem does not occur. Both installation are 32-bit, > but the kernel in SS01 is amd64 and the kernel in Defiant is i686. > > Ie both are 32bit userspace with the difference that ss01 has a 64-bit > kernel. The problem is there? Because versions of Linux and qemu-kvm > look the same. This bug has 2 halves, one half is general 32bit migration issue (it does not actually work on 32bits, the fact it worked for you is pure luck), and second half is special case of 32bit userspace running on 64bit kernel (due to wrong kernel/user space communications). Both will be fixed in the upcoming squeeze version of qemu-kvm. You can try patching and rebuilding your qemu-kvm using patches in the package waiting upload. Unfortunately right now the anonscm.debian.org service (with http access to the git repository) does not work due to system maintenance. It's in git://git.debian.org/collab-maint/qemu-kvm.git, I extracted the patch into my site here: http://www.corpit.ru/mjt/tmp/fix-crash-in-migration-32-bit-51b0c6065a.diff This patch fixes both halves of the problem. /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
