Bug 35132
Summary: | 2.6.39-rc7 Oopses when booting with kvm -cpu phenom -smp 2 | ||
---|---|---|---|
Product: | Platform Specific/Hardware | Reporter: | Török Edwin (edwin+bugs) |
Component: | x86-64 | Assignee: | platform_x86_64 (platform_x86_64) |
Status: | CLOSED CODE_FIX | ||
Severity: | normal | CC: | florian, hpa, maciej.rutecki, rjw |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.39-rc7 | Subsystem: | |
Regression: | Yes | Bisected commit-id: | |
Bug Depends on: | |||
Bug Blocks: | 32012 |
Description
Török Edwin
2011-05-15 14:05:22 UTC
Host kernel says: [23723.632616] kvm: 23803: cpu3 unhandled rdmsr: 0xc0010048 [23723.632620] kvm: 23803: cpu3 unhandled wrmsr: 0xc0010048 data fff00000401 Looks like KVM doesn't support that MSR, and that KVM will cause a GP fault in the guest if it tries to write to unknown MSR: if (svm_set_msr(&svm->vcpu, ecx, data)) { trace_kvm_msr_write_ex(ecx, data); kvm_inject_gp(&svm->vcpu, 0); I think that either KVM should be taught about that MSR, or the code writing to it should check whether running under KVM (what about Xen/VMware/etc.?), and don't write if so. First-Bad-Commit : 5bbc097d890409d8eff4e3f1d26f11a9d6b7c07e A patch referencing this bug report has been merged in v3.0-rc1: commit d47cc0db8fd6011de2248df505fc34990b7451bf Author: Roedel, Joerg <Joerg.Roedel@amd.com> Date: Thu May 19 11:13:39 2011 +0200 x86, amd: Use _safe() msr access for GartTlbWlk disable code Confirmed the fix. |