From: Avi Kivity <avi@qumranet.com>
To: duck@sophos.com
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: Out-of-box kvm-61 driver crash, first kvm problem ever, boo hoo...
Date: Wed, 20 Feb 2008 11:42:12 +0200 [thread overview]
Message-ID: <47BBF5F4.7050207@qumranet.com> (raw)
In-Reply-To: <47BBF1D3.2020701@qumranet.com>
[-- Attachment #1: Type: text/plain, Size: 513 bytes --]
Avi Kivity wrote:
> duck@sophos.com wrote:
>> EIP: [<f8b8dcd2>] vmx_set_efer+0xa2/0xb0 [kvm_intel] SS:ESP
>> 0068:f4a63ed4
>>
>>
>
> Not completely unexpected. You are running a Core (not 2) processor
> which doesn't support nx or x86_64, so it doesn't have the EFER
> register. kvm-61 adds support for the EFER on i386, but apparently
> doesn't handle those old cpus well.
>
> I'll try to get a patch for you to test.
>
Attached.
--
Any sufficiently difficult bug is indistinguishable from a feature.
[-- Attachment #2: no-efer-on-old-core.patch --]
[-- Type: text/x-patch, Size: 411 bytes --]
diff --git a/kernel/vmx.c b/kernel/vmx.c
index e75b2f5..a575e54 100644
--- a/kernel/vmx.c
+++ b/kernel/vmx.c
@@ -1342,6 +1342,8 @@ static void vmx_set_efer(struct kvm_vcpu *vcpu, u64 efer)
struct kvm_msr_entry *msr = find_msr_entry(vmx, MSR_EFER);
vcpu->arch.shadow_efer = efer;
+ if (!msr)
+ return;
if (efer & EFER_LMA) {
vmcs_write32(VM_ENTRY_CONTROLS,
vmcs_read32(VM_ENTRY_CONTROLS) |
[-- Attachment #3: Type: text/plain, Size: 228 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
[-- Attachment #4: Type: text/plain, Size: 158 bytes --]
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
prev parent reply other threads:[~2008-02-20 9:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 7:45 Out-of-box kvm-61 driver crash, first kvm problem ever, boo hoo duck
2008-02-20 9:24 ` Avi Kivity
2008-02-20 9:42 ` Avi Kivity [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47BBF5F4.7050207@qumranet.com \
--to=avi@qumranet.com \
--cc=duck@sophos.com \
--cc=kvm-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.