From mboxrd@z Thu Jan  1 00:00:00 1970
From: Gleb Natapov <gleb@redhat.com>
Subject: Re: [nvmx testing, linux on linux] Disabling EPT in L1 renders L2
 stuck on boot
Date: Wed, 9 Oct 2013 11:16:37 +0300
Message-ID: <20131009081637.GJ3574@redhat.com>
References: <20131004093859.GF31244@redhat.com>
 <CAOaxAcatqVOKCJ06=ckkKBAkk_Vjsxqe1TaVgUXB8MsXHhLZyA@mail.gmail.com>
 <20131004130550.GA12257@redhat.com>
 <20131004130817.GB12257@redhat.com>
 <CAOaxAca2tfZxtjBwS43AGBR3yTaKb+fC8DpoW3bvn=RXtfJp8w@mail.gmail.com>
 <CAOaxAcbh8nfpV_fUh1kf+BTrE+tHF-GV1=uwKtFnP=hyWrc4Ug@mail.gmail.com>
 <CAOaxAcYXHxUPRO9V16HAPDJic_Nvvxe4YC7nZj5FTfzq9dXfVA@mail.gmail.com>
 <52540298.2030807@redhat.com>
 <52541B25.504@redhat.com>
 <CAOaxAcZocDO-wOdw7XQJjgf-MVJghm-0NiAq-P8UhahtiOLH_Q@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
To: Kashyap Chamarthy <kashyap.cv@gmail.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:61270 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751567Ab3JIMrY (ORCPT <rfc822;kvm@vger.kernel.org>);
	Wed, 9 Oct 2013 08:47:24 -0400
Content-Disposition: inline
In-Reply-To: <CAOaxAcZocDO-wOdw7XQJjgf-MVJghm-0NiAq-P8UhahtiOLH_Q@mail.gmail.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Wed, Oct 09, 2013 at 11:52:29AM +0530, Kashyap Chamarthy wrote:
> On Tue, Oct 8, 2013 at 8:18 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
> > Il 08/10/2013 15:03, Paolo Bonzini ha scritto:
> >> Il 08/10/2013 07:38, Kashyap Chamarthy ha scritto:
> >>> On Mon, Oct 7, 2013 at 6:29 PM, Kashyap Chamarthy <kashyap.cv@gmail.com> wrote:
> >>>> Gleb, so I just did a trace of KVM MMU to try to understand why L2 is
> >>>> stuck with shadow on EPT
> >>>
> >>> Paolo, were you able to reproduce this again? Yesterday, on #qemu you
> >>> mentioned you'll test it again :-)
> >>
> >> Yes, I could reproduce it too.

72f857950f6f19cba42a9ded078bbc99f10aa667 causes it and I ran kernel
without this commit. Will look into it.

--
			Gleb.