From: Nadav Har'El <nyh@math.technion.ac.il>
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 17:38:14 +0300 [thread overview]
Message-ID: <20120411143814.GA20655@fermat.math.technion.ac.il> (raw)
In-Reply-To: <2064795.zbiLdg1ddQ@pc10>
On Wed, Apr 11, 2012, Guido Winkelmann wrote about "Nested virtualization on Intel does not work - second level freezes when third level is starting":
> Nested virtualization on Intel does not work for me with qemu-kvm. As soon as
> the third layer OS (second virtualised) is starting the Linux kernel, the
> entire second layer freezes up. The last thing I can see console of the third
Hi,
>From your description, I understand that "ordinary" (2-level) nested
virtualization working for you (host, guest and 2nd-level guest), and it's
the third nesting level (guest's guest's guest) which is broken?
This is the second report of this nature in a week (see the previous
report in https://bugzilla.kernel.org/show_bug.cgi?id=43068 - the
details there are different), so I guess I'll need to find the time
to give this issue some attention. L3 did work for me when the nested
VMX patches were included in KVM, so either something broke since, or
(perhaps more likely) your slightly different setups have features that
my setup didn't.
But in any case, like I explain in the aforementioned URL, even if L3 would
work, in the current implementation it would be extremenly slow - perhaps to
the point of being unusable (I think you saw this with grub performance in L3).
So I wonder if you'd really want to use it, even if it worked... Just
curious, what were you thinking of doing with L3?
Nadav.
--
Nadav Har'El | Wednesday, Apr 11 2012,
nyh@math.technion.ac.il |-----------------------------------------
Phone +972-523-790466, ICQ 13349191 |If I were two-faced, would I be wearing
http://nadav.harel.org.il |this one?.... Abraham Lincoln
next prev parent reply other threads:[~2012-04-11 14:38 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
2012-04-11 14:38 ` Nadav Har'El [this message]
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=20120411143814.GA20655@fermat.math.technion.ac.il \
--to=nyh@math.technion.ac.il \
--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