From: Guido Winkelmann <guido-kvml@thisisnotatest.de>
To: Kashyap Chamarthy <kashyap.cv@gmail.com>
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:04:15 +0200 [thread overview]
Message-ID: <1941720.kxlSPa5LQ7@pc10> (raw)
In-Reply-To: <CAOaxAcaZCuZqj8PP4BKvM1ZBTzWibDHUjXfmpiXub54Ak_DgGA@mail.gmail.com>
Am Mittwoch, 11. April 2012, 23:14:07 schrieb Kashyap Chamarthy:
> On Wed, Apr 11, 2012 at 6:14 PM, Guido Winkelmann
> <guido-kvml@thisisnotatest.de> wrote:
[...]
> Here is my complete notes on nested virtualization w/ Intel --
> http://kashyapc.wordpress.com/2012/01/14/nested-virtualization-with-kvm-inte
> l/
I had already found you blog post via Google :). In fact, I used some of the
things you wrote for setting up my system, in the hopes that I would have more
luck.
BTW, the line for modprobe.d/dist.conf should read
options kvm_intel nested=1
In your blog post, the "options" keyword is missing.
> My result: I was able to ssh into the nested guest (guest installed
> inside the regular guest), but, after a reboot, the nested-guest
> loses the IP rendering it inaccessible.(Info: the regular-guest has a
> bridged IP, and nested-guest has a NATed IP)
>
> Refer the comments in the above post for some more discussion. Though
> I haven't tried the suggestion of 'updating your system firmware and
> disabling VT for Direct I/O Access if you are able in the firmware' .
> And I wonder how does turning it off can alleviate the prob.
Yeah, I've seen that comment, that was what prompted me to update the server's
firmware. The Dell BIOS does not offer the option to disable VT for Direct I/O
Access, though.
> And my AMD notes is here(which was completely successful) --
> http://kashyapc.wordpress.com/2012/01/18/nested-virtualization-with-kvm-and-
> amd/
Unfortunately, AMD is not an option for me, at least not in this particular
context.
Guido
next prev parent reply other threads:[~2012-04-11 18:04 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
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 [this message]
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=1941720.kxlSPa5LQ7@pc10 \
--to=guido-kvml@thisisnotatest.de \
--cc=kashyap.cv@gmail.com \
--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