public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Orit Wasserman <owasserm@redhat.com>
To: Guido Winkelmann <guido-kvml@thisisnotatest.de>
Cc: kvm@vger.kernel.org
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	[thread overview]
Message-ID: <4F85C23E.6090107@redhat.com> (raw)
In-Reply-To: <8260391.A7oNVztJSs@pc10>

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




  reply	other threads:[~2012-04-11 18:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11 12:44 Nested virtualization on Intel does not work - second level freezes when third level is starting Guido Winkelmann
2012-04-11 13:29 ` Orit Wasserman
2012-04-11 13:43   ` Guido Winkelmann
2012-04-11 14:25     ` Orit Wasserman
2012-04-11 17:00       ` Guido Winkelmann
2012-04-11 17:41         ` Orit Wasserman [this message]
2012-04-11 18:37       ` Guido Winkelmann
2012-04-11 18:46         ` Orit Wasserman
2012-04-12 11:30         ` Guido Winkelmann
2012-04-11 14:38 ` Nadav Har'El
2012-04-11 16:27   ` Guido Winkelmann
2012-04-11 21:24     ` Nadav Har'El
2012-04-11 17:44 ` Kashyap Chamarthy
2012-04-11 18:04   ` Guido Winkelmann
2012-04-11 18:49     ` Kashyap Chamarthy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F85C23E.6090107@redhat.com \
    --to=owasserm@redhat.com \
    --cc=guido-kvml@thisisnotatest.de \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox