On 17.05.2009, at 22:00, Avi Kivity <avi@xxxxxxxxxx> wrote:
Alexander Graf wrote:
case MSR_VM_CR:
+ case 0x40000081:
*data = 0;
break;
This probably is a Hyper-V MSR, but I don't see how it expects it
to be present in real hardware. Are you sure this is really needed?
Well hyper-v just crashes/reboots if it get a #gp on that msr, so I
suppose yes.
This is suspicious. It won't get this MSR on real hardware.
Maybe this was with cpuid.hypervisor enabled?
Before I sent out this patch I rechecked if the 0x4 msr is really
required because it seemed awkward to me too and it did, but I can
recheck for a 3rd time :)
Alex
--
Do not meddle in the internals of kernels, for they are subtle and
quick to panic.
--
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
