From: Theodore Tso <tytso@mit.edu>
To: Avi Kivity <avi@redhat.com>
Cc: linux-kernel@vger.kernel.org, KVM list <kvm@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: Problems with CONFIG_KVM_GUEST?
Date: Sun, 2 Aug 2009 15:14:39 -0400 [thread overview]
Message-ID: <20090802191439.GE15828@mit.edu> (raw)
In-Reply-To: <4A75B56D.5070407@redhat.com>
On Sun, Aug 02, 2009 at 06:49:01PM +0300, Avi Kivity wrote:
>
> What's the host kernel version?
>
> We had problems with CONFIG_KVM_GUEST and PAE which were resolved in
> 2.6.30-final but perhaps failed to trickle down to whatever you're
> using. The upstream commit is a8cd0244 ("KVM: Make paravirt tlb flush
> also reload the PAE PDPTRs").
Commit ID 63f7a33, which is post 2.6.31-rc3. I run bleeding edge
kernels. :-)
I can try building a 2.6.30-final kernel and testing that as the
host if you think it might be a 2.6.31-rc regression.
- Ted
prev parent reply other threads:[~2009-08-02 19:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-01 21:26 Problems with CONFIG_KVM_GUEST? Theodore Tso
2009-08-02 9:38 ` Avi Kivity
2009-08-02 15:32 ` Theodore Tso
2009-08-02 15:49 ` Avi Kivity
2009-08-02 19:14 ` Theodore Tso [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=20090802191439.GE15828@mit.edu \
--to=tytso@mit.edu \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
/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