From: Dario Faggioli <dario.faggioli@citrix.com>
To: tutu sky <ooohooo_u@hotmail.com>, George Dunlap <dunlapg@umich.edu>
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: Tue, 10 May 2016 11:45:32 +0200 [thread overview]
Message-ID: <1462873532.4858.40.camel@citrix.com> (raw)
In-Reply-To: <HE1PR05MB1308507ECAE5D1B80747FF048D710@HE1PR05MB1308.eurprd05.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 975 bytes --]
On Tue, 2016-05-10 at 06:44 +0000, tutu sky wrote:
> No, A Xen running inside Vmware does not crash until i modified it.
> it is not because of vmware at all (it may be caused because of my
> wrong development).
>
This is the second (and last) time I'm saying this:
if Xen works (either inside of VMware, or everywhere else) up until you
modify it, and then it stops working after you've modified it, there's
99.99% probability that it is your modifications that are wrong.
Of course, without knowing:
- what exactly crash
- how (we need to see the logs)
- what was that you were trying to do
- how you did that (we need to see the code)
There is nothing we can possibly do.
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: 819 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-05-10 9:45 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
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 [this message]
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=1462873532.4858.40.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=Xen-devel@lists.xen.org \
--cc=dunlapg@umich.edu \
--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).