Avi Kivity wrote:
Well, there was a regression, but it was in 0.12.1.1.
There were two bugs involved, a serious one (that caused the cpuid to
show up as AMD) hiding the less serious one (that causes processor.sys
to BSOD).
Okay, understood. I must have just got lucky when upgrading from older
KVM to 0.12.1.1.
I'd like to find out why processor.sys fails, but the .1->.2 change
isn't any help unfortunately. It looks like here too there are two bugs
involved: one in kvm which doesn't act like processor.sys expects it,
and one in processor.sys which causes it to
UNLOAD_ITSELF_WITHOUT_CANCELLING_PENDING_OPERATIONS. You might try
running with kvm trace enabled and look at msr and cpuid accesses just
prior to the crash.
I've had a quick look at this, and I can't work out how to enable kvm
trace in Kconfig. Is there any documentation on how to build with kvm
trace enabled for debugging?
ATB,
Mark.
--
Mark Cave-Ayland - Senior Technical Architect
PostgreSQL - PostGIS
Sirius Corporation plc - control through freedom
http://www.siriusit.co.uk
t: +44 870 608 0063
Sirius Labs: http://www.siriusit.co.uk/labs
--
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
