Il 16/06/2013 02:25, Stefan Pietsch ha scritto: > Bisecting leads to > > git bisect bad 378a8b099fc207ddcb91b19a8c1457667e0af398 > git bisect good 007a3b547512d69f67ceb9641796d64552bd337e > git bisect good 1f3141e80b149e7215313dff29e9a0c47811b1d1 > git bisect good 286da4156dc65c8a054580fdd96b7709132dce8d > git bisect bad 25391454e73e3156202264eb3c473825afe4bc94 > git bisect good 218e763f458c44f30041c1b48b4371e130fd4317 > > > first bad commit: [25391454e73e3156202264eb3c473825afe4bc94] > KVM: VMX: don't clobber segment AR of unusable segments. > > 25391454e73e3156202264eb3c473825afe4bc94 > emulate_invalid_guest_state=0 -> hangs and shows "KVM: entry failed" > emulate_invalid_guest_state=1 -> hangs > > Please note, I had to compile some revisions with > 3f0c3d0bb2bcc4b88b22452a7cf0073ee9a0f1e6 applied, caused by > 9ae9febae9500a0a6f5ce29ee4b8d942b5332529. Can you please execute "info registers" and "x/10i $pc" from the QEMU monitor at the time of the hang, and include the output? Using "-monitor stdio" or the new GTK+ interface can help. Also, can you run under tracing (for information on how to do this, see http://www.linux-kvm.org/page/Tracing) and include the bottom of the log? Thanks, Paolo -- 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
