From: Guido Winkelmann <guido-kvml@thisisnotatest.de>
To: Orit Wasserman <owasserm@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: Nested virtualization on Intel does not work - second level freezes when third level is starting
Date: Thu, 12 Apr 2012 13:30:24 +0200 [thread overview]
Message-ID: <1578774.DqaTT2Xmez@pc10> (raw)
In-Reply-To: <2630612.xQ0BDW3ZUC@pc10>
Am Mittwoch, 11. April 2012, 20:37:56 schrieb Guido Winkelmann:
> Am Mittwoch, 11. April 2012, 17:25:12 schrieb Orit Wasserman:
> > 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 .
>
> That worked, though the VM inside the VM is still very slow...
Well, it appeared to work yesterday for a short time, but now a lot of
userspace programs in the L2 guest will die with a segmentation fault after
chrooting from the rescue CD to the installed OS...
Guido
next prev parent reply other threads:[~2012-04-12 11:30 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
2012-04-11 18:37 ` Guido Winkelmann
2012-04-11 18:46 ` Orit Wasserman
2012-04-12 11:30 ` Guido Winkelmann [this message]
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=1578774.DqaTT2Xmez@pc10 \
--to=guido-kvml@thisisnotatest.de \
--cc=kvm@vger.kernel.org \
--cc=owasserm@redhat.com \
/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