From: Keir Fraser <keir.xen@gmail.com>
To: John Backes <john.backes@adventiumlabs.org>,
xen-devel@lists.xensource.com
Subject: Re: Logging xen dmesg
Date: Fri, 19 Aug 2011 15:25:16 +0100 [thread overview]
Message-ID: <CA7430DC.1F75A%keir.xen@gmail.com> (raw)
In-Reply-To: <4E4E6C00.10405@adventiumlabs.org>
On 19/08/2011 14:58, "John Backes" <john.backes@adventiumlabs.org> wrote:
> Hello,
>
> I'm having a problem where the hypervisor is crashing when I call the
> verify_local_APIC() function and would like to see what the kernel
> prints out before it crashes. I know I can use xm dmesg to see
> current/past kernel messages, but is there a way to view a log of the
> kernel messages so I can see what was printed before the hypervisor
> crashed? Thanks in advance!
Options:
1. Specify noreboot on Xen command line, and read last few lines of log off
the VGA text local console (if you have that set up rather than, say, an X
server).
2. Set up a kdump crash kernel. I believe the kdump tools support reading
out things like the hypervisor console logs. I've never used kexec/kdump
myself however.
3. Set up hypervisor logging over a serial line. Then all log data will be
dumped over the serial line before the hypervisor reboots itself.
-- Keir
> - John
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-08-19 14:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 13:19 AMD IOMMU related boot failure due to page coalescing c/s 23767 Ian Jackson
2011-08-19 13:55 ` Wei Wang2
2011-08-19 13:58 ` Logging xen dmesg John Backes
2011-08-19 14:24 ` Pasi Kärkkäinen
2011-08-19 14:25 ` Keir Fraser [this message]
2011-08-19 14:55 ` AMD IOMMU related boot failure due to page coalescing c/s 23767 Wei Wang2
2011-08-19 15:57 ` Ian Jackson
2011-08-19 15:59 ` Ian Jackson
2011-08-19 16:12 ` Wei Wang2
2011-08-19 16:16 ` Ian Jackson
2011-08-19 16:29 ` Keir Fraser
2011-08-19 16:30 ` Ian Jackson
2011-08-22 11:29 ` George Dunlap
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=CA7430DC.1F75A%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=john.backes@adventiumlabs.org \
--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).