From mboxrd@z Thu Jan 1 00:00:00 1970 From: Guido Winkelmann Subject: Re: Nested virtualization on Intel does not work - second level freezes when third level is starting Date: Wed, 11 Apr 2012 19:00:40 +0200 Message-ID: <8260391.A7oNVztJSs@pc10> References: <2064795.zbiLdg1ddQ@pc10> <2931461.6fZxCgUGcV@pc10> <4F859448.8010303@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit To: Orit Wasserman , kvm@vger.kernel.org Return-path: Received: from unknownsite.de ([62.48.69.106]:56497 "EHLO hartes-hannover.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756012Ab2DKRAs (ORCPT ); Wed, 11 Apr 2012 13:00:48 -0400 In-Reply-To: <4F859448.8010303@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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... ) Guido