From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Zytaruk, Kelly" <Kelly.Zytaruk@amd.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Debugging Xen early boot
Date: Thu, 5 May 2016 10:19:55 -0400 [thread overview]
Message-ID: <20160505141949.GA5006@localhost.localdomain> (raw)
In-Reply-To: <CY1PR12MB02627FDD87D6914D34591D16FE7C0@CY1PR12MB0262.namprd12.prod.outlook.com>
On Thu, May 05, 2016 at 01:24:26PM +0000, Zytaruk, Kelly wrote:
> 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.
Also, are there any other Serial or Communication devices on the other
machine? Could you provide the lspci -v from both machines?
It may be that there is a built-in on the motherboard (like an AMT type
thing, or IPMI SoL?)
And if you boot Linux on it, can you do 'dmesg | grep tty' to see
what it finds in terms of serial cards?
>
> 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?
>
> Thanks,
> Kelly
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-05 14:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 13:24 Debugging Xen early boot Zytaruk, Kelly
2016-05-05 14:19 ` Konrad Rzeszutek Wilk [this message]
2016-05-06 12:31 ` Zytaruk, Kelly
2016-05-06 12:54 ` Jan Beulich
2016-05-06 13:41 ` Zytaruk, Kelly
2016-05-06 15:28 ` Konrad Rzeszutek Wilk
2016-05-06 13:04 ` David Vrabel
2016-05-06 13:43 ` Zytaruk, Kelly
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=20160505141949.GA5006@localhost.localdomain \
--to=konrad.wilk@oracle.com \
--cc=Kelly.Zytaruk@amd.com \
--cc=xen-devel@lists.xen.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.