On Wed, Jun 19, 2013 at 04:12:04PM +0200, Stefan Pietsch wrote: > On 19.06.2013 15:41, Gleb Natapov wrote: > > On Sun, Jun 16, 2013 at 02:25:04AM +0200, Stefan Pietsch wrote: > >> > >> 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 > >> > > With emulate_invalid_guest_state=1 the commit does nothing. Can you > > double check that 218e763f458c44f30041c1b48b4371e130fd4317 works for you > > with emulate_invalid_guest_state=1? > > > 218e763f458c44f30041c1b48b4371e130fd4317 > emulate_invalid_guest_state=0 -> works > emulate_invalid_guest_state=1 -> hangs > > 25391454e73e3156202264eb3c473825afe4bc94 broke > emulate_invalid_guest_state=0. Can you provide the output of 25391454e73e3156202264eb3c473825afe4bc94 and emulate_invalid_guest_state=0. Also run "x/20i $pc-20" in qemu monitor after the hang. -- Gleb. -- 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
