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

[Xen-devel] Debugging Xen early boot

  • To: "xen-devel@xxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxx>
  • From: "Zytaruk, Kelly" <Kelly.Zytaruk@xxxxxxx>
  • Date: Thu, 5 May 2016 13:24:26 +0000
  • Accept-language: en-US
  • Delivery-date: Thu, 05 May 2016 13:24:40 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:23
  • Thread-index: AdGm0BEMGzm+B6aRTl6hC3/z33zM+A==
  • Thread-topic: Debugging Xen early boot

I am having problems getting XEN boot messages over a serial console.

I have two systems.  On one system I can see the XEN boot message over a serial 
console whereas on the other system I cannot.

I physically move the same PCIe serial card and hard drive from one system to 
the other.  One system shows me the Xen boot messages and the other doesn't.

My config in /etc/grub.d/20_linux_xen is
xen_args="dom0_max_vcpus=4 dom0_mem=2048M,max:3072M iommu=1 conring_size=16384 
loglvl=all guest_loglvl=all com1=115200,8n1,pci console=com1"

I put a printk at the beginning of the Linux boot and I see the Dom0 Linux boot 
messages on both systems.  So I know that the serial port works on both systems 
but for some reason I don't see the Xen messages.

I would like to debug through __start_xen to see how the 16550 is being 
initialized.  Is there an easy way to debug __start_xen? 


Xen-devel mailing list



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