From: "Casey Jeffery" <kcjeffery-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Dor Laor" <dor.laor-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Recursive virtualization
Date: Wed, 4 Apr 2007 12:57:41 -0400 [thread overview]
Message-ID: <cb6aceaa0704040957r7ff6dc2dycc626e7079deceef@mail.gmail.com> (raw)
In-Reply-To: <64F9B87B6B770947A9F8391472E032160B318F00-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
Dor,
Thanks, I realize there will certainly be a lot of work in
virtualizing them. Maybe Intel can help out with VVT-x to give a
root-root mode. ;)
Any idea at a high level how vbox does it? I will post in their forum,
but I assume somebody here has a good idea.
Thanks.
On 4/4/07, Dor Laor <dor.laor-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote:
> >I swear this has been brought up before in this forum, but I can't
> >find it. I'm curious what the virtualization gurus in this forum think
> >of the possibilities for recursive virtualization. I know vbox claims
> >to support it, but I haven't come across many details on how they do
> >it and I don't think they really use the hvm hardware. Is it something
> >that should be possible without an "enlightened" guest hypervisor and
> >by basically just virtualizing the VMCS/VMCB structures?
>
> We have an open todo task for it.
> It is 'just' emulating the VMCS/VMCB structures and commands.
>
> >
> >-----------------------------------------------------------------------
> --
> >Take Surveys. Earn Cash. Influence the Future of IT
> >Join SourceForge.net's Techsay panel and you'll get the chance to share
> >your
> >opinions on IT & business topics through brief surveys-and earn cash
> >http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVD
> EV
> >_______________________________________________
> >kvm-devel mailing list
> >kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> >https://lists.sourceforge.net/lists/listinfo/kvm-devel
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-04-04 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 16:36 Recursive virtualization Casey Jeffery
[not found] ` <cb6aceaa0704040936j62354e99vb49108040ff79d4e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-04-04 16:48 ` Dor Laor
[not found] ` <64F9B87B6B770947A9F8391472E032160B318F00-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-04-04 16:57 ` Casey Jeffery [this message]
[not found] ` <cb6aceaa0704040957r7ff6dc2dycc626e7079deceef-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-04-04 21:30 ` Dor Laor
2007-04-04 16:53 ` Gregory Haskins
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=cb6aceaa0704040957r7ff6dc2dycc626e7079deceef@mail.gmail.com \
--to=kcjeffery-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=dor.laor-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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