WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] daemon to monitor 'xm dmesg'

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] daemon to monitor 'xm dmesg'
From: Tom Rotenberg <tom.rotenberg@xxxxxxxxx>
Date: Tue, 15 Dec 2009 12:25:00 +0200
Cc: James Harper <james.harper@xxxxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 15 Dec 2009 02:25:21 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=kVwLnsgtJnx95L42E0EVHhHsfAGYng4mCxPjw/jSHI0=; b=HmTJZoLyrTTBW/sO95XMjpawEPL25RX7L71MIzKZ8As0v98U//TMkFC19uJqbHrale W5Jl7FUFBsXls9rPZUy7q0HpCwcD7yP/U2pXnsDTuaJpOEuVvI6tG94XT0mHPsEnUSJR 5vzvdXW92hY0gC/0jxX8JftSehwsbRRMcZXr4=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=UF9Qf8bw+Xf4FeR28uS2r1ysAH5abP46JiDqWVbCJHjnk7fSow+6CJ73kF+RKZPZln 4ZwXOPmU803L3E/dOVF/FkxWB4DXEQqOCoJib19Hzz1xCTGTPfQEu7Vd+b1nXSMMQ2z4 a9y13JYI3p5Ktk3Z+jdtTt9gEFvgwaLhAulMw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C74D1008.471C%keir.fraser@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AEC6C66638C05B468B556EA548C1A77D0180DC38@trantor> <C74D1008.471C%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxx> wrote:
> Start xenconsoled with option --log=hv
>
>  -- Keir
>
> On 15/12/2009 09:29, "James Harper" <james.harper@xxxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>