From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54926) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YelIG-0002cE-K1 for qemu-devel@nongnu.org; Sun, 05 Apr 2015 10:12:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YelIF-00040t-Fp for qemu-devel@nongnu.org; Sun, 05 Apr 2015 10:12:56 -0400 Received: from mail-lb0-x235.google.com ([2a00:1450:4010:c04::235]:33075) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YelIF-00040C-3e for qemu-devel@nongnu.org; Sun, 05 Apr 2015 10:12:55 -0400 Received: by lbbzk7 with SMTP id zk7so6549542lbb.0 for ; Sun, 05 Apr 2015 07:12:53 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <20150330185634.GE13271@potion.brq.redhat.com> <20150331134512.GG13271@potion.brq.redhat.com> <20150331164539.GD14262@potion.brq.redhat.com> <20150401114923.GH13271@potion.brq.redhat.com> <551BF064.9030506@redhat.com> From: Andrey Korolyov Date: Sun, 5 Apr 2015 17:12:32 +0300 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] E5-2620v2 - emulation stop error List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: "kvm@vger.kernel.org" , =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , "qemu-devel@nongnu.org" , "Dr. David Alan Gilbert" , Bandan Das , Kevin O'Connor , Gerd Hoffmann A small update: the behavior is caused by setting unrestricted_guest feature to N, I had this feature disabled everywhere from approx. three years ago when its enablement was one of suspects of the host crashes with contemporary then KVM module. Also nVMX is likely to not work at all and produce the same traces as in https://lkml.org/lkml/2014/7/17/12 without unrestricted_guest=1. I think this fact actually explaining all real mode weirdness we`ve seen before and this should be probably ended either by putting appropriate bits in a README or module information or making strict dependency between apicv/unrestricted_guest+nested/unrestricted_guest or fixing the issue at its root if this is possible or appropriate solution. Thanks everyone for keeping up with ideas through this thread!