From: Dario Faggioli <dario.faggioli@citrix.com>
To: tutu sky <ooohooo_u@hotmail.com>
Cc: Juergen Gross <jgross@suse.com>,
"Xen-devel@lists.xen.org" <Xen-devel@lists.xen.org>
Subject: Re: Xen does not work after changing scheduler's code
Date: Wed, 27 Apr 2016 17:21:50 +0200 [thread overview]
Message-ID: <1461770510.3525.145.camel@citrix.com> (raw)
In-Reply-To: <HE1PR05MB13082EB781F036CADB9EF44F8D640@HE1PR05MB1308.eurprd05.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 1325 bytes --]
On Wed, 2016-04-27 at 14:58 +0000, tutu sky wrote:
> Thanks Dario,
> and then, i don't understand what is your meaning by:
>
> "That's a valid use case, and there are people doing it a log, and
> you
> don't even need VMWare to do that."
>
> Do you mean that for developing/debugging three is no need for using
> vmware?
>
Exactly. Developing and debugging is a valid use case for nested
virtualization.
Nested virtualization means that you run an hypervisor (let's call it
level-1) as a guest of another (level-0) hypervisor.
What I think you are doing is using some version of vmware as level-0,
and then Xen as level-1.
And what I meant is that you can just use Xen at both levels.
Note that I don't know if it would be easier or harder, or in general
better or worse, to do so (as compared to what you are doing right
now). I only wanted to mention that it is possible.
This page may have more information (although, I'm not sure how updated
it is):
http://wiki.xenproject.org/wiki/Nested_Virtualization_in_Xen
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-27 15:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 7:48 Xen does not work after changing scheduler's code tutu sky
2016-04-22 8:03 ` Juergen Gross
2016-04-22 8:18 ` tutu sky
2016-04-22 8:46 ` Juergen Gross
2016-04-22 8:59 ` tutu sky
2016-04-26 13:10 ` Dario Faggioli
2016-04-27 14:58 ` tutu sky
2016-04-27 15:21 ` Dario Faggioli [this message]
2016-04-27 17:17 ` tutu sky
2016-04-28 8:32 ` George Dunlap
2016-04-28 10:46 ` tutu sky
2016-05-09 14:56 ` George Dunlap
2016-05-10 6:44 ` tutu sky
2016-05-10 8:34 ` Paul Durrant
2016-05-10 8:47 ` tutu sky
2016-05-10 9:42 ` Dario Faggioli
2016-05-10 9:45 ` Dario Faggioli
2016-05-10 10:02 ` tutu sky
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=1461770510.3525.145.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=Xen-devel@lists.xen.org \
--cc=jgross@suse.com \
--cc=ooohooo_u@hotmail.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).