From mboxrd@z Thu Jan 1 00:00:00 1970 From: Orit Wasserman Subject: Re: Nested virtualization on Intel does not work - second level freezes when third level is starting Date: Wed, 11 Apr 2012 20:41:18 +0300 Message-ID: <4F85C23E.6090107@redhat.com> References: <2064795.zbiLdg1ddQ@pc10> <2931461.6fZxCgUGcV@pc10> <4F859448.8010303@redhat.com> <8260391.A7oNVztJSs@pc10> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Guido Winkelmann Return-path: Received: from mx1.redhat.com ([209.132.183.28]:59906 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754346Ab2DKSwn (ORCPT ); Wed, 11 Apr 2012 14:52:43 -0400 In-Reply-To: <8260391.A7oNVztJSs@pc10> Sender: kvm-owner@vger.kernel.org List-ID: On 04/11/2012 08:00 PM, Guido Winkelmann wrote: > Am Mittwoch, 11. April 2012, 17:25:12 schrieben Sie: >> On 04/11/2012 04:43 PM, Guido Winkelmann wrote: >>> Am Mittwoch, 11. April 2012, 16:29:55 schrieben Sie: >>>> I'm not sure if this is the problem but I noticed that the second layer >>>> and >>>> the third layer have the same memory size (8G), how about trying to >>>> reduce >>>> the memory for the third layer ? >>> >>> I tried reducing the third layer to 1G. That didn't change anything. >> >> There is a patch for fixing nVMX in 3.4. >> http://www.mail-archive.com/kvm@vger.kernel.org/msg68951.html >> you can try it . > > Should I use that patch on the host, or on the first virtualized layer, or on > both? (Compiling 3.4-rc2 for both for now... ) On the host (we refer to it as L0 by the way). Orit > > Guido