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: Sun, 13 Feb 2011 15:03:40 +0200 [thread overview]
Message-ID: <4D57D6AC.7000608@redhat.com> (raw)
In-Reply-To: <AANLkTikS2M2pxO09PHN8+5+cBaQ593C9H7KthQHd4tM0@mail.gmail.com>
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?
> 2011-02-13T02:56:28.694914+01:00 phy005 kernel:
> ept_misconfig_inspect_spte: spte 0x25602d007 level 4
> 2011-02-13T02:56:28.694916+01:00 phy005 kernel:
> ept_misconfig_inspect_spte: spte 0x3df3e2007 level 3
> 2011-02-13T02:56:28.694919+01:00 phy005 kernel:
> ept_misconfig_inspect_spte: spte 0x5e90c7007 level 2
> 2011-02-13T02:56:28.694925+01:00 phy005 kernel:
> ept_misconfig_inspect_spte: spte 0x1603a0730500d277 level 1
Magic 1603a073........ pte.
> 2011-02-13T02:56:28.694928+01:00 phy005 kernel:
> ept_misconfig_inspect_spte: rsvd_bits = 0x3a00000000000
> 2011-02-13T02:56:28.694930+01:00 phy005 kernel: ------------[ cut here
> ]------------
> 2011-02-13T02:56:28.694933+01:00 phy005 kernel: WARNING: at
> arch/x86/kvm/vmx.c:3425 handle_ept_misconfig+0x152/0x1d8 [kvm_intel]()
> 2011-02-13T02:56:28.694936+01:00 phy005 kernel: Hardware name: X8DTU
> 2011-02-13T02:56:28.694941+01:00 phy005 kernel: Modules linked in: tun
> ipmi_devintf ipmi_si ipmi_msghandler bridge 8021q garp stp llc bonding
> xt_comment xt_recent ip6t_REJECT nf_conntrack_ipv6 ip6table_filter
> ip6_tables ipv6 kvm_intel kvm i2c_i801 i2c_core iTCO_wdt igb ioatdma
> dca iTCO_vendor_support joydev serio_raw microcode 3w_9xxx [last
> unloaded: scsi_wait_scan]
> 2011-02-13T02:56:28.695004+01:00 phy005 kernel: Pid: 4756, comm:
> qemu-kvm Not tainted 2.6.34.7-66.tilaa.fc13.x86_64 #1
> 2011-02-13T02:56:28.695008+01:00 phy005 kernel: Call Trace:
> 2011-02-13T02:56:28.695013+01:00 phy005 kernel: [<ffffffff8104d11f>]
> warn_slowpath_common+0x7c/0x94
> 2011-02-13T02:56:28.695020+01:00 phy005 kernel: [<ffffffff8104d14b>]
> warn_slowpath_null+0x14/0x16
> 2011-02-13T02:56:28.695024+01:00 phy005 kernel: [<ffffffffa00c97fb>]
> handle_ept_misconfig+0x152/0x1d8 [kvm_intel]
> 2011-02-13T02:56:28.695028+01:00 phy005 kernel: [<ffffffffa00ca401>]
> vmx_handle_exit+0x204/0x23a [kvm_intel]
> 2011-02-13T02:56:28.695033+01:00 phy005 kernel: [<ffffffffa0084998>]
> kvm_arch_vcpu_ioctl_run+0x7cd/0xa74 [kvm]
> 2011-02-13T02:56:28.695037+01:00 phy005 kernel: [<ffffffffa00735ba>]
> kvm_vcpu_ioctl+0xfd/0x56e [kvm]
> 2011-02-13T02:56:28.695042+01:00 phy005 kernel: [<ffffffff810feaab>] ?
> virt_to_head_page+0xe/0x2f
> 2011-02-13T02:56:28.695046+01:00 phy005 kernel: [<ffffffff810cc6ca>] ?
> mempool_kfree+0xe/0x10
> 2011-02-13T02:56:28.695051+01:00 phy005 kernel: [<ffffffff810cc857>] ?
> mempool_free+0x76/0x7b
> 2011-02-13T02:56:28.695055+01:00 phy005 kernel: [<ffffffff8111aa2f>]
> vfs_ioctl+0x32/0xa6
> 2011-02-13T02:56:28.695060+01:00 phy005 kernel: [<ffffffff8111afa2>]
> do_vfs_ioctl+0x483/0x4c9
> 2011-02-13T02:56:28.695065+01:00 phy005 kernel: [<ffffffff8111b03e>]
> sys_ioctl+0x56/0x79
> 2011-02-13T02:56:28.695070+01:00 phy005 kernel: [<ffffffff81009c72>]
> system_call_fastpath+0x16/0x1b
> 2011-02-13T02:56:28.695074+01:00 phy005 kernel: ---[ end trace
> d95032626ea304ca ]---
>
> Any help would be much appreciated. It seems very strange that I'm the
> first one who runs into this.
> I've found two bugreports which report the same, the first one at
> https://partner-bugzilla.redhat.com/show_bug.cgi?format=multiple&id=613691,
> but that's a duplicate of
> https://partner-bugzilla.redhat.com/show_bug.cgi?id=606131 which I'm
> not authorized to see...
These don't appear to be related. Are you running ksm, btw?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-02-13 13:03 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 [this message]
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=4D57D6AC.7000608@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).