On 07/26/2012 02:58 PM, Chris Clayton wrote: >> It looks like general memory corruption. Is this repeatable? What's >> the guest uptime when it happens (i.e. is it immediate?) > > I've just done 10 runs of WinXP SP3 and 5 of them crashed. Three crashed > early as XP was starting up - well before the desktop would have > appeared. The other two crashed as XP was closing down, having been > running for a few minutes (but not doing much). > > The error messages seen through dmesg are: > > qemu-kvm[12778] general protection ip:b6c43d77 sp:b5e800fc error:0 in > libc-2.16.so[b6b06000+1b4000] > qemu-kvm[12813] general protection ip:b6bf6d77 sp:b54ff0fc error:0 in > libc-2.16.so[b6ab9000+1b4000] > qemu-kvm[12986] general protection ip:b6cd3d77 sp:b55ff0fc error:0 in > libc-2.16.so[b6b96000+1b4000] > qemu-kvm[13045] general protection ip:b6c91d77 sp:b54ff0fc error:0 in > libc-2.16.so[b6b54000+1b4000] > qemu-kvm[13225] general protection ip:b6c5bd77 sp:b54ff0fc error:0 in > libc-2.16.so[b6b1e000+1b4000] > > The other 5 were OK, although I only did a bit of web browsing for few > minutes with IE. Failures always in the same place (I'm guess the variations are due to PIE -- please configure with --disable-pie for future tests). Please generate a core and look around, esp. in frame 3 (type_table_lookup). Also try to dissect type_table (you may need to install the glib debug symbols for this). -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
