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
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
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 >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
<log_dir>/hypervisor.log where <log_dir> defaults to /var/log/xen/console but can be overridden with command-line option --log-dir -- Keir On 15/12/2009 10:25, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:> 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 >>_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Tue, Dec 15, 2009 at 5:30 AM, Keir Fraser <keir.fraser@eu.citrix.com> wrote:> <log_dir>/hypervisor.log where <log_dir> defaults to /var/log/xen/console > but can be overridden with command-line option --log-dir> > -- Keir > > On 15/12/2009 10:25, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote: > >> 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? >>>>Has anyone else noticed repeat messages in the log file after enabling hypervisor logging? It seems like whenever a few messages are logged to ''xm dmesg'' the entire contents of ''xm dmesg'' are appended to hypervisor.log. Keith Coleman _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel