From: Javier Guerra <javier@guerrag.com>
To: "Dong, Eddie" <eddie.dong@intel.com>
Cc: Xen List <xen-users@lists.xensource.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Thomas Goirand <thomas@goirand.fr>,
Daniel Stodden <daniel.stodden@citrix.com>
Subject: Re: [Xen-users] RE: DomU as Dom0?
Date: Tue, 16 Feb 2010 10:50:58 -0500 [thread overview]
Message-ID: <90eb1dc71002160750vc00ccd7iaab64828c28d01c@mail.gmail.com> (raw)
In-Reply-To: <60E426D47DE8EA47AA104E65008A100D206EA40573@shzsmsx501.ccr.corp.intel.com>
On Mon, Feb 15, 2010 at 11:32 AM, Dong, Eddie <eddie.dong@intel.com> wrote:
>>> It's called "nested virtualization" (not recursive) and there was a
>
> It is just a name difference. It is actually recursivable as if the CPU is power enough.
not if (as in this case) you use different requirements for each
virtualization level. the 'real' level needs HVM support to set an
HVM DomU, where you can run Xen, but this level doesn't have HVM, so
you can only put PV DomU's there.
The KVM on KVM experiments are closer to being fully recursive.
--
Javier
next prev parent reply other threads:[~2010-02-16 15:50 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
2010-02-15 16:32 ` Dong, Eddie
2010-02-16 15:50 ` Javier Guerra [this message]
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=90eb1dc71002160750vc00ccd7iaab64828c28d01c@mail.gmail.com \
--to=javier@guerrag.com \
--cc=daniel.stodden@citrix.com \
--cc=eddie.dong@intel.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).