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: Tue, 26 Apr 2016 15:10:03 +0200 [thread overview]
Message-ID: <1461676203.3525.50.camel@citrix.com> (raw)
In-Reply-To: <HE1PR05MB13082FD191FC2B07BFF401BA8D6F0@HE1PR05MB1308.eurprd05.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 1533 bytes --]
On Fri, 2016-04-22 at 08:59 +0000, tutu sky wrote:
> yeah i tried, attaching a serial console was not possible for me, so
> i tried vmware and i tried match the information in link with some
> links on do the same using vmware. actually when using vmware for
> doing so, i changed: GRUB_CMDLINE_XEN line of grub to "loglvl=all
> guest_loglvl=all com1=115200,8n1,0x3e8,5 console=com1,vga" as
> mentioned in that link and it caused a kernel panic (blinding num
> lock and scroll lock together).
> if using two VM in vmware which one contains xen and other just does
> monitoring another, i think it must be possible to monitor xen.
>
So you're basically using nested virtualization for
developping/debugging.
That's a valid use case, and there are people doing it a log, and you
don't even need VMWare to do that.
In any case, even if I've never used VMWare, I suspect there is a way
to redirect the serial console of a VM to a file or a terminal, and
hence be able to see it without many problems.
As per what is going wrong, that's impossible to say without seeing the
error messages and the code. However, if you say that the problem only
manifests with your modifications, I would bet the error is somewhere
in there.
Regards,
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-26 13:10 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 [this message]
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
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=1461676203.3525.50.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 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.