All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <dunlapg@umich.edu>
To: tutu sky <ooohooo_u@hotmail.com>
Cc: Juergen Gross <jgross@suse.com>,
	Dario Faggioli <dario.faggioli@citrix.com>,
	"Xen-devel@lists.xen.org" <Xen-devel@lists.xen.org>
Subject: Re: Xen does not work after changing scheduler's code
Date: Thu, 28 Apr 2016 09:32:00 +0100	[thread overview]
Message-ID: <CAFLBxZZcv-9ne4JVfNRYALYRM-6n-wWN_z3p+6DrdMRk4R6itw@mail.gmail.com> (raw)
In-Reply-To: <HE1PR05MB130897485CB77DEC5635D3778D640@HE1PR05MB1308.eurprd05.prod.outlook.com>

On Wed, Apr 27, 2016 at 6:17 PM, tutu sky <ooohooo_u@hotmail.com> wrote:
>
> 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.

So you'd rather hard-crash your development box quickly than
successfully debug your guest OS a little less quickly?

 -George

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

  reply	other threads:[~2016-04-28  8:32 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
2016-04-27 17:17               ` tutu sky
2016-04-28  8:32                 ` George Dunlap [this message]
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=CAFLBxZZcv-9ne4JVfNRYALYRM-6n-wWN_z3p+6DrdMRk4R6itw@mail.gmail.com \
    --to=dunlapg@umich.edu \
    --cc=Xen-devel@lists.xen.org \
    --cc=dario.faggioli@citrix.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.