kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Ruben Kerkhof <ruben@rubenkerkhof.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: EPT: Misconfiguration
Date: Tue, 25 Jan 2011 19:39:29 +0200	[thread overview]
Message-ID: <4D3F0AD1.9010903@redhat.com> (raw)
In-Reply-To: <AANLkTi=kMRu+4V6cc3bZtAT-L2P5cUo0QR3wNR3Y4u6B@mail.gmail.com>

On 01/25/2011 04:44 PM, Ruben Kerkhof wrote:
> Hi Marcello,
>
> On Fri, Jan 21, 2011 at 14:22, Marcelo Tosatti<mtosatti@redhat.com>  wrote:
> >  On Thu, Jan 20, 2011 at 12:48:00PM +0100, Ruben Kerkhof wrote:
> >>  I'm suddenly getting lots of the following errors on a server running
> >>  2.36.7, but I have no idea what it means:
> >>
> >>  2011-01-20T12:41:18.358603+01:00 phy005 kernel: EPT: Misconfiguration.
> >>  2011-01-20T12:41:18.358621+01:00 phy005 kernel: EPT: GPA: 0x3dbff6b0
> >>  2011-01-20T12:41:18.358624+01:00 phy005 kernel:
> >>  ept_misconfig_inspect_spte: spte 0x50743e007 level 4
> >>  2011-01-20T12:41:18.358627+01:00 phy005 kernel:
> >>  ept_misconfig_inspect_spte: spte 0x523de2007 level 3
> >>  2011-01-20T12:41:18.358629+01:00 phy005 kernel:
> >>  ept_misconfig_inspect_spte: spte 0x62336f007 level 2
> >>  2011-01-20T12:41:18.360109+01:00 phy005 kernel:
> >>  ept_misconfig_inspect_spte: spte 0x1603a0730500d277 level 1
> >>  2011-01-20T12:41:18.360137+01:00 phy005 kernel:
> >>  ept_misconfig_inspect_spte: rsvd_bits = 0x3a00000000000
> >>  2011-01-20T12:41:18.360151+01:00 phy005 kernel: ------------[ cut here
> >>  ]------------
> >
> >  A shadow pagetable entry in memory has bits 45-49 set, which is not
> >  allowed. Its probably bad memory if this errors were not present before
> >  with the same workload and host software. Would be useful to see what
> >  memtest86 says.
>
> I did 2 memtest86+ passes, but no errors were found.
>
> Just to be save, we replaced all memory. The machine has been running
> stable over the weekend, but now gives exactly the same error.
>
> Is there anything else which could cause this?

Try updating the BIOS.

When you say "suddenly", this was with no changes to software and hardware?

Is cooling adequate?

How much memory is on that machine?  Even outside the reserved bits the 
address looks way too large.

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


  reply	other threads:[~2011-01-25 17:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-20 11:48 EPT: Misconfiguration Ruben Kerkhof
2011-01-20 11:59 ` Ruben Kerkhof
2011-01-21 13:22 ` Marcelo Tosatti
2011-01-25 14:44   ` Ruben Kerkhof
2011-01-25 17:39     ` Avi Kivity [this message]
2011-01-25 18:29       ` Ruben Kerkhof
2011-01-26  9:52         ` Avi Kivity
2011-01-26 15:00           ` Ruben Kerkhof
2011-02-10 15:23             ` Ruben Kerkhof
2011-02-13  2:07               ` Ruben Kerkhof
2011-02-13 13:03                 ` Avi Kivity
2011-02-13 14:40                   ` Ruben Kerkhof
2011-02-15 17:16                   ` Marcelo Tosatti
2011-02-15 19:04                     ` Ruben Kerkhof
2011-02-24 21:15                       ` Ruben Kerkhof
2011-02-27 10:46                         ` Avi Kivity
2011-03-05 18:57                           ` Ruben Kerkhof
2011-02-13 12:58               ` Avi Kivity
2011-02-13 14:36                 ` Ruben Kerkhof

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=4D3F0AD1.9010903@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=ruben@rubenkerkhof.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;
as well as URLs for NNTP newsgroup(s).