[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] Kernel BUG at "arch/xen/x86_64/mm/hypervisor.c":198

  • To: "Harald Koenig" <H.Koenig@xxxxxxxxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Petersson, Mats" <mats.petersson@xxxxxxx>
  • Date: Tue, 10 Jan 2006 18:38:11 +0100
  • Delivery-date: Tue, 10 Jan 2006 17:45:16 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcYWCqc0qjBRwafNS6iJ52ZYa6Ig9AAATF7A
  • Thread-topic: [Xen-devel] Kernel BUG at "arch/xen/x86_64/mm/hypervisor.c":198

> unfortuneately I didn't yet manage to get the _full_ crash 
> info for both the hypervisor _and_ the dom0 kernel in syslog, 
> and I'm still wrestling with the serial console when using 
> xen.  right now I only have a "real" 
> screen shot (4 Mpixel;) which shows both information, if this 
> is needed...

You may find that using a line like this:
kernel (hd0,0)/boot/xen-3.0-devel.gz dom0_mem=200000 com1=115200,8n1
co\nsole=vga,com1 sync_console
Gives you a good console output. 

Also adding console=/dev/ttyS0 on the line with the vmlinuz will help. 

Both of these in /boot/grub/grub.conf

The xen-command-line-argument of sync_console is critical in making sure
that the system doesn't actually reboot before the output is finished. 


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.