crosvm: kernel complains about unhandled rdmsr |
||
Issue descriptionBoot a VM on eve ToT and check dmesg: <4>[ 6024.640618] kvm_get_msr_common: 6 callbacks suppressed <3>[ 6024.640623] kvm [15246]: vcpu0 unhandled rdmsr: 0x140 <3>[ 6024.857028] kvm [15246]: vcpu0 unhandled rdmsr: 0x1c9 <3>[ 6024.857036] kvm [15246]: vcpu0 unhandled rdmsr: 0x1a6 <3>[ 6024.857039] kvm [15246]: vcpu0 unhandled rdmsr: 0x1a7 <3>[ 6024.857041] kvm [15246]: vcpu0 unhandled rdmsr: 0x3f6 <3>[ 6024.857044] kvm [15246]: vcpu0 unhandled rdmsr: 0x3f7 <3>[ 6024.881296] kvm [15246]: vcpu1 unhandled rdmsr: 0x140 <3>[ 6024.892482] kvm [15246]: vcpu2 unhandled rdmsr: 0x140 <3>[ 6024.902516] kvm [15246]: vcpu3 unhandled rdmsr: 0x140 <3>[ 6025.155139] kvm [15246]: vcpu0 unhandled rdmsr: 0x64e
,
Aug 2
The messages are benign, the guest kernel is trying to figure out/validate processor capabilities, KVM returns GP fault, guest handles it as missing MSR, all is good. Is the request to suppress the messages (kernel change) or to actually attempt to implement these MSRs (and if so why)? I am tempted to simply leave it alone.
,
Aug 2
If they are benign, then I'm fine leaving them as is.
,
Aug 3
|
||
►
Sign in to add a comment |
||
Comment 1 by dgreid@chromium.org
, Aug 2Owner: dtor@chromium.org
Status: Assigned (was: Untriaged)