From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: EPT: Misconfiguration Date: Sun, 13 Feb 2011 15:03:40 +0200 Message-ID: <4D57D6AC.7000608@redhat.com> References: <20110121132247.GA3097@amt.cnet> <4D3F0AD1.9010903@redhat.com> <4D3FEEDB.5070407@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Marcelo Tosatti , kvm To: Ruben Kerkhof Return-path: Received: from mx1.redhat.com ([209.132.183.28]:24574 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753936Ab1BMNDo (ORCPT ); Sun, 13 Feb 2011 08:03:44 -0500 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: 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: [] > warn_slowpath_common+0x7c/0x94 > 2011-02-13T02:56:28.695020+01:00 phy005 kernel: [] > warn_slowpath_null+0x14/0x16 > 2011-02-13T02:56:28.695024+01:00 phy005 kernel: [] > handle_ept_misconfig+0x152/0x1d8 [kvm_intel] > 2011-02-13T02:56:28.695028+01:00 phy005 kernel: [] > vmx_handle_exit+0x204/0x23a [kvm_intel] > 2011-02-13T02:56:28.695033+01:00 phy005 kernel: [] > kvm_arch_vcpu_ioctl_run+0x7cd/0xa74 [kvm] > 2011-02-13T02:56:28.695037+01:00 phy005 kernel: [] > kvm_vcpu_ioctl+0xfd/0x56e [kvm] > 2011-02-13T02:56:28.695042+01:00 phy005 kernel: [] ? > virt_to_head_page+0xe/0x2f > 2011-02-13T02:56:28.695046+01:00 phy005 kernel: [] ? > mempool_kfree+0xe/0x10 > 2011-02-13T02:56:28.695051+01:00 phy005 kernel: [] ? > mempool_free+0x76/0x7b > 2011-02-13T02:56:28.695055+01:00 phy005 kernel: [] > vfs_ioctl+0x32/0xa6 > 2011-02-13T02:56:28.695060+01:00 phy005 kernel: [] > do_vfs_ioctl+0x483/0x4c9 > 2011-02-13T02:56:28.695065+01:00 phy005 kernel: [] > sys_ioctl+0x56/0x79 > 2011-02-13T02:56:28.695070+01:00 phy005 kernel: [] > 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