From: Ruben Kerkhof <ruben@rubenkerkhof.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Avi Kivity <avi@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: EPT: Misconfiguration
Date: Thu, 24 Feb 2011 22:15:01 +0100 [thread overview]
Message-ID: <AANLkTiknMneQtYqgmX7gvXsMoSO-yiLXr-dwbEej80Uy@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimeFf2Smj=bWDYoH0Hf+ftnbW3XjacyS2pu49_o@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2145 bytes --]
Hi Marcelo,
On Tue, Feb 15, 2011 at 20:04, Ruben Kerkhof <ruben@rubenkerkhof.com> wrote:
> Hi Marcelo,
>
> On Tue, Feb 15, 2011 at 18:16, Marcelo Tosatti <mtosatti@redhat.com> wrote:
>> On Sun, Feb 13, 2011 at 03:03:40PM +0200, Avi Kivity wrote:
>>> On 02/13/2011 04:07 AM, Ruben Kerkhof wrote:
>>> >And tonight we had another one of those errors we had a few weeks ago:
>>> >
>>> >2011-02-13T02:56:28.694496+01:00 phy005 kernel: EPT: Misconfiguration.
>>> >2011-02-13T02:56:28.694908+01:00 phy005 kernel: EPT: GPA: 0x2edff000
>>>
>>> This GPA indexes into the 511th entry of the spte. Marcelo, does
>>> this remind you of https://bugzilla.kernel.org/show_bug.cgi?id=27052
>>> by any chance?
>>
>> This and the others reported. So yes, it looks something is corrupting
>> memory. Ruben, you can try to boot with slub_debug=ZFPU kernel option.
Ok, there are now only 6 vms left on this host, and I've booted it
with the slub_debug=ZFPU option.
After a few hours, I got the following result:
2011-02-24T21:41:30.818496+01:00 phy005 kernel:
=============================================================================
2011-02-24T21:41:30.818517+01:00 phy005 kernel: BUG kmalloc-2048 (Not
tainted): Object padding overwritten
2011-02-24T21:41:30.818523+01:00 phy005 kernel:
-----------------------------------------------------------------------------
2011-02-24T21:41:30.818526+01:00 phy005 kernel:
2011-02-24T21:41:30.818530+01:00 phy005 kernel: INFO:
0xffff8806230752ca-0xffff8806230752cf. First byte 0x0 instead of 0x5a
2011-02-24T21:41:30.818534+01:00 phy005 kernel: INFO: Allocated in
__netdev_alloc_skb+0x34/0x51 age=2231 cpu=8 pid=0
2011-02-24T21:41:30.818537+01:00 phy005 kernel: INFO: Freed in
skb_release_data+0xc9/0xce age=2368 cpu=8 pid=2159
2011-02-24T21:41:30.818541+01:00 phy005 kernel: INFO: Slab
0xffffea00157a9880 objects=15 used=13 fp=0xffff8806230752d0
flags=0x40000000004083
2011-02-24T21:41:30.818545+01:00 phy005 kernel: INFO: Object
0xffff880623074a88 @offset=19080 fp=0xffff8806230752d0
The rest of the output is attached since it's quite large.
Kind regards,
Ruben
[-- Attachment #2: messages.gz --]
[-- Type: application/x-gzip, Size: 46355 bytes --]
next prev parent reply other threads:[~2011-02-24 21:15 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
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 [this message]
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=AANLkTiknMneQtYqgmX7gvXsMoSO-yiLXr-dwbEej80Uy@mail.gmail.com \
--to=ruben@rubenkerkhof.com \
--cc=avi@redhat.com \
--cc=kvm@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;
as well as URLs for NNTP newsgroup(s).