Jonathan Gray <jsg <at> jsg.id.au> writes: > > So what is the point for guest to run erratas if hypervisor > > may already done that upwards? > > Filling the kernel full of if not really running on hardware > do something else paths is asking for trouble. If a hypervisor > claims to be a specific model of a processor it should not be > surprised when it gets msrs that processor can handle.
Have you noticed kernel: protection fault trap, code=0 Stopped in pid 0.1 (system) at netbsd:rdmsr_locked+0xb: rdmsr in original NetBSD PR? Is there a possibility to tell if MSR access in locked or not without receiving a protection fault trap?
