[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Xen does not work after changing scheduler's code

yeah, I do familiar with nested virtualization. but using xen in xen has less 
performance vs using xen in vmware, so i decided using vmware.
but let me ask you, what do you do typically as a developer, in case of a 
development causes system failure or in my case kernel panic for example? DO 
you return to the last healthy system image of your setup (of course it 
wouldn't happen for you never, just asking for my inform)? 
Does developing these kind of mature system softwares, especially xen, has a 
especial tool?

From: Dario Faggioli <dario.faggioli@xxxxxxxxxx>
Sent: Wednesday, April 27, 2016 3:21 PM
To: tutu sky
Cc: Juergen Gross; Xen-devel@xxxxxxxxxxxxx
Subject: Re: [Xen-devel] Xen does not work after changing scheduler's code

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

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):

<<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)

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.