Radim Krčmář <rkrcmar@xxxxxxxxxx> writes: > 2015-03-26 21:24+0300, Andrey Korolyov: >> On Thu, Mar 26, 2015 at 8:40 PM, Radim Krčmář <rkrcmar@xxxxxxxxxx> wrote: >> > 2015-03-26 20:08+0300, Andrey Korolyov: >> >> KVM internal error. Suberror: 2 >> >> extra data[0]: 800000ef >> >> extra data[1]: 80000b0d >> > >> > Btw. does this part ever change? >> > >> > I see that first report had: >> > >> > KVM internal error. Suberror: 2 >> > extra data[0]: 800000d1 >> > extra data[1]: 80000b0d >> > >> > Was that a Windows guest by any chance? >> >> Yes, exactly, different extra data output was from a Windows VMs. > > Windows uses vector 0xd1 for timer interrupts. > I second Bandan -- checking that it reproduces on other machine would be > great for sanity :) (Although a bug in our APICv is far more likely.) If it's APICv related, a run without apicv enabled could give more hints. Your "devices not getting reset" hypothesis makes the most sense to me, maybe the timer vector in the error message is just one part of the whole story. Another misbehaving interrupt from the dark comes in at the same time and leads to a double fault. -- 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
