On Wed, Feb 12, 2014 at 09:20:24AM +0100, Stefan Bader wrote: > On 11.02.2014 20:45, Peter Zijlstra wrote: > > On Tue, Feb 11, 2014 at 07:34:51PM +0100, Stefan Bader wrote: > >> Hi Peter, > >> > >> I am currently looking at a weird issue that manifest itself when trying to run > >> kvm enabled qemu on a i386 host (v3.13 kernel, oh and potentially important the > >> cpu is 64bit capable, so qemu-system-x86_64 is called). > > > > AMD or Intel machine? > > Personally I am reproducing this on an AMD: > > cpu family : 15 > model : 72 > model name : AMD Turion(tm) 64 X2 Mobile Technology TL-64 > > but the reports I got are showing the same issue on an Intel i7 > > cpu family : 6 > model : 37 > model name : Intel(R) Core(TM) i7 CPU M 620 @ 2.67GH > > Another reporter also saw this on an AMD and said it could not be reproduced on > the same hardware and the same software versions when using 64bit instead of 32. > > In my case on a 32bit installation I will see this on every invocation of Curious.. so its both AMD and Intel. That makes funny hardware less likely... but how can the vmexit loose an interrupt like this. -- 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
