From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Logging xen dmesg Date: Fri, 19 Aug 2011 15:25:16 +0100 Message-ID: References: <4E4E6C00.10405@adventiumlabs.org> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4E4E6C00.10405@adventiumlabs.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: John Backes , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 19/08/2011 14:58, "John Backes" 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