All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Theodore Tso <tytso@mit.edu>,
	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, 02 Aug 2009 18:49:01 +0300	[thread overview]
Message-ID: <4A75B56D.5070407@redhat.com> (raw)
In-Reply-To: <20090802153238.GC15828@mit.edu>

On 08/02/2009 06:32 PM, Theodore Tso wrote:
> On Sun, Aug 02, 2009 at 12:38:59PM +0300, Avi Kivity wrote:
>    
>> (Adding ccs)
>>
>> On 08/02/2009 12:26 AM, Theodore Tso wrote:
>>      
>>> Using the XFS QA regression test suites to test ext4, I reliably get
>>> lock-ups and OOPS's with I run a kernel using KVM with
>>> CONFIG_KVM_GUEST configured.  This is with 2.6.31-rc3 and 2.6.31-rc4.
>>>
>>> The problems disappear if I turn off CONFIG_KVM_GUEST; the XFS tests
>>> run without problem to completion once I turn this configuration
>>> option off.  That's what I'll do for now, but if someone could look
>>> into this, I'd appreciate it.
>>>
>>>        
>> Is this a PAE mode guest?
>>      
>
> Yes, it is.  Here's the config (with CONFIG_KVM_GUEST turned off, but
> otherwise what I had testing with).
>
>    

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").

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2009-08-02 15:44 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 [this message]
2009-08-02 19:14       ` Theodore Tso

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=4A75B56D.5070407@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=tytso@mit.edu \
    /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.