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:24:35 +0200 [thread overview]
Message-ID: <47BBF1D3.2020701@qumranet.com> (raw)
In-Reply-To: <OF0AD5B184.FAA44B4B-ONCA2573F5.00281FE6-CA2573F5.002AA4F2@sophos.com>
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.
--
Any sufficiently difficult bug is indistinguishable from a feature.
-------------------------------------------------------------------------
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/
next prev parent reply other threads:[~2008-02-20 9:24 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 [this message]
2008-02-20 9:42 ` Avi Kivity
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=47BBF1D3.2020701@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox