From: Tom Rotenberg <tom.rotenberg@gmail.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: James Harper <james.harper@bendigoit.com.au>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: daemon to monitor 'xm dmesg'
Date: Tue, 15 Dec 2009 12:25:00 +0200 [thread overview]
Message-ID: <8686c3cd0912150225n9f13ea7x10f0e9c5ab4ab49f@mail.gmail.com> (raw)
In-Reply-To: <C74D1008.471C%keir.fraser@eu.citrix.com>
And then to where will the log be directed to? where will it be
located on the HD?
On Tue, Dec 15, 2009 at 12:06 PM, Keir Fraser <keir.fraser@eu.citrix.com> wrote:
> Start xenconsoled with option --log=hv
>
> -- Keir
>
> On 15/12/2009 09:29, "James Harper" <james.harper@bendigoit.com.au> wrote:
>
>> Is there a way to put xen's logs into a file in dom0? Eg
>> /var/log/xen/hypervisor.log or something like that?
>>
>> I just did an 'xm dmesg' and saw this:
>>
>> (XEN) p2m_pod_demand_populate: Out of populate-on-demand memory!
>> (XEN) domain_crash called from p2m.c:1079
>> (XEN) Domain 72 (vcpu#0) crashed on cpu#1:
>> (XEN) ----[ Xen-3.4.2 x86_64 debug=n Not tainted ]----
>> (XEN) CPU: 1
>> (XEN) RIP: 001b:[<0000000071078f3a>]
>> (XEN) RFLAGS: 0000000000010246 CONTEXT: hvm guest
>> (XEN) rax: 000000000566300c rbx: 00000000003cb628 rcx:
>> 0000000000000000
>> (XEN) rdx: 0000000005660147 rsi: 0000000005660148 rdi:
>> 000000000566300c
>> (XEN) rbp: 000000000099e94c rsp: 000000000099e93c r8:
>> 0000000000000000
>> (XEN) r9: 0000000000000000 r10: 0000000000000000 r11:
>> 0000000000000000
>> (XEN) r12: 0000000000000000 r13: 0000000000000000 r14:
>> 0000000000000000
>> (XEN) r15: 0000000000000000 cr0: 0000000080010031 cr4:
>> 00000000000006b9
>> (XEN) cr3: 000000001fd9a360 cr2: 000000000eff8000
>> (XEN) ds: 0023 es: 0023 fs: 003b gs: 0000 ss: 0023 cs: 001b
>>
>> But I'm not sure exactly when it happened, other than it happened to
>> domain 72 whenever that was created.
>>
>> Thanks
>>
>> James
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2009-12-15 10:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 9:29 daemon to monitor 'xm dmesg' James Harper
2009-12-15 10:06 ` Keir Fraser
2009-12-15 10:25 ` Tom Rotenberg [this message]
2009-12-15 10:30 ` Keir Fraser
2010-02-23 23:43 ` Keith Coleman
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=8686c3cd0912150225n9f13ea7x10f0e9c5ab4ab49f@mail.gmail.com \
--to=tom.rotenberg@gmail.com \
--cc=james.harper@bendigoit.com.au \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.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).