On Fri, 2009-10-30 at 09:10 +0100, Chris Lalancette wrote: > Can either you or Danny: > > 1) Get the output from stderr of qemu when this happens? I believe qemu dumps > the state of all of the guest fields when it's going to crash like this, and > that can tell us if the GUEST_STATE is wrong. <blush> Any pointer how to produce/where to find the dump ? </blush> > 2) Try the patch posted here: http://lkml.org/lkml/2009/10/28/201, and see if > it helps? > [oneliner patch manually applied] vhost1:/usr/src/linux-2.6.32-rc5-git4# time make-kpkg kernel-image --initrd [SNIP] dpkg-deb: building package `linux-image-2.6.32-rc5-git4' in `../linux-image-2.6.32-rc5-git4_2.6.32-rc5-git4-10.00.Custom_amd64.deb'. make[2]: Leaving directory `/usr/src/linux-2.6.32-rc5-git4' make[1]: Leaving directory `/usr/src/linux-2.6.32-rc5-git4' real 4m50.866s user 30m3.549s sys 2m41.270s [REBOOT] vhost1:~# kvm -m 512 -cdrom /vz/template/iso/debian-503-amd64-netinst.iso -cpu pentium3 Segmentation fault vhost1:~# dmesg| tail handle_exception: unexpected, vectoring info 0x8000000d intr info 0x80000b0d handle_exception: unexpected, vectoring info 0x8000000d intr info 0x80000b0d handle_exception: unexpected, vectoring info 0x8000000d intr info 0x80000b0d handle_exception: unexpected, vectoring info 0x8000000d intr info 0x80000b0d handle_exception: unexpected, vectoring info 0x8000000d intr info 0x80000b0d handle_exception: unexpected, vectoring info 0x8000000d intr info 0x80000b0d handle_exception: unexpected, vectoring info 0x8000000d intr info 0x80000b0d handle_exception: unexpected, vectoring info 0x8000000d intr info 0x80000b0d vmx_handle_exit: unexpected, valid vectoring info (0x8000000d) and exit reason is 0x80000021 kvm[5138]: segfault at c ip 00000000004674ac sp 0000000041cebfd0 error 4 in kvm[400000+21b000] In my case it doesn't seem to help. I straced the process in case that should provide some more help: http://dth.net/supermicro/strace_2.6.32-rc5-git4_p3_cpu Thanks for the feedback! -- 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
