2015-06-18 17:29+0200, Paolo Bonzini: > On 18/06/2015 17:24, Radim Krčmář wrote: > > W10 insider has a bug where it ignores CPUID level and interprets > > CPUID.(EAX=07H, ECX=0H) incorrectly, because CPUID in fact returned > > CPUID.(EAX=04H, ECX=0H); this resulted in execution of unsupported > > instructions. > > > > While it's a Windows bug, there is no reason to emulate incorrect level; > > and amend xlevel while at it. > > > > I have used http://instlatx64.atw.hu/ as a source of CPUID and checked > > that it matches Penryn Xeon X5472, Westmere Xeon W3520, SandyBridge > > i5-2540M, and Haswell i5-4670T. > > > > kvm64 and qemu64 were bumped to 0xD to avoid similar problems. > > This unfortunately has to be done only for new machine types. Old types > will remain buggy forever.
Ah, ok, which machine type should I target, 2.4? And is patch 2 is only supposed to work with new machine types? Thanks.
