xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Sassy Natan <sassyn@gmail.com>
To: Daniel Stodden <daniel.stodden@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Thomas Goirand <thomas@goirand.fr>,
	Xen List <xen-users@lists.xensource.com>
Subject: Re: DomU as Dom0?
Date: Mon, 15 Feb 2010 14:08:49 +0200	[thread overview]
Message-ID: <529a12f41002150408n3882b70aw7c3230a8dd6d45d8@mail.gmail.com> (raw)
In-Reply-To: <1266229006.9492.38.camel@ramone.somacoma.net>


[-- Attachment #1.1: Type: text/plain, Size: 1604 bytes --]

WOW, This topic become a hot one.

I in a middle of written an overview about virtualized the virtual.
Thanks for all the pepole who respones to this email.

I will send my papaer once I will finish it :-)

Thanks for all

Xen is really cool project!

Sassy

On Mon, Feb 15, 2010 at 12:16 PM, Daniel Stodden
<daniel.stodden@citrix.com>wrote:

> On Fri, 2010-02-12 at 02:46 -0500, Thomas Goirand wrote:
> > Sassy Natan wrote:
> > > OK,
> > >
> > > Thanks for the answers
> > >
> > > Sassy
> > >
> > > On Thu, Feb 11, 2010 at 11:41 PM, Daniel Stodden
> > > <daniel.stodden@citrix.com <mailto:daniel.stodden@citrix.com>> wrote:
> > >     If you're rather looking for recursive virtualization, I don't
> think
> > >     that's going to fly all that well either.
> > >
> > >     Daniel
> >
> >
> > It's called "nested virtualization" (not recursive) and there was a talk
> > about it on the last Xen Summit in Shanghai. I suggest you to read the
> > video:
> >
> > http://www.xen.org/files/xensummit_intel09/xensummit-nested-virt.pdf
> >
> http://www.xen.org/media/Movies/XenSummitAsia09/2009-11-19-afternoon/NestedVirtualization.MTS
>
> Ah, nice. I didn't expect VMX emulation be actually in the works
> somewhere. Cool, thanks for the link.
>
> "Recursive" was the original term for such a beast.
>
> Any estimates on the footprint? Small enough to be a candidate for
> inclusion? It'd certainly be interesting for some applications.
>
> Cheers,
> Daniel
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>

[-- Attachment #1.2: Type: text/html, Size: 2771 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2010-02-15 12:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-11 19:43 DomU as Dom0? Sassy Natan
2010-02-11 20:49 ` [Xen-devel] " Konrad Rzeszutek Wilk
2010-02-11 21:41 ` Daniel Stodden
2010-02-12  6:23   ` [Xen-devel] " Sassy Natan
2010-02-12  7:46     ` Thomas Goirand
2010-02-12  9:13       ` [Xen-devel] " Pasi Kärkkäinen
2010-02-15 10:16       ` Daniel Stodden
2010-02-15 12:08         ` Sassy Natan [this message]
2010-02-15 16:32         ` Dong, Eddie
2010-02-16 15:50           ` [Xen-users] " Javier Guerra
2010-02-17  3:25             ` RE: [Xen-devel] " Dong, Eddie
2010-02-12 15:06 ` Thiago Camargo Martins Cordeiro

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=529a12f41002150408n3882b70aw7c3230a8dd6d45d8@mail.gmail.com \
    --to=sassyn@gmail.com \
    --cc=daniel.stodden@citrix.com \
    --cc=thomas@goirand.fr \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).