From: George Dunlap <george.dunlap@citrix.com>
To: kumara rathnavel <kumara.bsd@gmail.com>, xen-devel@lists.xen.org
Cc: George.Dunlap@eu.citrix.com
Subject: Re: Log Messages ....
Date: Wed, 2 Dec 2015 16:55:48 +0000 [thread overview]
Message-ID: <565F2294.4060204@citrix.com> (raw)
In-Reply-To: <CA+NzLaO4teesMhQ9hm0fyyQgLV-1yqJ_b4XABk-Kyn3L4EmABw@mail.gmail.com>
On 02/12/15 16:48, kumara rathnavel wrote:
> Hello George,
>
> Thanks a lot. One more question if I connect serial port will I be able to
> see what is happening in xen....without using xen trace ....
Please don't top-post. :-)
If you set up a serial console you'll be able to get the same output as
"xl dmesg".
Here's a guide for serial consoles in Xen in case you need it:
http://wiki.xenproject.org/wiki/Xen_Serial_Console
-George
> On 2 Dec 2015 19:34, "George Dunlap" <George.Dunlap@eu.citrix.com> wrote:
>
>> On Wed, Dec 2, 2015 at 1:49 PM, kumara rathnavel <kumara.bsd@gmail.com>
>> wrote:
>>> Hello All,
>>>
>>> I require logs of the Hypercalls made from Guest to the Hypervisor after
>> the
>>> boot, as xl dmesg provides me with the log messages during the
>>> initialisation.
>>
>> One thing you could look at is xentrace and xenalyze. You can find a
>> brief introduction here:
>>
>> https://blog.xenproject.org/2012/09/27/tracing-with-xentrace-and-xenalyze/
>>
>> You can enable Xen tracing on the Xen command-line using the
>> "tbuf_size" and "tevt_mask" parameters described here:
>>
>> http://xenbits.xenproject.org/docs/unstable/misc/xen-command-line.html
>>
>> -George
>>
>
next prev parent reply other threads:[~2015-12-02 16:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 13:49 Log Messages kumara rathnavel
2015-12-02 14:04 ` George Dunlap
2015-12-02 16:48 ` kumara rathnavel
2015-12-02 16:55 ` George Dunlap [this message]
2015-12-03 4:52 ` kumara rathnavel
2015-12-03 5:47 ` kumara rathnavel
2015-12-03 5:52 ` kumara rathnavel
2015-12-03 9:50 ` kumara rathnavel
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=565F2294.4060204@citrix.com \
--to=george.dunlap@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=kumara.bsd@gmail.com \
--cc=xen-devel@lists.xen.org \
/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.